I have created a table in a Word document. I have added a Table Title and Summary (right click Table-->Properties-->Alt Text)
I have tried a File--> Save As-->PDF and a File-->Save as Adobe PDF.
In both situations, when I ran the Accessibility Checker it returned Table Summary - Failed.
What happened to my table summary? Why didn't it convert?
As per the description given above, while running accessibility checker it returns Table summary failed. When converting word to pdf table content should convert to form fields.
For better understanding, you may please share the screenshot of the error message. If possible, please share the original word file as well as created PDF.
As a reference, please refer to this article: https://www.adobe.com/accessibility/products/acrobat/pdf-repair-repair-tables.html
... When converting word to pdf table content should convert to form fields. By @AkanchhaS
No no no no no. This is complete nonsense. Please ignore this comment.
Word tables should never convert to form fields.
Word tables should convert to PDF tables.
Thank you for all of this info Bevi.
Learning something new here everyday...
Thank you Bevi, so are you able to provide the answer. hy it isn't converting? I am running into the same problem.
Thank you for responding. Here are the screen captures.
It has been a while. I was wondering if anyone was able to replicate my scenario? While I know I can fix this by editing the Table Summary on the Adobe end, I'm trying to train staff to make their Word documents 508C before they convert to PDF. But if they have to do the Table Summary twice (once in Word and then again at the PDF end) they are going to have "Why am I doing this twice?!" questions.
Any help will be greatly appreciated. -- RLL
I too have experienced this bug, still trying to find an answer as to why and how to fix/work around
Adding to the suggestions, you may want to try and lower the security levels of the Macros, and just for troubleshooting purposes, you can also try the following:
I am in a newer version and I "lose" the table summaries, according to the accessibility checker. And I don't see them when I go to the table summary editor. But what's weird is that in read aloud mode the summaries are still there and are read aloud! Wish there was an easy fix!
I think that in this case, go back to the source Micrososft Word document.
MS Word also have an accessibility checker tool.
If, instead of using "Save As PDF, and you are exporting directly from MS Word to PDF using the PDF Maker add-in instead, then you should use the MS Word built-in accessibility checker tool before exporting to PDF.
Micrososft Word provides a more comprehensive checker tool that offers suggestions on how to make the document fully accessible and also spot errors.
As pointed out before in this thread, You may have to run the checker tool twice: once in MS Word before exporting to PDF, and if necessary in Acrobat (after the document is exported to PDF).
However, most people that have reported similar issues in these forums seem not to be aware that, in order to attain a higher succes rate in making an accessible PDF document, they must make the MS Word document fully accessible before the export action.
Acrobat is obviously the wrong tool to fix or add accessibility to a document specifically if the source document wasn't fully accessible to begin with.
My Word document was completely accessible before conversion to pdf according to the Word checker. When converted it had table summaries on all the tables. I think I used "save as Adobe PDF" to convert.
I should say it had table summaries on all tables in Word before conversion to pdf.
Would you be able to share an example of the PDF with no sensitive data on it?
I am curious now.
Okay. There isn't any sensitive data.
This sample retains the odd property of having the table summary available when I do read aloud mode, but shows up as an error in the accessibility check. Nothing shows up in "edit table summary" even though my original table summary is there somewhere to be read aloud. I attached the Word sample of the original source document also - no accessibility errors show up when I run the checker and the table summaries are there.
I think when I first opened the accessibility checker tool it had 31 of 32 checking options selected as a default, perhaps with table summaries not checked as one of the options, if I remember right. However, our office protocol requires us to run all 32 checks before posting so I added it back in.
Table Summaries are no longer recommended or required. The need for a summary was developed years ago before screen readers announced tables correctly.
Therefore, in the Acrobat Accessibility Checker, the option to check for table summaries is unchecked by default.
We suggest that your office update its policies on this.
Bevi, Thanks so much for your information! This is very helpful. I'll let our office know.
For a formal reference about this, download the free Tagged PDF Syntax Guide that is written by the PDF Association's committee that writes the PDF/UA standard. https://www.pdfa.org/resource/tagged-pdf-best-practice-guide-syntax/
Sec. 5.4.2 Summary attribute
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.
First, Alt Text is not the same as the Summary attribute. They are 2 different attributes used for different purposes.
Second, don't test a PDF with Acrobat's Read Aloud utility. It's a worthless piece of junk programming, created several years before we even had the PDF/UA standard. Therefore, it doesn't know what to do with a tagged PDF.
In techno-babble, it isn't a PDF/UA compliant text-to-speech reader, and is definintely not a fully featured screen reader. So expect false positives and false negatives when it's used. If you can, use a true screen reader — JAWS and NVDA (which is free at https://www.nvaccess.org/download/) are the 2 leading SRs. See our blog at https://www.pubcom.com/blog/2019_04-05/checking-with-screenreaders.shtml
Third, most screen readers don't normally recognize Alt Text on the <Table> tag. Alt Text was originally intended to describe graphical material, not text or text-based tables. The usage may expand in the future, but for now you're wasting your time putting Alt Text on a table.
Fourth, your tables are simple, basic tables; there's nothing about them that needs to be explained with a Summary attribute. You did a good job of designating the Column Headers <TH> and Row Headers <TH>, and that's all that these simple tables need to be fully accessible.
Good job on that!
And Fifth, the rest of your PDF has some accessibility errors. Some minor, some not-so-minor, but too many to describe in this all-volunteer help forum.
I am having the exact same issue. Accesibilty on word passes fine. Added summary in word, but not passing in PDF. I need the creator of the source document to create the summaries as my job is to simply hekp it pass PDF accessibility and my company doesn't want me putting in the summaries that the originator should have done in word.
As stated before, summaries on tables are not required per the accessibility standards.
My Word document was completely accessible before conversion to pdf according to the Word checker.By @defaultxfs9gvffregi
Don't depend on the checker in Word to verify the accessibility of the .DOCX file. It's a very low-level mediocre checker that checks only a few of the requirements.
Thanks once again for all of your helpful information Bevi. You've confirmed my suspicion that none of the checkers we use are adequate and that I don't know enough to be able to make these pdf documents accessible! I didn't know that the Adobe read aloud utility is not useful as a check. I'm going to get more resources.