Hello,

To whomever may be competent to solve the problem....

There are several incomprehensible bugs with accessibility in Acrobat. Many tags are not correctly created, even if the link has been created directly from acrobat.

Links give problems of "tagged annotations - incorrect", recursively.

Problems with the establishment of the reading order, when the programme wants to, it does not tag correctly, those declared as artefacts do not disappear from the reading order, you try to remove a reading order from the structure and it does not do it, you try to mark it as another type of element and it does not do it either.......

In tables, sometimes the table summary or edit options do not appear (which incomprehensibly have to be made to appear with a contextual menu that only appears if the reading order box is open).
When you try to modify the cells to mark merged cells, always at the beginning of the table, the table rows are affected and it does not do it correctly.

The reading order cannot be undone and if there is something that the program does incorrectly and you have not saved it, you have to start again.

And a long etc.

I cannot understand how the creators of great platforms such as Photoshop, Illustrator, Indesign and others, could have created a programme as bad as Adobe Acrobat and that in addition in the accessibility options it still works as badly as its previous versions.

See you!!

Problem Description: While remediating document for accessibility in Adobe Acrobat Pro DC, Visual Tags that are assigned can sometimes be stacked or overlayered (<P>, <H1>, <TOC>, etc.) on top of the tagged text. This makes it difficult to ISOLATE AND KNOW the layered tag that you would like to right-click on the output display.

Steps to Reproduce: //Open a Table of Contents in Adobe Acrobat Pro DC/ Open Accessibility Checker and check document/ Click on Tags Icon in Accessibility Menu/ Click on Reading Order/ go to body of document/ Identify tags that look like they are overlayered on top of each other/ Left click tag and wait until it turns blue/ Right click cluster of Tags where top tag on output display is blue/

Actual Result: Output Display shows condensed right-click menu for unknown tag (Up to 10+ right clicks) or shows expanded menu for unknown tag.

Expected Result: Output Display shows expanded right-click menu for specific tag.

Any Workarounds: (Just an idea and is Unimplemented and Untested) When Output display shows tags that are overlayered on text as well as other tags, the first right-click will let you choose which element of the overlayered cluster of tags to apply the right-click to.

When performing Acrobat remediation on Indesign publications containing correct export tagging, the Acrobat Reading Order tool shows "P" tags at the end of each line of text (as well as additional "P" tags in the middle of lines). The Acrobat Tags panel shows no paragraph tags -- just broken up lines of text.

Fortunately, these broken up lines are not reproduced as such by the screen reader. So why does Acrobat identify each line of text with a "P" in the first place?

This issue needs to be fixed as it creates a dilemma and lot of unnecessary remediation work for those who are unaware that screen readers are able to bypass broken up lines and read the full paragraph.

Microsoft Word 365 has an immersive reader where the text is read out loud while panning and highlighting the text being read with options such as WPM adjustment. Trying to use the Read Out Loud function in Adobe Acrobat Reader is painful. It is hard to find, the synthetic voice is unpleasant and disruptive, and overall the accessibility for this feature seems to be the bare minimum. PDF's are the format of choice for scientific papers, which are rather dry reading material. An option to listen, following along while reading would greatly increase the efficacy of this program. I've personally been converting the PDFs to a Word Document and then using the immersive reader, but this workaround is imperfect as the conversion does not always result in a legible document, and alienates users from the native Adobe program. This program is in desperate need of updates to expand document accessibility to persons that may have impaired vision, ADHD, Dyslexia, etc.

Not only is the DC interface confusing and more time-consuming to use than the old one, but it does not comply with Section 508 of the Americans With Disability Act, which requires that the federal government, in its software procurement process, consider accessibility. Adobe Acrobat does not take into account the needs of users who rely on voice recognition software to accomplish actions that fully abled users accomplish with the mouse. When using voice recognition software, it is quick and easy to dictate a shortcut key or sequence of shortcut keys, but extremely slow, cumbersome and error-prone to get the software to click on a particular location. In the older version of Adobe Acrobat, most of what I did could be accomplished by dictating shortcut keys. In the new version, very few commands can be accomplished with keyboard shortcuts (or even with a series of them, as in Microsoft applications). As a result, I do almost nothing in Acrobat with my voice recognition software. Using the current version exacerbates the repetitive stress injury that I rely on voice recognition software to minimize. For one of many resources explaining that the availability of shortcut keys is an element of Section 508 compliance, see: https://www.justice.gov/crt/software-accessibility-checklist.

