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.
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.
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
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.
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 for images 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 tag with 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 tags 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 are also very sorry for the inconvenience caused by these issues.
Issue #1 and #6 being new issues with Sep 14 update were fixed on priority and another update on Sep 29th (Release Notes for September 29, 2021: https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/continuous/dccontinuoussept2021qfe.html#dccontinuoussepttwentytwentyoneqfe ) carried the fixes for both of them. You can click Help → Check for Updates… to get the latest version of Acrobat containing these fixes.
The remaining issues have been added to our product backlog and will be prioritized to be fixed in coming releases.
Thanks & Regards
Vikki Howe commented
I work on GOV.UK for the Department for Education and this bug has had a huge impact on our content's accessibility.
This can currently only be fixed by manually clicking into each cell row and deleting the P tag (unless there are any other work arounds?) Some of our research publications have over 40 tables in them and this is having a huge impact on our teams’ resource. We are having to spend hours, days fixing PDFs to ensure this error is fixed and the content meets the new accessibility legislation that came into force for public sector content back in 2018. This is having a direct impact on our publishing deadlines.
This also has an impact on all PDFs with tables previously published on GOV.UK. When we initially published content it was accessible but with this update these publications no longer are. This is a global issue and will affect the accessibility of 1000s of publications on GOV.UK.
Please can you let us know when we can expect a fix for this.
Hi Tanvi, can I just check if you have a fix date for this issue? Thanks.
Bevi Chagnon | PubCom.com commented
Thanks for the updates.
Bugs #2-#5 are indeed from a previous release, but they are now being flagged as errors in Acrobat's internal accessibility checker, especially in Table Headers.
Note: PathPathPath is a serious accessibility error no matter where it appears, not just in table headers.
Please don't wait until spring to fix this with all of the PathPathPath, whether they:
— appear in an <Artifact> tag (which is not a legal PDF/UA-1 tag),
— are role-mapped to <P> (which makes them discoverable by assistive technologies),
— are embedded and mixed in with the content,
And please don't tell us to turn off checking table headers (we're required by various country laws to ensure they are accessible). That's not allowable because we'd be breaking our laws.
Natasha galea commented
I agree with Bevi, this is an issue that should be resolved, as it can take hours to remediate list tagging in a large document. Please update us on your engineer's progress.
Kimberly Steinmann commented
Please fix these issues soon! California state government cannot post PDFs that dont meet accessibility standards - I have hundreds of documents to convert - many over a hundred pages - and i cant go through an manually fix all the table headers - the PDF crashes!
David Burnham commented
I installed the 20099 update. Now the save aa a pdf is not working in addition to links not working.
The Sep 29th update didn't fix issue #1 when installed. Are there others for whom the update did not work?
Like others have commented: The issue with the alt-text is not that the alt-text do not covert to the pdf, but that images tagged as decorative get a gibberish alt-text. This makes is impossible to create a accessible Word-template.
Bevi Chagnon | PubCom.com commented
HERE'S ANOTHER BUG:
Hyperlinks from latest Word 365 + latest PDF Maker don't work.
David Burnham commented
Tanvi - Adobe is not making their customers happy. This is urgent.
You have built up reliance on these tools to make accessible PDFs that are mandated and treated as compliance in many countries.
Laura Hopkins commented
We are unable to tread water, waiting for these issues that were rolled out to be remediated. We are unable to make any accessible PDF forms. Please advise the ETA.
Liv Detrick commented
Please fix this bug so that we can create accessible PDF documents.
Ilana Gordon commented
Please fix all bugs related to the September update of Acrobat DC. It's astounding that version was released without proper testing and has negatively affected the ability to provide accessible information.
Please fix the tables issue ASAP. Please bring back the previous version while you are correcting the September 14 version.
Please fix the tables issue ASAP.
This worked, thank you! Still having all of the other issues mentioned here, but you have fixed my header and TOC issue and are my favorite person right now! TYSVM!
Michele Christian commented
let me know if this fix helps your H2 to images problem:
To fix, in Word, go to the first heading level where the problem occurs (in this example it would be “2.1.1”), highlight the number with the cursor, and hit Ctrl + space bar.
This action should fix all heading level threes (or any other heading levels that exhibit this error). This fix needs to be done only once, but the TOC must be regenerated (the image errors carry over from the headings to the TOC).
UPDATE: H2 and TOC image issue resolved. All other issues remain.
In addition to the issues already mentioned, level 2 headings and their associated TOC items on larger documents exported from Word are incorrectly tagged as images. I cannot attach a sample as the documents I work on a proprietary.
All of these are MAJOR issues as making these documents accessible is required by law. I have installed the most recent update and still have all of the issues mentioned here.
I echo the others, PLEASE fix these issues, they are barriers for many people with disabilities and clients will get human rights complaints against them, as well as lawsuits, if they can't remediate their own PDFs, because of the software problem.
Karen McCall commented
PLEASE fix the PathPath issues with table gridlines, bordered paragraphs, hyperlink underline and other things that normally would be artifacts but are now in the tags tree inappropriately! I tried artifacting what should be an artifact yesterday and couldn't do it in Acrobat! I'm also seeing Path stuck onto text. For example "PathIntroductionPathPath" and can't artifact the Path in the Content Panel. It says it is artifacted but is till in the tags tree. This is adding hours of additional work that is not necessary and is a barrier to those of us who have to produce legislatively conforming PdF documents! I vote to fix this as soon as possible!!!!!! Artifacts should not be in the tags tree!
Lori Schulze commented
Please address the issues immediately. This negatively impacts businesses, organizations, and state governments. But most importantly, it impacts the user experience for users of assistive technology.