answers.delivery

How-to · 3 min read

How to check a PDF for accessibility before you post it

You have a PDF ready to go on your site, like a price list, a policy or a brochure, and you need to know whether a screen reader user can actually read it. Your web pages may already pass a scan, but the PDF is a separate file with its own tags, reading order and alt text. Most people only find out it is broken when someone complains. And you would rather not upload a private document to a random service just to test it.

Published
17 Nov 2026
Delivery
No. 12
Topic
Work and office
Evidence
7 claims quoted from websiteaccessibilitychecker.net

01
Why it's hard

A PDF can look perfect on screen and still be a flat picture of text to assistive technology. Whether it works depends on hidden structure: tags, the order those tags are read in, alternative text on images and a declared document language. Opening the file in a viewer shows none of that, and the export settings in most writing tools are easy to get wrong. Full manual testing against PDF/UA takes a trained person and a lot of time, so small teams usually skip it and hope for the best. Website scanners do not help here either, because they read the HTML of a page and treat a linked PDF as just another download.

This part describes the usual way. It makes no claims about Website Accessibility Checker, so nothing is quoted here.

02
How Website Accessibility Checker does it

Website Accessibility Checker has a separate PDF tool next to its website scanner. It checks the file for PDF/UA tagging, reading order, alt text and language, and runs the part of the Matterhorn Protocol that a machine can test. The rest is not hidden from you: the report lists the checkpoints a person still has to verify. The file is parsed in memory and not saved to disk, which matters if the PDF holds internal or customer details.

Audit PDF/UA tagging, reading order, alt text and language.Quoted from websiteaccessibilitychecker.net
PDF audits cover 47 of the 136 Matterhorn Protocol checkpoints automaticallyQuoted from websiteaccessibilitychecker.net
PDF files are parsed in memory and never written to disk.Quoted from websiteaccessibilitychecker.net

03
Step by step

  1. 1Open the PDF Accessibility Checker from the tools list on the home page.
  2. 2Upload the final export of your document, not a draft, since tags often change between exports.
  3. 3Read the automated findings first: tagging, reading order, alt text and language.
  4. 4Go through the list of human-verification items the report adds at the end.
  5. 5Fix the source file, export again and run a second check before you publish.

04
Tips

Treat the automated result as the first pass, not the finish line. Only 47 of the 136 Matterhorn checkpoints are covered automatically, so a clean report still leaves items like meaningful alt text and logical heading order for a human to judge.

every report lists the remaining human-verification items.Quoted from websiteaccessibilitychecker.net

Fix problems in the original document (Word, InDesign or whatever you wrote it in) and export again. Patching tags inside the finished PDF works once, but the next export from the source brings the same errors back.

General advice. Not a claim about the product.

Download or save the report the same day you run it. Report links stay active for 24 hours, so a link pasted into a ticket on Monday may be dead by the time someone opens it later in the week.

Fair-use protection • Reports active for 24hQuoted from websiteaccessibilitychecker.net

Plan your checks around the daily cap. The free allocation is 10 audits per 24 hours, which is enough to test a document, fix it and test it again, but not to run every file in a large archive in one sitting.

10/10 audits remaining per 24hQuoted from websiteaccessibilitychecker.net

05
Questions

Is my PDF stored after the check?

No. The file is parsed in memory and is not written to disk.

PDF files are parsed in memory and never written to disk.Quoted from websiteaccessibilitychecker.net

Which PDF standards does it test against?

PDF/UA-1 and the Matterhorn Protocol, alongside the WCAG and Section 508 standards used for web pages.

PDF/UA-1 (ISO 14289-1)Quoted from websiteaccessibilitychecker.net

Does a passing PDF report mean the file is fully accessible?

No. Part of the Matterhorn Protocol needs a person, and the report lists those remaining items for you to check.

every report lists the remaining human-verification items.Quoted from websiteaccessibilitychecker.net

More from Website Accessibility Checker

All 2 answers