Paperly
Upload PDF

PDF Accessibility Checker

Check title, language, tags and text layer.

Check a PDF for accessibility basics: document title, language declaration, tagged structure, selectable text and form fields. Results are labeled PASS, FAIL or NOT CHECKABLE — honestly.

Your files are processed locally in your browser. Nothing is uploaded to a server, ever.

Tip

Drop your file here or click to browse. Everything is processed on this device — nothing is uploaded.

Quick answers

What does this tool do?
Check title, language, tags and text layer. Check a PDF for accessibility basics: document title, language declaration, tagged structure, selectable text and form fields. Results are labeled PASS, FAIL or NOT CHECKABLE — honestly..
Is it free?
Yes — free and unlimited, with no account required and no watermark on the result.
What files are supported?
PDF files, up to 100 MB each.
Where is my file processed?
Entirely in your browser. Your file never leaves your device — nothing is uploaded to a server.
What are the limitations?
Automated subset only; tagged-structure correctness and reading order require manual verification.
What happens if processing fails?
You get a clear message explaining what went wrong and how to fix it (try another file, check the format, or start over). Your original file is never touched.

How to PDF Accessibility Checker

  1. Upload the PDF to check.
  2. Click "Process" — accessibility basics are measured.
  3. Download the report.
  4. Use the results as a starting point for screen-reader testing.

Frequently asked questions

No — automated checks cover a subset. Full compliance requires manual review with a screen reader.

Common problems and fixes

  • Document properties look wrong or stale

    Why: metadata is whatever the creating software wrote — it can be outdated or edited arbitrarily.

    Fix: trust the structural checks (pages, sizes, fonts) as ground truth; clean metadata separately if it matters.

  • The accessibility checker lists many issues

    Why: older PDFs were exported without tagged structure, which screen readers need.

    Fix: re-export from the source app with "tagged PDF" enabled, then re-check.

  • An encrypted file cannot be analysed

    Why: encrypted documents must be unlocked before any tool can parse them.

    Fix: remove protection first if you own the password — tools cannot and should not bypass encryption.

Who uses PDF Accessibility Checker?

  • Compliance teams — checking PDF/A conformance and tagging before documents go to the archive.
  • Legal review — inspecting metadata before a document is released or filed.
  • PDF producers — QA on generated output — page sizes, fonts embedded, structure intact.