Brennan Young

My feedback

  1. 11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Acrobat for Windows and Mac » Accessibility  ·  Flag idea as inappropriate…  ·  Admin →
    Brennan Young supported this idea  · 
  2. 182 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    62 comments  ·  Acrobat for Windows and Mac » Creating PDFs  ·  Flag idea as inappropriate…  ·  Admin →

    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 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…

    An error occurred while saving the comment
    Brennan Young commented  · 

    These new bugs may put Adobe customers in legal difficulties, which in turn may become a serious legal problem for Adobe. It is especially bad that users can not downgrade to an earlier version which does not have these bugs. Drop everything and get this fixed ASAP, please.

  3. 15 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Hi,
    Thanks for connecting with us. I went though all the requests suggested by you. I would like to inform you that :
    For #1, Shortcut keys exist for Pause, Play like Ctrl+Shift+Y/V/B.
    For #2, the feature is supported. Click on any paragraph after enabling Read Out Loud and it will read the paragraph. For specific content read, we have informed the management and have been kept in radar for future improvements.
    For #3, you can add the voices though system language setting and the voices will be visible in Acrobat if they exists on system.
    For $4, we have informed the management and have been kept in radar for future improvements.

    Try the latest enhancements and features on the latest version of Acrobat Pro DC.

    Thanks
    Rachit

    An error occurred while saving the comment
    Brennan Young commented  · 

    The correct thing to do is to ditch "Read Aloud" entirely, and instead support semantic tags so that the reader feeds an accessibility tree to the host system's accessibility API.

    Then users can choose whatever assistive tech they prefer (or have to use, because of their particular disability).

    I have made a feature request about this. Please vote for it.

  4. 14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Brennan Young shared this idea  · 
  5. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    Brennan Young supported this idea  · 
  6. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Acrobat for Windows and Mac » Accessibility  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Brennan Young commented  · 

    Thanks for the answer Rachit, but it is not helpful. As far as I can tell, Acrobat for Mac does not expose an accessibility tree to Mac OS, which means that PDF/UA is not actually supported on the Mac platform at all.
    Given that Apple Preview ignores PDF/UA tags and read order, it also means that PDF/UA is neither portable (beyond MS Windows), nor accessible (on Mac).
    PLEASE prioritise this. Apple has an accessibility API for both Mac and iOS. Acrobat should use it.

    Brennan Young supported this idea  · 
  7. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Acrobat for Windows and Mac » Creating PDFs  ·  Flag idea as inappropriate…  ·  Admin →
    Brennan Young supported this idea  · 
  8. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Acrobat for Windows and Mac » Creating PDFs  ·  Flag idea as inappropriate…  ·  Admin →
    Brennan Young supported this idea  · 
  9. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Acrobat for Windows and Mac » Other  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Brennan Young commented  · 

    The problem is not 'broken tags' it's 'no tags at all'.

    Adobe PDF Print simply does not generate PDF/UA files from the browser. (Browser may be failing to generate an accessibility tree, which is not Adobe's fault, but reflects badly on PDF as an accessible and portable format)

    Semantics are entirely lost when you create a PDF using the Adobe PDF print gadget.

    The use case is:

    Make (or visit) a WCAG compliant HTML5 page in any browser that supports Adobe PDF print.
    Print the page to PDF using Adobe PDF print.

    Expected Result - Semantics converted to corresponding PDF/UA tags in output
    Actual Result - Non-tagged PDF is output

    Brennan Young shared this idea  · 
  10. 44 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Acrobat for Windows and Mac » Accessibility  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Joel,
    We are always working to make it a better of experience for our accessibility customers.
    We’ll be adding the support of Undo/Redo in order panels and Reading Order Tool in our coming releases.
    Can you please tell me why you need the Tags Panel and Reading Order to be merged.

    Thanks
    Rachit.

    An error occurred while saving the comment
    Brennan Young commented  · 

    "We are always working to make it a better of experience for our accessibility customers"

    Does that include the Mac version? I can't get any PDF viewer on Mac to play properly with VoiceOver, expecially including Acrobat Reader.

    As long as this goes unfixed, Adobe are choosing to make PDF unviable in various jurisdictions, including USA, Canada, EU, UK and others, because accessibility compliance is now mandatory in these regions, for the public sector at least, and there is legislation for the private sector on the road map too. Laws have already passed about accessible digital content in France for larger firms. Wake up Adobe!

Feedback and Knowledge Base