Settings and activity
2 results found
-
17 votes
Hi Jerra,
Thanks for reaching out to us. We are reviewing your feedback and will get back to you soon.
Thanks,
ShwetaDezinah supported this idea ·An error occurred while saving the comment -
231 votes
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)…
An error occurred while saving the comment Dezinah commentedCORRECTION:
Adjusting previous post. Regular graphics in Word with Alt-text are exporting correctly to PDF with their Alt-text in tact.It's when graphics in Word are marked as decorative / artifact that is still creating an error in the PDF. They are being tagged as <P>image content (which is incorrect) and have the code gibberish for Alt-text.
End result for screen reader users:
They just hear the code gibberish be voiced, but with hearing that it's an image. And it's code gibberish.These are supposed to be artifacted and completely hidden from users, not producing gibberish.
Dezinah supported this idea ·An error occurred while saving the comment Dezinah commentedUPDATE on Sept 29, 2021
Acrobat 2021.007.20095 (and PDF Producer Library 21.7.127) were updated today.
The "fix" is just as bad as their original bug!
Before, our alt-text was lost when the PDF was exported from Word and replace with nonsense code.With this so-called "fix", we now get ... N O T H I N G.
No Alt-text at all.And the table headers and rows are still producing PathPathPathPathPathPath rather than artifacting that stuff.
What is wrong at Adobe?
Do they really want us all to leave them and go to Foxit's PDF software instead?
Excellent suggestion!
Use the HTML tags and DOM to convert it to a PDF/UA-1 compliant PDF.
See the PDF Association's Syntax Guide at https://www.pdfa.org/resource/tagged-pdf-best-practice-guide-syntax/