This issue of InDesign and Acrobat incompatibility in regards to Acrobat displaying all spans even when the Reading Order is correct has been around for over two years. We deserve to know what Adobe is doing about it.

Acrobat Team acknowledges the problem and blames InDesign:

"It's actually not an Acrobat issue, it's an issue with InDesign and how it's generating the Content that Acrobat is displaying correctly"

https://forums.adobe.com/message/10005333#10005333

InDesign Team acknowledges the problem and blames Acrobat:

"You'd have to talk to the Acrobat team about why they display in the Tags panel the way they do." - Adobe
https://forums.adobe.com/message/10225230#10225230

OR

"Our investigation suggests that the issue lies in the latest update of Acrobat and there is little that can be done at our end to resolve the issue.
The problem has been communicated to the relevant team.
In the meanwhile we are closing this thread for InDesign."

https://indesign.uservoice.com/forums/601180-adobe-indesign-bugs/suggestions/33755254-accessible-pdf-exported-from-id-contains-spans-in

And closes the issue.

What is Adobe doing to fix this issue? And don’t tell us that it is not a real problem for screen readers because the Tags panel is ok. When a certain government agency reviews files, they just use the Reading Order Tool when they make complaints against people who use your product. These are not the kind of people who will read all these posts of Adobe blaming each other and then saying it does not matter because some screen readers don't use the reading order. Adobe is basically saying that this feature is pointless. If it is pointless remove it or merge it fully with the Tags panel.

Besides, there is a lot more assistive technology and applications than just JAWS and NVDA that depend on the reading order and reflow being correct.

What is Adobe doing to fix this span issue?

And don’t ask me for more info or more files. You have these posts with detailed explanations and you have already acknowledged the problem exists yourselves and acknowledged that you can reproduce it yourselves. And don’t tell us to go to Forums for help. Because they will send us back to UserVoice.

Thank you.

Feature Requests / Bug Reports for the Accessibility features in Adobe Acrobat Pro DC.

Adobe Acrobat Pro DC (Version 2018.011.20063) on Windows 7 Professional.

For the Tags panel:
1. Option to create Lists <L> tags with a set number of List Items <LI> tags instead of one at a time. Time wasted creating one at time.
2. Option to created tables <Tables> tags with a set number of Rows <TR> tags instead of one at a time. Time wasted creating one at time.
3. Stop forcing all the Tags folders to all be opened when opening a PDF file! Not efficient if having to reopen a PDF with an extensive Tags structure. These folders need to remain as they were when last saved!

For the Reading Order Popup menu:
1. Button to create List Items <LI> and List Body <LBody> for selected text. Currently have to manually change the tag for example <P> to <LBody>. Action Wizard is hit and miss with Lists, so I create from scratch many times.
2. Button to create Links <Link> for selected text and/or images with a popup box for enter the URL while simultaneously creating its Annotation in the Content panel and in the Tags panel. This would save time.
3. The Background/Artifact button doesn't work as it should. Items still go to the Tags panel.

For the Content panel:
1. Within the Page contents, the option to delete Annotations by selecting it and/or with a right click. This would save time.

For Adobe Acrobat Pro DC software updates:
1. Need a way to save my current customized layout so that when the software is updated, it is not lost. Time consuming to recreate with every software update. (iOS and PC).

Thank you,
terri@fusiononline.com

1. Brief Title

Losing german äüö (Umlauts) and letters in the Structure Tree when using "Add Tags to Document" in Adobe Acrobat DC (previous operation Number ADB-3207012-T1M7) German Language Problem?

1. Steps to reproduce the issue

Export a text document with german words that contain german umlauts (äöü), e.G.: "für, können, öfter, mögen" as a PDF without tags from InDesign or Word
Open the file in Acrobat DC
Go to "Tags" and open the little menu and choose "Add Tags to Document"
After the Structure Tree was created — save and close
when you open the document again in Acrobat DC and you can take a look at the tags in the Structure Tree and see that the letters are missing in the tags. Not only the umlauts but sometimes accompanying letters aswell
Examples: "für" -> "fr"; "können" -> "knen"
Conclusion: blind people can't read these anymore and the document is not accessible anymore!

The problem doesn't exist in Acrobat X and Acrobat XI.
The problem occurs with any font and all operating systems.
The problem was already documented with video and example-documents with the operation Number ADB-3207012-T1M7.

1. Operating system

The error occurs in all operating systems.

1. Expected results

Loss free texts in the Structure Tree with umlauts and all other letters so that the docment can be read by screen-readers.

1. Observed result

Missing letters in the Structure Tree after using "Add tags to Document" mainly in combination with Umlauts äöü and umlaut-ligatures.

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!

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

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.

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.

I am a PhD student and have switched to Adobes pdf viewer because I think it is the best one (google and edge do not offer the same accessibility for mark up etc.) The one thing that I love about google and edge is that you can set them to open the previously viewed document. I read a lot of articles and use the tabs as a sort of reading to-do list. But when I close adobe (or my computer restarts) that list disappears, I have to either remember them or go to the recently opened files to open them again (but since sometimes I opened them a long time ago it is low on the list or has disappeared). It would huge if adobe could automatically open all files that were previously opened the last time I closed it. Thanks!

I am encountering problems with poorly labeled controls in the Acrobat DC Action Wizard. As a blind screen reader user, I would greatly appreciate anything you can do to improve the control labels that are spoken by screen readers. I am using the JAWS 2020 screen reader with Acrobat DC version 20.006.20042.
The issues I have encountered:

1. Some of the button control labels are unclear and it is difficult to determine which control has focus. For example, when adding a Watermark, the button to add the watermark is spoken as “Add”. If I press “space” to select this option, another button appears, spoken as” Add”. I must tab to this second “Add” button and press enter to set watermark options.




2. I do not see a clear way to determine which control has focus when rearranging the sequence of actions. None of the buttons say “Selected” to let the user know which option is highlighted and will be modified by the “Move Up”, “Move Down”, or “Remove” from sequence buttons.




3. If using the NVDA or Windows Narrator screen reader, none of the options in the Action Wizard seem to read. These options due seem to be spoken in JAWS.




4. When trying to run an action, focus is automatically placed on the “Select a File” button. When I attempt to tab from the “Select a File” button to the “Start” Button, to launch my action, Acrobat DC crashes and completely closes. The only work around I have found is to not use keyboard navigation and instead use the mouse emulation options in JAWS to find and activate the start action button.

I don’t know if I have explained these issues clearly enough for you to reproduce. I need to use Acrobat DC in my work and would greatly appreciate if these issues could be resolved. Any assistance you can provide is greatly appreciated.

Thanks,
Peter

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.