The PDF/UA ("tagged PDF") standard was established in 2012 to add accessibility features to the PDF format using a system of tags.

The tags add semantic information to a document, "marking up" such elements as headings, lists, figures, tables and other common document idioms.

PDF/UA also offers a 'read order' feature, which allows content to be presented in a non-visual way which corresponds to the intended sequence.

These features may be created and edited using Acrobat Pro, which is good. although Acrobat Pro is currently unable to generate or accurately assess a fully compliant PDF/UA file without additional 3rd party software.
(The criteria for well-formed PDF/UA is documented by the Matterhorn Protocol. A URL to this spec may be found below. Acrobat's accessibility check does not follow this spec 100%).

The tagging and read-order features should permit 'semantic browsing' of PDF files, so that a visually impaired or dyslexic user can use a screen reader, braille device or other assistive technology to navigate a document.

Using Acrobat's "Read Aloud", a user is obliged to read every single word of every single page just to find content. They are offered no distinction between headings and body text, lists, list items, tables, figures or images even if those tags have been carefully set up by the document author.

With support for browsing via tags, a user would be able to skim quickly to the content they need, just as they already do with well-formed HTML pages in a modern browser.

Unfortunately, Acrobat Reader's accessibility features have not followed up with PDF/UA. There is currently no way to browse a tagged PDF using the tags, and there is very poor or non-existent support for assistive technology such as Apple's VoiceOver, Microsoft's Narrator, or third party ATs such as JAWS or NVDA.

Perhaps worst of all, there are no other PDF viewers on Apple's platform which communicate the PDF/UA tags to Apple's Accessibility API.

When a 'tagged PDF' is viewed in a browser, it does not generate an 'accessibility tree' - the data structure which communicates the semantic structure and content to the host accessibility API. Some of these in-browser PDF viewers come from 3rd parties, but at least one of them is offered by Adobe.

This means that even a well-formed PDF/UA is neither truly portable, nor truly accessible, making it wholly unsuitable for conformance with accessibility legislation such as Section 508.

Furthermore this could have legal consequences for Adobe's customers, who may be led to believe (by Adobe's own marketing materials and accessibility documentation) that "PDF tagging" is a legally viable way to conform to the accessibility guidelines mandated in various jurisdictions, especially including North America and the EU.

Will it take a lawsuit before Adobe acts on this shortcoming? It could be a painful, expensive and time-consuming way to address the problem.

My feature request is this: Adobe Acrobat should communicate the accessibility tags and read order in PDF/UA files to the appropriate accessibility APIs of any host system it runs on.

Until this happens, the accessibility of PDF as a whole may be described as "limited" at best. The "Read Aloud" feature offers a bare minimum of screen reader features - but is a very blunt tool, which offers a very inferior experience to users with visual impairments, dyslexia or similar disabilities.

2020 saw record numbers of accessibility lawsuits in the wake of recent legislation. Adobe should consider the legal risk of the current situation very carefully (especially the legal risk to Adobe's own customers), and perhaps revise its Acrobat marketing and documentation to clarify the shortcomings.

A "reference quality" PDF/UA file may be found at https://www.pdfa.org/wp-content/uploads/2021/04/Matterhorn-Protocol-1-1.pdf ... which happens to be the documentation of the PDF/UA spec itself.

Suggestions for this feature:
1. Add read out loud to the toolbar for easier access, including pause and play options.The read out loud feature is currently very inaccessible from the "view" drop down menu.
2. Allow user to choose where to start reading and stop reading by highlighting text, rather than the limited ability to only read full pages / the entire document
3. Upgrade voice - please consider adding a more adaptive voice to the program for read out loud. the system default is not pleasant for listening and we know the technology exists to have more advanced AI voices such as Google Assistant, Siri, and Alexa integrated into software.
4. Echoing another user - definitely highlight words / phrases being read aloud.

These suggestions are already standard features in many of my digital textbooks; however, the majority of my reading as a student consists of PDFs from scientific journals. As a college student with a visual impairment, I would really like to see these features be improved to meet today's technological standards and made more accessible to individuals with disabilities. I am planning on completing a five-year graduate program, and will be eagerly waiting for these improvements to be made.

For all of the machines in my Win 10 2004 test group, the Reader plugin for IE (AcroPDF64.dll) has lost the ability to start the print dialog, either from the handy button in the border UI, the drop down menu, or Ctrl+P. In all cases nothing happens. There are a variety of versions on the affected machines but most of them are quite current (20.9.20063 and ...65). The problem is restricted to IE (11 I have no other versions to check) and the new windows 10 2004 feature build.
If you're interested in any other data I can provide on the issue feel free to let me know.

Acrobat Reader DC changes the mouse pointer into its own scheme. Not talking about the specific tools, just the standard mouse when hovering over the Acrobat window.
I don't have the best vision, so I have my Windows mouse pointer set to be very visible, or I will lose track of it on the screen. But when using Acrobat, I lose track of the pointer, because Acrobat INSISTS that I don't get to use my custom pointer, but rather use the virtually invisible Acrobat default.
Why would Acrobat need to change the pointer? I get it for specific tools, like drag or magnify or whatever, but just for regular use? NO reason, other than to annoy users as much as possible

I need to read a PDF while using others apps at the SAME TIME; Reading the documentation of the other program from a PDF file.

I don't need toolbars. I dont' need status bars. I don't need menu bars.

I can press ctrl-f If I want to search for something, I can press ctrl-p if I want to print the document. I don't need a buttons or search bars for those to be constantly visible.

If I need to use ANY other functionality, I can right-click and all that functionality could be put into that right-click menu.

I ONLY WANT TO SEE THE CONTENT OF THE PDF!

So, you already have a "read mode". But you have failed it miserably; This read mode makes the acrobat reader go full screen, which is totally unusable; I need to be able to multitask, I need to see the documentation which is inside the PDF and to be able to use my other programs AT THE SAME TIME.

This is probably one of the most common use cases for PDF viewer and you fail it miserably. Full screen "read mode" hides my other program. and on windowed mode acrobat reader wastes one third of my window space for unnecessary UI bloat.

HI. I am using Adobe Acrobat Pro 2020 and Adobe Reader DC.
I think there is security bug at Adobe Reader DC when handling 3d-pdf files.

The problem is enabling 3d measurement tools at Adobe Reader DC with secured 3d-pdf files made by Adobe Acrobat Pro 2020.
I contacted to region customer service about this problem and received this function is intended option.

Customer center said that you’d better to contact bug report if you want to know about further information.

I should have not have bought Adobe Acrobat Pro 2020 bundle if enabling 3d measurement tools for secured 3d-pdf files.
I want to keep Adobe Reader DC from enabling 3d measurement tool when opening secured 3d pdf files have no permission.

Since using Adobe Reader DC for PC, the last few updates have only increased the number of clicks required to do basic tasks. When saving a document, with either the CTRL + S key press or selecting Save from the file tree, there doesn't seem to be any necessity to have the window attached pop up. It's a similar feature to Office programs now, and really only makes the process take longer. Clicking on Choose a Different Folder just brings up the same save options we had in the past. This just creates more steps and wastes time.

To be clear, this dialogue appears when I press SAVE or CTRL S, not when I click on Save As.