Within Adobe Acrobat there are options to Create a Portfolio of documents or to use the Attachment feature to create a group of documents. While keyboard shortcuts allow you to browse some of the menus, get to the document list, and select a document from the list. However, there is not a keyboard short cut to read the document in the view or to access the Open Document link. It seems to be only available through mouse selection.

This places users of these features at risk because the end user can't access the document to read it using only keyboard selections. Since these features lack keyboard accessibility, the product is not fully accessible.

It would be amazing if you didn't have to go all the way inside Cell Properties to check and see what a header cell's scope is set as, and what header cells are associated with any given cell in a table. If, once you were already inside Table Editor, that information would be available when you hover over any given cell (could be a feature that can be turned on or off), it would save so much time and effort in a very tedious job.

When a table is really large or complicated, it can be easy to lose your place when assigning associated headers and scope, and it would be a huge timesaver/help to have this info available on a hover-over.

Thanks for listening!

I want to report a bug in the read-out loud feature of Acrobat Pro DC. I’m using a Mac (Mojave), and I have already set its accessibilty options to my favorite system voice and speaking rate. I thought I’d have a PDF doc read out aloud while I work on some graphics. The default voice was meh-next-to-terrible, so I looked under preferences for an option to change voice. I found it and was happy to find a long list of available voices, including the ones I already have installed on my computer. So I selected my favorite voice and tried having the doc read out loud,… and the voice sounded horrendous! It didn't recognise the settings I have for it on my system. So, back to Acrobat settings looking for a setting to correct that. Well, you have settings for pitch and words per minute (Note that the options available don't match up with what is on the OS preferences.), but no way of previewing it! I have to go back to the document to be able to hear the difference and go back to preferences, try a different setting, and repeat… navigating back and forth... too much bother! I simply gave up.
So could the devt /programming team include on the next update of Acrobat a pre-listen (preview) button in the preferences? That would be sooo helpful. Thanks.

Auto Generate Cell IDs adds a space to the end of IDs which are not long enough, and appears to be including internal spaces. Since cell IDs cannot contain spaces, those headers are not announced by AT when reading the table. (OS: Windows 10 on desktop PC; Acrobat Pro DC 20.012.20043; latest as of 8/30/2020).

The attached file has two identical tables (Word 365, Saved as PDF) with auto-generated header IDs. With the first, NVDA (v 2019.2) only announces the headers for Vegetable, Potassium, and Brocolli. All other headers have spaces at the end, and the IDs for % DV have a space after %. NVDA reads the second table fine with those spaces removed from the IDs.

This is not an anomaly that Acrobat Accessibility Checker or even PAC 3 catches. The tagger who does not actually check the complex table with a screen reader can submit a document to the client with a table that is unreadable.

When you have elements with no alt-text you get accessibility errors when running the checker. However, if you right click on the error and choose "fix" and walk through the items and mark them as decorative, instead of actually making them an artifact it simply changes the tag to "Artifact" which is not a valid tag and creates other errors. You then have to go in and properly designate the objects as Artifacts properly for the other errors to go away. VERY Frustrating. Come on Adobe Acrobat!

This is a repeatable condition and needs to be fixed immediately please!

Setting something as an artifact is a state and not a valid tag in the tags tree. Very frustrating that one tool designed to fix an issue actually creates other issues.

https://youtu.be/cLpXgisBgeg

Current Behaviour - If a PDF document has a title present in the “Title” document property then the default initial view of Acrobat Reader and Acrobat PRO is set to "File Name" rather than the "Document Title".

Impact - Acrobat's Accessibility Checks report the "Title" error while the title is already there. This requires the "Initial View" setting to be changed on each PDF manually.

Desired Behaviour - Set the “Initial View” to “Document Title” as default when a PDF is opened on Acrobat Reader DC and Acrobat DC Pro.

Why the feature is needed - All organisations want to publish their PDFs which are 100%. For example, all US Federal agencies are required to publish their PDFs which are Section 508 compliant. Acrobat Accessibility Checks tools allow to achieve Section 508 compliant by making the PDF's accessible. If PDF contains a title then it doesn't make sense to keep the Initial View to "File Name".

Please release a patch or add this feature in the next versions or Acrobat Reader and Acrobat Pro versions.

Hyperlinks that span more than one line create multiple OBJR tags.
Reproduce: Create file in InDesign with links that span more than one line. Export to PDF/open with Acrobat. Find tag. Link will have two OBJR tags (or more if the link spans more than two lines). This is a bad experience for users of assistive technologies.
Sometimes manually fixing tags (deleting old links and creating new OBJR tag) isn't sufficient and designer has to resort to editing in the content pane or even using the Actual Text override to get the link to be read by assistive technology properly.
Please fix so that links that span multiple lines only have one tag.