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

We received this document from a vendor and it wasn't tagged for accessibility. I went through page by page, adding figure alternative text, table summaries, and tagged H1 through H3 headings. Then using Adobe's book mark tool I auto-generated the bookmarks based on the H1-3 heading tags.

I sent this document to our 508C consultant who is blind. He used NVDA and JAWS to read the document. He found all of the alt text for figures but could not see the H1-3 tags nor could he see any of the tables or table summaries.

I double checked the document using the Reading Order panel. Everything is there.

What is going on? We are very concerned. Since we are a government entity we are required by law to make our public documents accessible.

Please advise. I have had issues with manually tagging with Adobe Pro DC. Now I am using Adobe Pro 2017 Version 2017.011.30138

Thank you
Rachael Leyba
Technical Writer
Olmsted County, MN

Why doesn't Adobe set the default initial view magnification setting to "fit page" so a viewer can see an entire document upon initial view? As a seasoned graphic designer, I believe it is much more courteous to allow the viewer to orient themselves to an entire document and then allow then to zoom in for more detail. It is disconcerting to see a partial document when opening a PDF file. Adobe is a leader in accessibility standards and I wondered if you had insight into this topic, I don't see a recommended initial view magnification in the WCAG 2.0 AA standard but I have found references that state that the "page fit" works better for some screen readers when they read a PDF. I'm seeking a "best practice" guideline. Please respond at your earliest convenience. Thank you.

I use Word 365 of a main docment to generate a PDF, and remediate in Acrobat DC. I have to add in pages in the fron an back of the document that comprises the front and back covers (also from Word). (The cover PDFs also pass accessibility check).

However, when I drag one page into the Main document PDF and run the accessiblity checker, all the hyperlinks that tested OK in the main document now generate a 'tagged annotations' error.

Normally, remediating such errors is easy: you show in the content panel, find the unmarked links/annotations and tag them appropriately.

However, Acrobat finds no unmarked links or annotations, so these files cannot be remediated.

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.