Skip to main content

Why did my PDF fail the accessibility check?

A PDF fails an accessibility check when a machine-checkable rule is not met. The usual causes are no tags, no title, no language, images without alt text, form fields without a name and fonts that cannot be read as text. Each one below is explained in plain English with its fix.

or drop it here. Free: up to 30 pages and 20 MB, no sign-up. The file is deleted as soon as the check finishes.

What are the most common reasons a PDF fails an accessibility check?

The most common failures are an untagged document, a missing title, a missing language, form fields without an accessible name, fonts without a Unicode map and PDF/UA-1 rule failures.

The table uses the wording of the PDF Checkup report (read 2026-11-20); numbers in the report lines change with your file.

Common failing checks in the PDF Checkup report
Report lineWhat it meansHow to fix it
Document is not taggedWithout tags, screen readers cannot tell headings, lists, tables or reading order apart (WCAG 1.3.1, 1.3.2).Re-export from the source with tags turned on, or auto-tag in Acrobat Pro. Not fixed by PDF Checkup.
Document has no titleThe document has no descriptive title for a screen reader to announce (WCAG 2.4.2).Add a descriptive title. Fixed automatically with a remediation pack.
Document language is not setScreen readers may pronounce the text with the wrong voice (WCAG 3.1.1).Set the language. Fixed automatically with a remediation pack.
N of N form fields have no accessible nameA screen reader cannot tell what to type into the field (WCAG 1.3.1, 3.3.2, 4.1.2).Give each field a tooltip that says what to enter. Needs a tagging tool; not fixed by PDF Checkup.
Some text cannot be converted to readable charactersA font has no Unicode map, so screen readers may read gibberish (WCAG 1.3.1).Re-export from the source document.
N PDF/UA-1 machine rules fail (N places)The full PDF/UA-1 (ISO 14289-1) rule set run with veraPDF found failures; they are listed rule by rule, with pages, under the report.Depends on the rule: the report labels each rule as fixed automatically or manual.

What other checks can make a PDF fail?

Besides the failures above, a PDF can fail for scanned pages with no real text, images without alt text, links without a description, wrong tab order, missing table header cells and missing bookmarks.

  • Scanned pages with no real text (WCAG 1.4.5): the page is a picture of text and needs OCR.
  • Images without alt text, or with placeholders such as “image” (WCAG 1.1.1): fixed with AI-drafted alt text that you review, in a remediation pack.
  • Links without a description (WCAG 2.4.4) and tab order that does not follow the structure (WCAG 2.4.3): fixed automatically with a remediation pack.
  • Table header cells and headings (WCAG 1.3.1, 2.4.6), and bookmarks for documents over 20 pages (WCAG 2.4.5): listed in the report; table structure needs the source file or a tagging tool.

Which PDF accessibility failures can PDF Checkup fix automatically?

With a remediation pack, PDF Checkup fixes the document title, DisplayDocTitle, document language, the tagged flag, link descriptions and structure tab order automatically, and drafts alt text with AI for you to review.

Untagged documents, wrong reading order, table structure and fonts need the source file or a tagging tool such as Acrobat Pro; the report says which issues those are.

What should I fix first when my PDF fails the check?

Fix the tags first, because without tags there is nothing for alt text or reading order to attach to.

  1. If the report says the document is not tagged, re-export it from Word, Google Docs or InDesign with tags turned on, or auto-tag it in Acrobat Pro.
  2. Run the PDF through the free checker again and read the failing checks from the top.
  3. Fix the title, language, link descriptions, tab order and alt text with a remediation pack, or by hand.
  4. Finish with a human pass for reading order, alt text quality and contrast, which no automated check can confirm.

Why does my PDF fail when it looks fine on screen?

A PDF can look correct on screen and still fail, because the checks test the structure behind the page (tags, title, language, alt text) that screen readers use, not how the page looks.

How much does PDF Checkup cost?

PDF Checkup is free to check a PDF of up to 30 pages and 20 MB, and fixing a PDF costs $29 for a 50-page pack or $99 for a 300-page pack, paid once and valid 12 months.

Free checker

$0

  • WCAG 2.1 AA and PDF/UA-1 report on screen
  • Issues by page, in plain English
  • Up to 30 pages and 20 MB per file
  • No account, files deleted after the check

Remediation packs

  • Automatic fixes: title, language, link descriptions, tab order, tagged flag
  • AI-suggested alt text for images, reviewed by you before it is written into the file
  • Downloadable compliance report PDF (WCAG 2.1 AA and PDF/UA-1 results; the report itself passes PDF/UA-1)
  • Files up to 500 pages and 60 MB. One credit per page, charged once per document
  • No subscription. 14-day refund if you change your mind

Frequently asked questions

Does failing the check mean my PDF is not ADA or Section 508 compliant?

A failing check means a machine-checkable rule is not met, which is a to-do item, and passing every check does not prove compliance either. A person still has to confirm reading order, alt text quality, colour contrast and link wording. This site does not give legal advice.

Where can I see which pages a failure is on?

Each failing check in the PDF Checkup report lists the pages where it occurs, and the technical PDF/UA-1 results list every failed rule with its pages.

Does passing this checker make my PDF ADA or WCAG compliant?

No automated tool can prove that. Machine checks catch missing tags, titles, language, alt text and many PDF/UA errors, but a person still has to confirm reading order, alt text quality, colour contrast and meaningful link text. Use the report as your to-do list and keep a human review step. This site does not give legal advice.