Create 508 compliant PDF documents frequently that need to be passed. These documents more than not have several lengthy tables. These documents also come from different people using different software and versions. And more than not these tables need to be rebuilt. Would love to have the option to create tables in the Tags sidebar from scratch where you can at the same time specify how many TR, TH, and TD and in a certain order. Right now I can only add them one at a time. Also, if there is a way to remove the hard setup of tables. Sometimes there is only one error where a TD is split into two when it should only be one. When I combined the cells, I then get a Regularity error even though the table is setup perfectly like a grid. In this case, I have to completely rebuild the table from scratch to remove the error. Hope in the next few updates, Adobe can add some more of these options for Accessibility tables.
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

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

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.

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 am using Keyboard only to access the Tags Panel.

Switching between the Advanced Search menu, and the main document Window, using F6 to move Focus to the Tags panel and Find Tag from Selection work great. I perform subsequent actions and my first search/action is done.

Then I Alt tab back to the Advanced Search panel, move up to the next item, Alt tab back to the main document Window, F6 to the Tags Panel, the item I searched for is selected, but the previous Tag (from search # 1) still has dotted lines around it and it has focus.

My highlighted Search and Found from selection term is selected but when I use the Up arrow on my 2nd, 3rd, 4th searches, it does not go to the item above my selection, it goes to the item above the previous tag from Search 1 (the one with the dotted lines around it).

I want to release this focus and put focus on the item I searched for and apparently this is not possible. Have tried Escape, Space Bar, Shift F4, all to no avail. When I search for an item and Find Tag from Selection I think focus should go to that item FULLY, so that when I arrow up it goes to the next content item or tag above that searched for item. This does not happen.