Settings and activity

1 result found

  1. 233 votes
    How important is this to you?

    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
    jan45 commented  · 

    Hi Tanvi,

    Thank you for your response and the updates regarding the accessibility issues introduced in the September 2021 Acrobat and PDF Maker update. While I appreciate that some issues, such as the Alt-Text and drag-and-drop functionality, were addressed with subsequent releases, several critical problems remain unresolved. Specifically, the improper tagging of table borders as “PathPathPath” and the incorrect tagging of borders and background shadings as <Figure>s or “PathPathPath” are still causing accessibility failures. These issues violate PDF/UA-1 standards and continue to create significant challenges for users who rely on Acrobat for making legally compliant accessible PDFs, particularly in government and academic sectors.

    Additionally, the inability to revert to a previous version of PDF Maker after the update is a serious concern. This issue limits the flexibility for users who need a stable and reliable version to maintain accessibility standards. Given the wide-reaching impact of these problems, I urge Adobe to prioritize resolving these remaining bugs in future releases. Addressing these concerns will ensure that users can confidently produce fully accessible PDFs in line with legal and regulatory requirements. Thank you for your continued efforts, and I look forward to seeing these critical issues resolved soon.