PDF Accessibility Checker
Check your PDFs
Choose your files, see what needs a closer look, and take the review notes with you.
Automated findings guide your review; check reading order and meaning by hand.
Choose your PDFs
Files stay in this browserUp to 20 PDFs · 20 MiB each · 100 MiB per batch · 200 pages each
Your PDFs stay in this browser. They are not uploaded or saved.
Choose files or try the sample batch.
PDF check results
Reports include filenames and document details. Review them before sharing.
What else to check
Keep these manual checks with the automated findings.
References: W3C PDF18 (title), PDF16 (language), PDF3 (reading order); Mozilla PDF.js page API.
Find your next improvements
- Document titles, language settings and text
- Image descriptions in tagged PDFs
- Bookmarks for navigating longer documents
Keep the results
Save each finding and its next step in a spreadsheet, or print a report to share. Page references and unfinished checks stay with the results.
Details about the checks
Mozilla PDF.js reads the document structure. The Marked flag is a declaration; a page structure tree is a presence signal. Neither establishes correct tagging. Text extraction does not confirm text recognition accuracy, visible text, or reading order.
Document language is the catalog’s /Lang value, not a detected language. A title’s presence does not confirm its usefulness or that a viewer displays it. A parser limitation can prevent a property from being retrieved.
Each file has a 60-second time limit. Password-protected files and unsupported XFA forms need a different tool. Limits, cancellations and parser errors remain in the exported report.
Primary references: PDF.js document API, PDF.js page API, and W3C techniques for document titles, language and reading order.