# PDF accessibility checker https://thedollscout.com/pdf-accessibility-checker Published by TDS Document Scout Updated: 2026-09-27 When to use it: Before publishing a report, handout or client deliverable. What you get: Page-level findings, manual review prompts, and CSV or JSON exports. What to check yourself: Reading order, image descriptions and the accuracy of tags require human review. This tool does not certify conformance. Files are processed in this browser. No file upload or account required. This is a preflight review, not a WCAG or PDF/UA certification. A detected tag or title does not prove that it is correct. The reader parses actual PDF objects with Mozilla PDF.js. It inspects title and language metadata, the tagged-document declaration, page text, exposed structure roles and interactive fields. Missing declarations and text-bearing pages without a structure tree are triage signals. Heading jumps, tables, forms and long documents without bookmarks are review prompts. No percentage accessibility score is calculated. Files are limited to 20 MB each, 10 per batch and 100 MB total. Inspection covers up to 200 pages per PDF and 600 per batch. Very large text pages are capped at 100,000 characters and 2,000,000 per document. Partial results are labelled. Text comparison aligns pages using normalized extracted text. Equal text does not prove equal layout, tags, links or images. Pages without usable text remain unknown. Reports are generated locally. Review checkboxes record a user assertion; they are not an independent audit. Original files are never rewritten. The image, JSON and time-zone tools publish their own methods, limits and worked examples on each tool page. Image output depends on the browser encoder; JSON comparisons preserve numeric text and compare arrays by index; meeting times use the browser’s time-zone database. What does a detected PDF tag tell me? It reports a tagged declaration or structure exposed by the PDF reader. A detected tag does not prove correct reading order, useful image descriptions or accessible tables. Review those separately. Can this checker certify WCAG or PDF/UA compliance? No. It is an automated preflight plus a record of your manual review. It does not certify compliance, repair tags or produce a percentage accessibility score. A result you can reproduce Download these fictional PDFs and run them in the tool above. The results below are generated from the same PDF reader used by the tool, so you can check the example yourself. Download these fictional PDFs and run them in the tool above. The results below are generated from the same PDF reader used by the tool, so you can check the example yourself. Check | Observed result | What to do next Document title | Fictional workshop handout | Check that the title describes the document; the tool does not test the viewer title setting. Default language declaration | en-US | Check that the declared language matches the content. Tagged-document declaration | Not detected | Inspect structure and reading order in an authoring or remediation tool. Original handout: https://thedollscout.com/document-assets/samples/sample-before.pdf Revised handout: https://thedollscout.com/document-assets/samples/sample-after.pdf Image-only sample: https://thedollscout.com/document-assets/samples/sample-image.pdf Link to this example: https://thedollscout.com/pdf-accessibility-checker#worked-example Download all sample results (JSON): https://thedollscout.com/document-assets/sample-results.json W3C PDF18 — document title: https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF18 W3C PDF16 — document language: https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF16 W3C PDF3 — reading and tab order: https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF3 Reference material - W3C: PDF reading order: https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF3 - W3C: text alternatives in PDF: https://www.w3.org/WAI/WCAG22/Techniques/pdf/PDF1 - Mozilla PDF.js: https://mozilla.github.io/pdf.js/