5
Replies
Hi -I need to have table summaries for all my PDFs with tables to meet accessibility requirements.
By @K_steinmann
Table summaries are not needed to meet accessibility standards. The use of summaries was developed eons ago when screen readers didn't have as many user features as today's do.
If you're using Acrobat's built-in accessibility checker, UNcheck the option for Table/Summaries.
Reference: 5.4.2 Summary Attribute in the PDF/UA Syntax Guide available for free from the PDF Association (which manages and creates the PDF/UA accessibility standard under the ISO). Download a free copy from https://www.pdfa.org/resource/tagged-pdf-best-practice-guide-syntax/
I dont see anyway to create the table summary in Word though - alt text for the table does not seem to transfer to the PDF. Is there any part of a Microsoft Word document that will transfer over as the table summary when i create the PDF?
Nope!
Don't confuse Alt Text with Summary. Although both are attributes on <Tags>, they are for different purposes on different tags. Alt Text should be used only on graphics, its original intent, or complex hyperlinks. If it's used on a table, I don't know of any assistive technology that will voice it because that's a non-standard use of Alt Text.
If you'd like to make tables accessible, then follow the guidelines:
- Keep them simple, that is with a "regular" and uniform series of rows and columns (don't merge cells in the body of the table).
- Make sure you have <TH> tags on column and row headers (row headers are optional at this time).
- Put a caption <Caption> on the table. Best to have it appear before the <Table> tag so that it can prepare a user before they actually start to navigate it.
Hi @K_steinmann, not the first time I've heard that from our California clients.
I think their information and internal guidelines for the state's materials are out of date.
I'm a US delegate to the ISO's committees for PDF/UA standards, and I'm a former contributor to the WCAG standards for websites. I read standards for "fun" in my free time, and I will confess, we don't make it easy for anyone to figure out what's the current way to do things!
WCAG defines summaries well in section H:73 https://www.w3.org/WAI/WCAG21/Techniques/html/H73 Note the first green note lower down on the page:
In HTML5 the
summaryattribute is obsolete. Assistive technologies may or may not continue to support the attribute. Authors should consider alternatives and only use with caution.
The PDF/UA Syntax Guide also doesn't recommend table summaries. In section 5.4.2 Summary Attributes:
It is recommended that use of this attribute be restricted to cases where visual information about the table would not be characteristically available to assistive technology.
Where auxiliary information or guidance would be useful to any user it is recommended that such be provided in text, and not hidden in a Summary attribute which would only be available to those using certain AT.
Providing a Summary is not precluded for specific target audiences, but it is recommended that the practice be limited to such cases.
Generally, follow PDF/UA for PDF documents, but when you get to something that either isn't addressed by PDF/UA or you'd like more details, then consult WCAG, too. We try to make both standards mesh with each other, but remember that the technologies are very different from each other. A PDF file is not the same as an HTML webpage so the 2 standards are not going to be identical.
I hope you can pass this along to your IT department that's enforcing their internal accessibility standards.
AdChoices