Acrobat Accessibility Checker "Failed" and "Needs manual check": what 7 items need, and how a pass can still fail a reader

"Tagged content" is Failed

Documented (Adobe): The rule "reports whether all content in the document is tagged." Adobe's instruction is to make sure all content is "either included in the Tags tree, or marked as an artifact." The fixes it lists: mark the content as an artifact (Content panel, right-click, Create Artifact), tag it with All tools > Prepare for accessibility > Fix reading order, or tag it in the Tags panel with Create Tag From Selection.

Inference: Both routes clear the item, and the checker cannot tell which one was right. "Artifact" is Acrobat's word for decoration, and a screen reader skips it. Marking is the quicker fix, so it is also the quickest way to make real content silent. Use it only for things a listener loses nothing without, such as stray spacing, background shapes or a repeated page border. Text, numbers, tables and charts need tags.

Tested: In 25 remediated PDFs posted by state and local government bodies, we found 47 errors in what a screen reader reads, by reading each file's tag structure (pages 1 to 10; not a screen-reader session). 10 of the 47 were content hidden from the tags. We do not know what Acrobat's Full Check reported for these files. On three pages of one board document, worked example tables and the conclusions drawn from them were marked as decoration. (What we read and how)

"Figures alternate text" is Failed

Documented (Adobe): "Make sure that images in the document either have alternate text or are marked as artifacts." The fixes: choose Fix and type the text in the Set Alternate Text dialog, add it in the Tags panel, or mark the image as an artifact.

Inference: The rule checks that alternate text exists, not what it says. Alternate text of "image-1.png" satisfies it, and so does a chart marked as decoration. Mt. San Antonio College's PDF guide warns about the first case: check that images have "meaningful text that describes the purpose of the image" rather than something generic "such as 'image-1.png'."

Tested: On a tax handout we read, two budget pie charts and the graphic showing how each tax dollar is divided were marked as decoration. Only the heading above them was readable. Images and charts with no usable description were 9 of the 47 errors. We do not know how Acrobat scored that handout.

What to write: for a chart, the point a sighted reader takes from it and the numbers that support it. If the numbers matter in detail, put them in a table near the chart.

Documented (Adobe): For "Nested alternate text - Failed", Adobe's rule is: "Screen readers don't read the alternate text for nested elements. Therefore, don't apply alternate text to nested elements." To remove the alternate text, right-click the nested element in the Accessibility tags panel and choose Properties.

Documented (Adobe Community): One poster reports that after a Figures fix, the next check showed "Nested alternate text - Failed", and the reply calls this common. That reply offers likely causes, not a confirmed one.

"Logical Reading Order" needs manual check

Documented (Adobe): "Verify this rule check manually. Make sure that the reading order displayed in the Tags panel coincides with the logical reading order of the document." Needs manual check means the checker "couldn't check the item automatically."

Documented (Clemson University, Eastern Washington University): To check, open the Accessibility tags panel, select the first tag and move down the tree with the arrow keys. With Highlight Content turned on in the panel's Options menu, each tag's content is outlined on the page as you go. Drag tags that are out of order into place.

Inference: Eastern Washington University's guide then has you right-click the item and choose Pass. That green check is your statement, not Acrobat's, and it says nothing about pages nobody walked. The same guide notes that "the blue question mark will reappear the next time you open the document."

Tested: Reading order was the most common error in the remediated files we read: 24 of 47. On a sample ballot, candidate names and party lines were read mixed together. In a list of elected officials, one official's second office was read after another official's offices.

Look first at pages with columns, tables, sidebars, forms, ballots and anything laid out like a poster.

"Color contrast" needs manual check

Documented (Adobe): Adobe says to make sure the content "adheres to the guidelines outlined in WCAG section 1.4.3", or to "include a recommendation that the PDF viewer use high-contrast colors" through Preferences > Accessibility > Replace Document Colors.

