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!

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.

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

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.

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.

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!

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

We noticed that your PDF viewer doesn't have AccSupp ActualText support. This means that copy-pasting technical text such as shellscripts and programming code, does not work in your PDF viewer and this greatly restrains the use of your whole program.

The replacement text is said to be supported, according to the file "Document management - Portable document format - Part 1: PDF 1.7" both on Table 323, page 559, and on section 14.9.4, page 615. Available here: https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf.

But according to the tests made using PDFs produced by pdflatex using the package accsupp, the replacement text support seems to be unreliable at the moment for copy and paste.

The tests are shown here: https://github.com/ho-tex/accsupp/issues/2
The tests generated various behaviors such as:
- Correct copy and paste of the text, but incorrect copy and paste of leading spaces and empty lines (Test 1);
- Unexpected insertions of spaces (Test 3 and Test 6), and;
- Spaces turned into newlines (Test 4).

We kindly request better support of the replacement text support, because the copy and paste directly from the PDF document is not reliable.

Please also refer to these two pages for further discussion:

https://tex.stackexchange.com/questions/563803/how-make-a-latex-document-that-generates-a-pdf-from-which-copy-paste-works-corre

https://github.com/ho-tex/accsupp/issues/2

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.