BYTETOOLS

PDF Accessibility Checker

Check a PDF for the structural basics of accessibility: tagging, a structure tree, a document language, a real title and alt text on every figure.

Drop a PDF here or click to browseThe file is inspected in your browser and never uploaded

What is the PDF Accessibility Checker?

Before a PDF goes on a public website it has to be usable with a screen reader, and a handful of structural entries decide whether that is even possible.

  • Seven structural checks against PDF/UA-1 (ISO 14289-1) and WCAG 2.1
  • Counts tagged figures that have neither alt text nor actual text
  • Checks the document title is set and shown in place of the file name
  • Flags encryption that can block assistive technology
  • Plain-text report you can copy or download
  • Runs entirely in your browser — nothing is uploaded

How to use the PDF Accessibility Checker

  1. 1

    Drop the PDF onto the upload area — the check runs immediately.

  2. 2

    Read the pass, fail and warning rows; each explains what was found and cites its standard.

  3. 3

    Look at the counters for checks passed, problems and pages.

  4. 4

    Copy or download the report as a text file to send to whoever produced the document.

About the PDF Accessibility Checker

Before a PDF goes on a public website it has to be usable with a screen reader, and a handful of structural entries decide whether that is even possible. This tool opens the file, walks its catalog and structure tree, and reports on each one with a pass, a fail or a “needs a look”.

It checks that the document declares itself as tagged, that a structure tree actually exists, that a language is set, that the title is filled in and shown instead of the file name, that every tagged figure carries alternative text, and that the tab order follows the tag tree. Each row cites the matching PDF/UA or WCAG checkpoint so you can take it to whoever owns the file.

These are structural checks only — not a substitute for PAC or Acrobat's full accessibility report, and certainly not for testing with a real screen reader. A machine can confirm that tags exist; only a person can confirm the reading order makes sense. The file is inspected in your browser and never uploaded.

Frequently asked questions

How do I know if a PDF is accessible?

Start with the structure: it must be tagged, have a structure tree, declare a language, carry a real title and give every image alternative text. This tool checks all of that in a few seconds. Passing it is necessary but not sufficient — reading order and heading levels still need a human eye.

What does “tagged PDF” actually mean?

A tagged PDF carries an invisible tree of structure elements — headings, paragraphs, lists, tables, figures — alongside the visual page. Screen readers use that tree to read the document in a sensible order instead of guessing from the layout.

Is this the same as PAC or Acrobat's accessibility checker?

No. Those run hundreds of checks including reading order, table headers and colour contrast. This tool covers the structural entries that a browser can inspect reliably, and it says so on the results page.

Why does my PDF fail the alternative text check?

Either the pictures were never tagged as figures at all, or they were tagged but the alt text entry was left empty. Both need fixing in the tool that produced the PDF — usually InDesign, Word or Acrobat.

Does a PDF need a language set even if it is in English?

Yes. Without a document language a screen reader falls back to the reader's own default voice, which may pronounce English text with, say, German phonetics. It is a one-field fix in the document properties.

Related tools