How to make an accessible PDF, step by step
From the source Word file to tags, reading order, alt text and a PDF/UA check — with a checklist.
Do it yourself: PDFs & documents
PDF/UA vs WCAG: which standard applies to your PDFs?
If you’re making PDFs accessible, you’ll run into two standards. They’re complementary, not competing.
WCAG: the legal benchmark
The Web Content Accessibility Guidelines define outcomes — text alternatives, meaningful sequence, contrast, keyboard access, labels — that apply to any digital content, including documents. US law references WCAG: the ADA Title II rule and HHS Section 504 rule require WCAG 2.1 AA for PDFs, and Section 508 requires WCAG 2.0 AA for electronic documents.
PDF/UA: the technical blueprint
PDF/UA (“Universal Accessibility”) is ISO 14289. PDF/UA-1 (ISO 14289-1) defines how a PDF file itself must be built so assistive technology can read it reliably: everything tagged, correct tag semantics, real text with Unicode mapping, artifacts marked, metadata present, fonts embedded. PDF/UA-2 (ISO 14289-2) updates it for the PDF 2.0 format.
The PDF Association’s Matterhorn Protocol turns PDF/UA-1 into 136 failure conditions; 87 can be checked by software (that’s what PAC checks) and the rest need human judgment.
How they fit together
| Aspect | WCAG 2.x | PDF/UA |
|---|---|---|
| Focus | What users experience | How the file is constructed |
| Applies to | Web pages, apps, documents | PDF files only |
| Referenced by US law | Yes | No (but widely used to demonstrate conformance) |
| Covers contrast, color, captions | Yes | No |
| Covers tag syntax, Unicode, metadata | Only indirectly | Yes |
| Testing tool | Manual + Acrobat checker | PAC, Matterhorn Protocol |
A PDF can conform to PDF/UA and still fail WCAG (for example, low contrast or meaningless alt text), and it can be usable without perfect PDF/UA syntax. Aim for both: PDF/UA for how it’s built, WCAG for how it works.
What we recommend
- Make WCAG 2.1 AA (or 2.2 AA) your compliance target.
- Use PDF/UA-1 and PAC as the technical quality bar for every file.
- Test with a screen reader, because neither checker can tell you whether the document makes sense.
That’s exactly how our PDF remediation team verifies every file.
Find out where you stand, in writing.
Send us a few URLs or sample PDFs. Within two business days you get a free, plain-English snapshot of your biggest accessibility risks and what it takes to fix them.