We use cookies to run the site. Measurement and advertising only if you allow it. Cookie Policy

Settings

You can change this any time under “Cookie settings” in the footer.

What do you allow?

Check whether your PDF is accessible — here, now, without uploading it.

Drop a file below and you get the verdict in a few seconds: whether it is tagged, whether it declares a language and a title, whether its images carry alt text. The check runs inside your browser — the file never leaves your computer, and you don't need an account.

On this page
  1. What this check tells you
  2. What it can't tell you
  3. How this compares to PAC, veraPDF and Acrobat
  4. If the check comes back bad

Or upload a document

Pick a PDF from your computer and we'll run the same accessibility check on it — right here.

The file is not uploaded — the check runs entirely in your browser.

What this check tells you

The in-browser check reads the file's structure and answers the questions that decide whether assistive technology can make sense of a document at all:

  • Is it tagged? An untagged PDF is a picture of a page to a screen reader. This is the single biggest divide in PDF accessibility.
  • Does it declare a language? Without it, a screen reader guesses — and reads a Hungarian paragraph through an English synthesizer.
  • Does it have a title, and is the viewer told to show it? This is why some documents open as final_v3_REALLY_final.pdf.
  • Do the images carry alternative descriptions?
  • Are the fonts embedded? If not, text extraction — the thing assistive technology depends on — can break.

What it can't tell you

No automated checker, ours included, can confirm that a document is accessible. The machine-checkable part of PDF/UA is roughly a third of the standard. The rest is judgment: whether an alt text actually describes the image, whether the reading order matches how a person would read the page, whether a table's headers mean what the layout implies.

A file that passes every automated check can still be unusable. A file that fails one can be fine after a minute of work. Treat any checker's output — PAC, veraPDF, Acrobat, ours — as a list of things to look at, not a certificate.

How this compares to PAC, veraPDF and Acrobat

PAC 2024 and veraPDF are the reference validators for PDF/UA, and both are free. They are more thorough than the check above: they walk all machine-testable checkpoints and hand back a detailed report. If you need the formal verdict, use them.

Where they stop is the repair. They tell you a text object isn't tagged; they don't tag it. That is the gap this service fills — and if you already have a validator report full of red items, our error reference explains what each message means and whether a tool can fix it.

If the check comes back bad

Most of what fails is mechanical, and mechanical problems have mechanical fixes: missing tags, undeclared language, absent document title, images without descriptions, a heading level skipped. Upload the file and you get a free analysis with the exact price before anything is spent — technical repair costs 1 credit per page, full reconstruction 3, and a file that turns out to already be compliant costs nothing.

The repaired file comes back tagged to PDF/UA-1 (ISO 14289-1), validated with veraPDF, with a report showing what changed.

See how the pipeline works or start with 20 free credits — no card, no sales call.