PDF Accessibility Checker: How to Test a PDF
On this page
A PDF accessibility checker is a tool that reads a PDF’s internal structure and reports which accessibility requirements it meets and which it fails. It answers a narrow, mechanical question: does this file have the tags, language, title and metadata that assistive technology depends on? It is the fastest way to find out whether a file is even close, and the correct first step before any remediation work.
What does a PDF accessibility checker test?
Checkers verify what can be judged without a human. That includes:
- Whether a tag tree exists and which element types appear.
- Whether the document declares a language (
/Lang) and a title. - Whether images are marked as figures with alt text, or as artifacts.
- Whether tables have header cells and a proper structure.
- Whether the file claims PDF/UA conformance and whether that claim holds.
- Whether the metadata flag that tells a screen reader to use the title is set.
What no checker can judge is meaning: whether the alt text describes the image, whether the heading levels reflect the real outline, whether the reading order makes sense to a person. Those need a human or a screen reader. That is the line between automated checking and PDF accessibility testing.
Which free PDF accessibility checkers are worth using?
The tools that rank for this work are all free, and all of them only check:
| Tool | Platform | Best for |
|---|---|---|
| PAC 2024 | Windows desktop | A clear pass/fail screen and a detailed, human-readable report |
| veraPDF | Cross-platform, open source | Precise PDF/UA and PDF/A conformance validation |
| Adobe’s online accessibility checker | Browser | A quick free check that then directs you to Acrobat Pro |
PAC 2024 is the one most coordinators reach for because its report is easy to read. veraPDF is the stricter validator and is the better second opinion when a vendor claims a file is PDF/UA compliant. Adobe’s free online tool is genuinely useful for a first look, but its purpose is to show you what Acrobat Pro would fix, and Acrobat Pro is where the tagging tools live (Adobe’s guide). None of the three writes a single tag into your file.
The categories a checker reports map back to the WCAG success criteria a file has to meet. The WCAG and PDFs guide shows which criterion each category serves, and the PDF accessibility testing guide turns those categories into a repeatable procedure a team can follow.
What does “Tagged PDF: Failed” actually mean?
It is the most common line in a report and the one that matters most. “Tagged PDF: Failed” means the file has no usable structure tree, so a screen reader cannot tell a heading from a paragraph or a table cell from its header. It falls back to reading text in the order the objects sit in the file, which often does not match how a person reads the page.
Everything else tends to depend on this one result. If a file is untagged, then it also has no heading structure, no table headers and no figure alt text to report on, because there is nowhere to store them. Fixing “Tagged PDF: Failed” is the bulk of the work, and it is the part free checkers cannot do for you.
Why a checker can only report, never fix
Checking is a read operation; repairing is a write operation, and a much harder one. To fix a file, a tool has to decide which text is a heading, reconstruct the reading order across columns, set the language and title, and rebuild the structure tree without changing how the pages look. Adobe does this well in Acrobat Pro, at $19.99 a month, once you have learned the tags panel and the reading order tool.
That is the shape of the market: the free half of the job (checking) is solved, and the paid half (repairing a PDF you did not author) is where teams get stuck. A hosted tool such as TagRight does the write half and then hands you back to a checker: you tag the file, then confirm the result with PAC or veraPDF. The comparison of PDF accessibility tools covers the whole landscape, and the free tier is on the pricing page.
How do I read an accessibility report?
Read it in three passes:
- Structure first. Is “Tagged PDF” a pass? If not, stop; nothing downstream is meaningful yet.
- Metadata next. Language set? Title set, and does it look like a real title rather than a filename?
- Content checks. Images without alt text, tables without headers, contrast, and any “needs manual check” items the tool lists.
Then decide, per file: tag it, fix it by hand, or send it to a human service. A worked example from a remediation run on a 12-page policy document:
Language detected: en-US Document title: “Records Retention Policy 2026” Heading outline inferred: H1 “Records Retention Policy” → H2 “Scope” → H2 “Retention Schedule” → H2 “Disposal” Flagged for a human: 3 images need alt text; the retention table on page 5 has merged cells and should be verified; page 11 is a scanned signature page with no text layer.
A checker would tell you the original file failed on tags, language and title. The report above tells you what a remediation run fixed and what it left for a person. Together they are the two halves of the job. If you want the fixing steps, start with how to remediate a PDF or the full accessible PDF checklist, and try the free tier at tag a PDF free.
Frequently asked questions
What does a PDF accessibility checker test?
It reads the file's structure and reports on things a machine can verify: whether a tag tree exists, whether the document has a language and title, whether images lack alt text, whether a table has header cells, and whether the PDF claims PDF/UA conformance. It cannot judge whether alt text is meaningful.
What does Tagged PDF: Failed mean?
It means the file has no usable structure tree, so assistive technology has to guess at the reading order from the visual layout. It is the single most common failure and the one that matters most, because almost everything else depends on tags being present.
Is PAC 2024 free?
Yes. PAC 2024 (PDF Accessibility Checker) is free from the PDF/UA Foundation, but it is a Windows desktop application and it only checks. It reports failures and does not repair them.
Can an accessibility checker fix my PDF?
No. A checker's job is to report, not to repair. Free tools tell you what is wrong and, in Adobe's case, point you to Acrobat Pro to fix it. Writing tags into a PDF you did not author requires a remediation tool or a person.
Which is more accurate, PAC or veraPDF?
Both are strong and standards-based. veraPDF validates PDF/UA conformance precisely; PAC 2024 gives a fuller human-readable report and a clear pass/fail screen. Many teams run PAC for the report and veraPDF for a second, independent opinion.