Skip to content
← Share your feedback on Acrobat DC

Settings and activity

2 results found

  1. PDF Maker: New Bug puts <Figure> tags in the wrong reading order

    64 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    11 comments  ·  Acrobat for Windows and Mac » Accessibility  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    LS commented  · 

    This is critical to fix this problem. Why is Adobe not caring about human rights? I just don't get it. They may read this and say this isn't human rights, yes it is. PDFs are used by businesses, organizations, health care, governments around the world, and yet again Adobe shows that people with disabilities don't matter. Do better!!! You did better in 2009 than today. Why are we still 'voting' for accessibility for people with disabilities?????

  2. Accessibility Errors with PDF Maker Update Sept 2021

    233 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    84 comments  ·  Acrobat for Windows and Mac » Creating PDFs  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Started  ·  AdminTanvi Rastogi (Lead Software Engineer, Adobe) responded

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

    Thanks, great to see!

    An error occurred while saving the comment
    LS commented  · 

    Adobe do better! For the love of god, it is 2022, and here we are...why? Why is accessibility not put into your every day workflow, with checks at every single step from the absolute beginning? I am so frustrated with you. I have used PDFs since the beginning, the absolute beginning and we had an easier time making PDFs accessible in 2010 then today, why is this so problematic? Microsoft changed their culture about 7-8 years ago, and while they aren't perfect, I no longer have to tell clients how bad their product is...now I say that about you! What will it take? Do we need to do a class action lawsuit in every country? Why do we need to beg for basic accessibility fixes????

    An error occurred while saving the comment
    LS commented  · 

    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.

    LS supported this idea  ·