Accessibility Errors with PDF Maker Update Sept 2021
Several major bugs have been documented by users in the Adobe Community Forums since Acrobat and PDF Maker were updated on September 14, 2021.
They are:
1: Alt-Text from MS Word is not converting into the PDF. Instead, it is dropped and gibberish code is inserted. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017 This violates the PDF/UA-1 standard which requires that every graphic have alt-text that verbally describes the graphic.
THIS IS A HUGE BUG. You essentially have made Acrobat unusable for those who are required by their country's laws to make fully accessible PDFs.
2: Every cell border on every table cell is being tagged as:
<P>PathPathPathPath. This violates PDF/UA-1 because unnecessary visual formatting is not being tagged at Artifacts.
See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017
3: The underline on Hyperlinks should be tagged as artifacts. Right not, it appears as one or more "PathPathPath" which is announced by different assistive technologies. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017
4: Borders and background shadings on Text Boxes are being tagged as a combination of <Figure>s and PathPathPath. This too is a violation of PDF/UA-1. https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017
5: Paragraph borders and shadings: same deal as #4 above.Per the PDF/UA-1 standard, they are visually decorative and should be artifacted. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017
NOTE: To be correctly tagged per PDF/UA-1, the borders/shading content should:
— Not appear anywhere in the Tag tree, either as <Figure> or as "Path" in a yellow content container box.
— Not appear in the Order panel.
— Should appear as Artifact in the Content panel.
6: Dragging and dropping elements in both the Tag and Order panels is now broken.
The text cursor doesn't show anymore, and the little black line doesn't show anymore and instead appears several inches away from where it really is. See https://community.adobe.com/t5/acrobat-discussions/alt-text-converting-wrong-from-word-to-pdf/m-p/12393017 and also https://community.adobe.com/t5/acrobat-discussions/acrobat-pro-reading-order-box-and-tag-dragging-no-longer-visible/m-p/12395226#M329877
And finally...
7: Once this update is installed, users can't revert back to a previous version of PDF Maker because Adobe doesn't allow that in Acrobat like it does with other Creative Suite applications.
So once the update is completed, it makes PDF Maker completely unusable for tagged accessible PDFs.
This affects millions of your government customers world wide, as well as millions of government contractors and millions of academic customers...all of whom are required by their country's laws to make accessible PDFs.
2 sets of sample Word and Matching PDF files are submitted as demonstrations of the problems in the exported PDFs via PDF Maker.
Hi,
Thank you for raising these accessibility issues. The post mentions about the following six bugs being introduced with the update that went live on September 14, 2021
1: Alt-Text from MS Word is not converting into the PDF. Instead, it is dropped and gibberish code is inserted
2: Every cell border on every table cell is being tagged as <P>PathPathPathPath
3: The underline on Hyperlinks should be tagged as artifacts
4: Borders and background shadings on Text Boxes are being tagged as a combination of <Figure>s and PathPathPath
5: Paragraph borders and shadings: same deal as #4 above.Per the PDF/UA-1 standard, they are visually decorative and should be artifacted
6: Dragging and dropping elements in both the Tag and Order panels is now broken.
Would like to mention that out of these, #1 and #6 were introduced with the Sep 14 update and remaining (#2, #3, #4 & #5) were present even in the Acrobat version prior to Sep 14 update. We apologize for the inconvenience caused by these issues.
Issue #1 and #6 were the regressions introduced with Sept 14th update and hence were fixed on priority with Sept 29th Update (Release Notes for September 29, 2021). With the latest version (22.001.20085) of Acrobat Pro DC released on March 7th (Release Notes for March 07, 2022), issues #2 and #3 have also been fixed. Issues #4 and #5 have been partially fixed so that PathPathPath tags won’t be part of the tag tree anymore. The remaining issue for #4 and # 5 (Borders and background shadings on Text Boxes / paragraphs are being tagged as <Figure>s) have already been added to our product backlog and those will be prioritized to be fixed in coming releases.
You can use the menu item Help → Check for Updates… to get the latest version of Acrobat Pro DC containing these fixes. Please try out the fixes and share the feedback as that will help us make our applications better from accessibility perspective.
Thanks & Regards
Tanvi Rastogi
-
Bevi Chagnon | PubCom.com commented
Screen capture of a PDF exported from Word 365 with PDF Maker 20.
Note the missing Lbl tag that should be inside the LI tag. -
Bevi Chagnon | PubCom.com commented
When PDF Maker exports PDFs from MS Office, lists are not tagged correctly per the PDF/UA-1 standards.
Each bullet or numeral character should be encased in an Lbl tag. Correct tag structure should be:
L
LI
Lbl (the bullet or numeral character)
LBody (the body text of the list item)At this time, PDF Maker does not include the Lbl tag and combines the bullet/numeral within the LBody tag.
This is an incorrect, non-compliant tag structure.
-
Bevi Chagnon | PubCom.com commented
When PDF Maker exports PDFs from MS Office, lists are not tagged correctly per the PDF/UA-1 standards.
Each bullet or numeral character should be encased in an Lbl tag. Correct tag structure should be:
L
LI
Lbl (the bullet or numeral character)
LBody (the body text of the list item)At this time, PDF Maker does not include the Lbl tag and combines the bullet/numeral within the LBody tag.
This is an incorrect, non-compliant tag structure.