How do I check if a PDF is accessible?

Run it through this checker for a quick structural check, fix the gaps it lists, then test the file with a screen reader. Formal conformance needs manual review and a PDF/UA validator.

Does a clean result mean my PDF meets WCAG or PDF/UA?

No. Automated checks cannot prove WCAG or PDF/UA conformance. A clean result means the basic structure is present, not that it is correct.

Does it check image alt text?

It finds images and checks whether the PDF is tagged. It does not read or judge alt text, so check that each meaningful image has accurate alt text yourself.

Why did I get a reading order warning?

Either the PDF has no tags, so there is no defined reading order, or text on some pages jumps around more than expected. Multi-column layouts often cause this. Look at those pages yourself.

Does the checker fix problems?

No. It only reports and does not change your PDF. Use the results to decide what to fix in the source file or a remediation tool.

Is the accessibility checker free?

Yes, with no sign-up. The PDF is checked in your browser, and the results and report are created on your device.

PDF Accessibility Checker

Check a PDF for language, title, tags, bookmarks, untagged images and likely reading-order problems, with the results on screen.

Select a PDF file

or drop it anywhere on this page, or paste

Opens in your browser. Nothing is uploaded.

PDF Accessibility Checker, free and private

Check PDF accessibility in your browser before you publish. The checker looks for the structure screen readers rely on: a title, a declared language, tags for headings and figures, and text that can be read out. None of this shows on screen, so a PDF can look perfect and still be unusable with a screen reader.

It runs 8 automated checks and lists each one on the result screen as Pass, Check or Fail, with a short explanation. You can also save the full report as HTML, Markdown or JSON. It is a quick first pass, not a WCAG or PDF/UA conformance test. It is free and the PDF is never uploaded.

How to check PDF accessibility

1
Add your PDF
Press Select a PDF or drop the file onto the page. The checks run straight away and the panel lists them as Failed, To check by hand and Passed, with page numbers where they apply.
2
Pick a report format
The tool reads the document structure and the text on every page.
3
Read the results
The result screen lists all 8 checks. Each shows Pass, Check or Fail and says what it found. If any check failed, the heading says how many issues were found.
4
Save the report, if you need it
Run the check, then press Download to keep a copy. It holds the same checks plus the limits of the test. HTML opens in any browser, Markdown suits issue trackers and JSON suits scripts.

Why use PDFToolz for this

8 checks in one pass

Title, language, tags, bookmarks, images, searchable text, probable reading order and the marked-content flag are checked together.

Results on screen

Every check is listed with its status and a reason, such as the declared language or how many pages have no text. No file to open first.

Clear about its limits

Check is used where an automated tool cannot be sure, and the report says what it cannot verify.

Checked on your device

Unpublished reports and contracts are checked in your browser. Nothing is uploaded.

What the PDF accessibility checker tests

Each check targets a common reason a PDF fails for screen reader users:

Document title: fails if the document properties have no title.
Document language: fails if no language is declared (the /Lang entry).
Tagged structure: fails if there is no tag tree. Tags tell assistive technology what is a heading, list, table or figure.
Bookmarks: marked Check if a document over 3 pages has none. Shorter documents pass.
Image alternatives: counts images on the pages. In an untagged PDF they fail, since alt text is unlikely. In a tagged PDF they are marked Check so you can review the alt text yourself.
Searchable text: marked Check if any page has no text, which usually means a scanned image that needs OCR.
Probable reading order: marked Check if the PDF is untagged, or if text on a page keeps jumping back up the page.
Marked-content flag: marked Check if the PDF does not declare itself as tagged (/MarkInfo /Marked true).

Fixing common failures

A missing title is the easiest fix. Add one with Edit metadata in PDF Metadata. Pages with no text can be made searchable with OCR PDF, though OCR adds a text layer, not tags.

Tags, language, alt text and bookmarks are best fixed in the source file. In Word, Google Docs or InDesign, use real heading styles, add alt text to images, set the document language, and turn on the tagged or accessible PDF option when exporting. For a PDF with no source file, a remediation tool such as Adobe Acrobat Pro can add or repair tags.

What an automated check cannot tell you

A pass means the basic structure is there, not that it is right. The checker cannot judge whether tags match the content, whether alt text is useful, how a screen reader behaves, whether colour contrast inside images is enough, or whether the reading order is the one you meant.

The reading order check guesses from text positions. Columns, sidebars and footnotes can trigger it on pages that work fine, so treat it as a prompt to look. For formal WCAG or PDF/UA conformance, test with a screen reader and a PDF/UA validator.

Frequently asked questions

Last reviewed October 1, 2026. See how we build and test our tools, or report an error.