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.

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?

2. 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.

3. Operating system

The error occurs in all operating systems.

4. 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.

5. Observed result

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

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

Please change the way Adobe Acrobat does the reading order so that the tags in the tags pane will automatically correspond to the order in the Touch- up reading order pane.
Also please make it easier to tag links - when I try to tag links it doesn't work right. Please consider creating a version of Adobe Acrobat that makes it easy to comply with Section 508 as described at Section508.gov. Dealing with the tags pane is a nightmare and also the unmarked annotations issue and other issues are a nightmare and don't fix easily. Please make this easier to use so the people will be more cooperative about complying with Section 508. Thanks.

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.
2. 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

I have a Microsoft Word file that has a number of images. I need to make an accessible PDF. I have entered alternate text for each image in MS Word. When I convert the Word file to PDF, the alternate text I had entered in MS Word is carried over to the PDF, which is what I want. The problem is that it puts all images/figures at the beginning of the tag tree no matter where the image comes in the document. When I look at the Reading Order for each page, it puts all images as the last item to be read on the page, even if the image is at the beginning or middle of the page.

If I use the Autotag Document function to re-tag the file, it puts everything in the correct order but the alternate text entries for every image has been stripped out.

I am using the latest version of Mac Acrobat DC 2018.011.20038

1- Make a form field.
2- Select it so you can make a <form> with the OBJR
3- Drag it into its proper spot in the reading order.
4- Then move it even one pixel, it will delete itself. This happens on all fields of any type. It also happens if you just resize any field.

Since this Adobe Forum usually asks questions until people give up on the thread I even made a video of the whole thing:

https://drive.google.com/open?id=1S79CQ53xiebkxiXmZawAML2kpSY3O6Bn

By the way, I lost 17 hours of work. When I was done with my form. I just use the alignment tools to make my fields line up, and it deleted every field the Acrobat adjusted itself.

As the title states, the right-click context menu is not consistent when in the Accessibility Reading Order tool. For example, when right-clicking tables to access the Table Editor and/or Edit Table Summary views, those items are sometimes not available.

With the Table Editor you can still at least access the floating Reading Order window to click open the Table Editor. However, when the Edit Table Summary menu item disappears (they always disappear in pairs), I have to manually save the PDF to refresh its context menu. Sometimes I have to close out completely. It appears random. I can go for 40 tables, then the next 5 I have to manually close out to refresh for each table. I cannot find a pattern for why the Table Editor option vanishes either.

- Noel

It has been important in my practice to review reports and multitask. The Apple OS version of Adobe Acrobat is not compatible with the system-wide keystroke of option+s, which activates text-to-speech. This essential function works with MS Office 365 and other third-party apps. Secondly, the rate of speech (even after changing the preferences) is too rapid for use. Clearly, the options of reading the whole page or whole document are limitations. I work with patients who have auditory processing problems, and I can imagine that this function makes some document reading inaccessible. The current configuration is probably an upgrade for Windows® users, but inefficient for Apple® users. The current tag routine consumes time and is not efficient as selecting text and listening to the text. Please consider adding an option to disable the Adobe text-to-speech function, similar to Microsoft Office so that one can use the Apple text-to-speech function. Thank you for reading and considering this concern.