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.

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.

Today I learned that when a PDF's text includes URLs that are -not- marked up as hyperlinks, Adobe Acrobat Reader, Apple Preview, and Google Chrome's built-in PDF renderer all attempt to convert the URLs to clickable hyperlinks for the reader's convenience.

However, Adobe Acrobat Reader does a noticeably worse job than the other software. Specifically: if the URL is followed by punctuation, Acrobat includes the punctuation in the target of the hyperlink, resulting in a broken link. Apple Preview and Google Chrome handle punctuation correctly.

You can see this behavior by opening the attached PDF in Acrobat, Preview, Chrome, and Firefox. (The Microsoft Word document I used to produce the PDF is also attached). The PDF includes some hyperlinks, some plain text URLs, and a variety of punctuation.

The most interesting cases are #2 and #3:
- Adobe Acrobat converts both plain text URLs to hyperlinks automatically, but gets it wrong, including ALL the punctuation, including the comma, the quotation marks, and the closing bracket (if present).
- Apple Preview converts both plain text URLs to hyperlinks automatically, and gets it right, including no punctuation
- Google Chrome (for Mac) does NOT convert the URL in #2 to a hyperlink; it converts the URL in #3 correctly
- Firefox (for Mac) doesn't convert either of them.

If Acrobat were improved to behave like Apple Preview or Google Chrome, LOTS of documents around the world would start having working, clickable links for readers that use Acrobat. In particular, URLs in the footnotes/citations/bibliographies of a large number of scholarly publications would start working for people.

I use Microsoft Edge in Windows 10 to view pdfs because it loads pdfs very quickly, and is smooth and responsive; it takes less than 5s to open 300MB+ pdfs.

Installed Adobe Reader recently because I needed the Fill & Sign function. I use Reader to Fill & Sign pdfs while viewing other pdfs with Edge.

After the installation, Edge takes more than 15s to open a pdf, even with small pdfs under 1MB. It has also become laggy. Chrome isn't affected though.

Completely closing Adobe Reader and reopening a pdf with Edge again solves this issue. It's a workaround but after a couple of days it's starting to get annoying. Please fix this.

I've already went online to unchecked the 'Auto-suggestions' option and cleared suggestions history.

Went back to using the Windows offline version. I am not signed in. suggestions still pop-up. Please look into this.

Also, for the love of all's good, please make this setting more accessible. Either make this setting available directly within the app itself or accessible directly online.

I cannot fathom why would they make the user jump through hoops for simple, commonly used functions. It's almost as if the offline and online functions were designed and developed completely separately and then later clunked together.

Recently kind of being forced to going back to using Adobe Reader after more than 10 years. Whatever happened to the workflow of the past as demonstrated in PS and Audition?

If you are unaware of the Quickbooks File Doctor's Advantages and Benefits of
Using this tool, it has several benefits and some of them are

network and connectivity setup issues can be easily resolved.

Its primary purpose is to fix -6000 series errors such as QuickBooks Error 6150, Quickbooks Error 6000 305, Error Code 6189, QuickBooks Error Code 6000 82, etc.

Additionally, it is the tool of choice for resolving errors from the H series: Error H101, Error H202, Error H303, Error H505, etc.

When your data gets lost or corrupted, you can rely on it to help you back up all your valuable information.

If you are trying to open a company file in one system that has been saved in another system, then QuickBooks File Doctor can help you.

To know more check https://quickbookstoolhub.com/quickbooks-file-doctor/

Since a recent Adobe Acrobat DC update, button styles set in InDesign are no longer working. They still work when the pdf is opened in a browser.

Steps to reproduce the issue: Create a radio button or checkbox in InDesign. Customise the style appearance for the on/off settings (colour, shape, text, removing default checks and dots, etc.). Export to Interactive pdf. Open in Acrobat. Button off styles have now reverted to default style settings. When you click on a button, it briefly shows the correct on style, but once you click off it reverts to the default style again.

Environment: InDesign CC 16.3. Adobe Acrobat DC 21.0. Windows 64-bit.

Expected result: button styles set in InDesign remain activated in Acrobat.

Observed result: styles revert to default settings in Acrobat.