Section 508 and WCAG requirements for PDFs
Which accessibility rules apply to your PDFs depends on who you are and who you sell to. This is a plain-language summary of the main regimes, their deadlines, and what they require of a document in practice.
This page is general information, not legal advice. If enforcement risk matters to your organisation, talk to a lawyer who knows your jurisdiction.
The short version
Almost every accessibility regime in force today points at the same technical standard: WCAG 2.1 Level AA. For PDFs specifically, meeting it in practice means meeting PDF/UA (ISO 14289) — a tagged document with correct reading order, alternative text, table headers, a title, and a declared language.
So while the legal landscape is fragmented, the engineering target is not. Fix a document properly once and it satisfies all of them.
Section 508 — United States federal
Section 508 of the Rehabilitation Act requires federal agencies to make their electronic information accessible. It applies to agencies directly, and reaches contractors and vendors through procurement: if you sell software or documents to a federal agency, you will be asked to demonstrate conformance.
The standard incorporates WCAG 2.0 Level AA as the baseline for electronic documents. Vendors are typically asked for an Accessibility Conformance Report, often called a VPAT, describing how their product measures up.
ADA Title II — US state and local government
This is the rule that has most changed the landscape for schools, universities, cities, and counties. The Department of Justice set an explicit technical standard — WCAG 2.1 Level AA — with compliance dates:
- 26 April 2027 for public entities with 50,000 or more residents
- 2028 for smaller public entities
It covers web content and documents published on the web, which is why school districts with decades of board minutes and course materials online are suddenly interested in per-page remediation pricing.
Section 504 — federally funded healthcare and programmes
Rules under Section 504 of the Rehabilitation Act extend similar obligations to recipients of federal funding, including much of the healthcare sector, with a compliance date in May 2026 — sooner than the Title II dates, and frequently overlooked.
European Accessibility Act
The EAA has been enforceable since 28 June 2025. It applies to private businesses selling to consumers in the EU — e-commerce, banking, transport, e-books, and more — not only the public sector. That is the significant difference from the US regimes.
Penalties are set by each member state and can reach substantial sums, with figures such as €100,000 or a percentage of turnover appearing in national implementations. Enforcement actions have already begun.
The referenced standard is EN 301 549, which incorporates WCAG 2.1 AA and points to PDF/UA for documents.
What this means for a single PDF
Strip away the legal framing and a compliant PDF needs all of the following. Every one of these is checkable, and the free checker on this site tests the structural ones.
| Requirement | Standard | Automatically checkable? |
|---|---|---|
| Document is tagged with a structure tree | WCAG 1.3.1 | Yes |
| Reading order is logical | WCAG 1.3.2 | No — needs a human |
| Images have meaningful alternative text | WCAG 1.1.1 | Presence only |
| Tables identify header cells | WCAG 1.3.1 | Presence only |
| Document has a descriptive title | WCAG 2.4.2 | Yes |
| Language is declared | WCAG 3.1.1 | Yes |
| Headings are used and correctly nested | WCAG 1.3.1, 2.4.6 | Partly |
| Text is real text, not a scanned image | WCAG 1.1.1 | Yes |
| Colour contrast is sufficient | WCAG 1.4.3 | Not by this tool |
| Form fields are labelled | WCAG 1.3.1, 3.3.2 | Partly |
The honest caveat about automated testing
Automated checks — including ours — catch a meaningful share of accessibility problems, but published research consistently finds that automation alone identifies only a fraction of real barriers. The rest require judgement: is this reading order sensible, does this alt text convey what the image means, is this actually a heading?
Treat a clean automated result as a floor, not a ceiling. It means you have cleared the mechanical failures. It does not mean a person using a screen reader can use your document, and no honest vendor will tell you otherwise.
Where to start
- Inventory what you have. Run your PDFs through the checker to find out how many are untagged and how many are scans. Most organisations are surprised.
- Work out the budget using real remediation rates.
- Fix the pipeline before the archive — tag documents at the source so the problem stops growing.
- Triage the archive by what people actually open.