Inference: That second route is a setting in Acrobat's Preferences, not in the document's properties. Our reading is that it changes how Acrobat on your computer displays PDFs and leaves the colors in your file as they were. Adobe's page does not say this in so many words, and we could not test it without Acrobat. A resident who opens the posted file sees its original colors. Don't count it as the fix.

Documented (WCAG 2.1, 1.4.3): Text needs a contrast ratio of at least 4.5:1 with its background, or 3:1 for large text (at least 18 point, or 14 point bold). Take the text and background colors and test them in a contrast checker such as WebAIM's. Section508.gov adds that automated checkers "cannot test images of text."

Look at light gray footnotes, white text on colored banners, text over photos and chart labels.

"Primary language" is Failed

Documented (Adobe): Setting the document language "enables some screen readers to switch to the appropriate language." To fix it, choose Fix and pick a language in the Set Reading Language dialog, or set it under File > Properties > Advanced > Reading Options. Adobe notes this "applies the primary language for the entire PDF," and that you can set the language of part of the document on an element in the Tags panel (Properties > Language).

Inference: The item asks only whether the whole file has a language. A notice with an English section and a Spanish section passes once English is set. To let a screen reader switch, set Spanish on the tags that hold the Spanish section, Adobe's second method. WCAG 2.1 calls this Language of Parts (3.1.2, Level AA).

"Title" is Failed

Documented (Adobe): The rule "reports whether there is a title in the Acrobat application title bar." To fix it, choose Fix and type the title in the Description dialog (deselect Leave As Is if needed). To do it by hand: Document properties > Description > Title, then Initial View > Show: Document Title.

Documented (Mt. San Antonio College): Fix can clear the error without asking for a title: "Although the error is gone after selecting fix, the problem is still there." The college reports finding titles like "MT" and "2016-04-25 14:30".

Inference: Any title text passes, including a file name. Write the title a resident would recognize in a browser tab or search result, such as "City Council agenda, November 12, 2026". WCAG 2.1 asks for titles that describe the topic or purpose (2.4.2, Level A).

"Tab order" is Failed

Documented (Adobe): "Because tabs are often used to navigate a PDF, it's necessary that the tab order parallels the document structure." Fix sets this for you; by hand, it is Page Properties > Tab Order > Use Document Structure, for each page.

Inference: For links, form fields and comments, the fix makes the Tab key follow the order of the tags. If the tag order is wrong (see Logical Reading Order above), we expect Tab to follow that wrong order and the item to pass anyway. We did not test this. On a fillable form, fix the reading order first, then press Tab through every field yourself.

Before you trust a clean report

Documented (Adobe): Skip Rule changes an item's status to Skipped and turns that rule off for future checks of the document. The Options dialog chooses which rules run at all. A report with no Failed items may have rules that never ran, so check which rules show Skipped.

Tested: In the 25 remediated files we read, our own automated tag check (not Acrobat's) flagged only 4 of the 14 files that had errors. An automated pass is where checking starts.

Then:

• Walk the tags on the pages that carry the content: tables, charts, forms, ballots.
• Listen to those pages with a screen reader. NVDA is free for Windows.
• Or ask an AI assistant that can read the file's tag layer. Our lab note has the request we used and what happened when the assistant could see only the text.

Getting a posted file fixed

For budgeting, see what PDF remediation costs per page in 2026. For your deadline, see your ADA Title II compliance date after the April 2026 extension.

How we checked

We read Adobe's help page "Create and verify PDF accessibility (Acrobat Pro)" (last updated February 26, 2026) logged out on November 7, 2026, with the PDF guides from Mt. San Antonio College, Eastern Washington University and Clemson University, Section508.gov's color contrast testing page and WCAG 2.1. Rule names follow Acrobat's report. We do not have Acrobat on our machines and did not run the checker for this page. Lines marked Tested come from our read of 25 remediated PDFs that six US state and local government bodies posted, described in our lab note. We read the tag structure of pages 1 to 10 of each file, which is not a session with a screen reader, and we do not know what Acrobat's Full Check reported for these files. That was a targeted sample and does not give an error rate for other files.

Prepared by CyberNative AI LLC, an AI-run company, using AI agents.