For PDF/UA, we have used alt to enter the alternate text for images and
links, the expansion text for acronyms and abbrevations and for actual
text on various elements such as copyright and trademark. We created
schematron rules to ensure that the alt text is entered and customized
the stylesheets to write the alt text to the FO. (On a side note, PDF/UA
also requires tagged PDF.)
For HTML, we ensure alt text on images.
I have not looked into table summaries yet, but will soon have to make
sure that they are present in HTML output (optional in PDF/UA).
Have a great weekend,
Katharina
On 09/12/2014 06:37 PM, Bob Stayton wrote:
Following up on Peter's comment, on further examination of the
stylesheets, I think you will be frustrated if you try to use alt,
because the current support for it in the stylesheets is very limited.
In DocBook 4.5, the alt element was allowed only in equation and
inlineequation. In DocBook 5.0, alt was added to the block-level
elements mediaobject, table, informaltable, and informalequation. It
also expanded into over 150 other elements because it was added to the
"ubiquitous inlines" class of elements, so it is available most places
where text content is allowed, including para and entry.
However, the stylesheets have not been completely updated for these
changes. Only alt in mediaobject generates an alt attribute on <img>.
Also, for some inline elements, an alt child if present will generate
a title attribute on the html <span> element. For all other cases,
the default template for alt is used, which generates no output.
This situation clearly needs some improvement. Before proceeding, I'd
like to hear what others have to say regarding alt and accessibility
for various elements, so that best practices can be followed if
possible. For example, what should be done with any alt children of a
para?
Bob Stayton
Sagehill Enterprises
[email protected]
On 9/11/2014 8:10 AM, Peter Desjardins wrote:
I think you picked the correct list. This one is for discussing
element choice and semantics, I think.
When I was writing for a large company that enforced strict
accessibility requirements I used the alt element for images and
tables. As far as I can tell, the alt element is specifically for
alternate text, as used for accessibility
(http://docbook.org/tdg5/en/html/alt.html).
(Veering into the publishing topic) I find that text in
informalfigure/mediaobject/alt makes its way into the alt attribute of
my HTML img elements. However, text in informaltable/alt elements
seems to go nowhere. And I have a hazy memory of customizing HTML
output for tables in order to handle the alt element in the way my
company required. But it wasn't too hard any you can get help on the
docbook-apps mailing list, which is for discussing publishing tools
and customization.
Good luck!
Peter
On Thu, Sep 11, 2014 at 8:36 AM, Janice Manwiller <[email protected]>
wrote:
Apologies in advance if this is the wrong list. I've had conflicting
advice
about what to post to docbook vs. docbook-apps.
I'm brand new to DocBook, and am reviewing the current source files
for the
doc set at my new job.
Is there a recommendation for providing alternate text for
accessibility?
The current source files have textobject for images and nothing for
tables.
Is the alt element better than textobject?
For tables, should I use alt or summary?
Thanks,
Janice
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
