Section 508: federal document accessibility, explained
Section 508 of the Rehabilitation Act requires US federal agencies to make the information and communication technology they develop, procure, maintain or use — websites, software and electronic documents alike — accessible to people with disabilities. Since the revised 508 standards took effect on January 18, 2018, the enforceable technical benchmark has been WCAG 2.0 Level AA.
The rule
What is Section 508 of the Rehabilitation Act?
Section 508 is the federal law that requires US federal agencies to make the information and communication technology they develop, procure, maintain or use accessible to people with disabilities. The US Access Board writes the technical standards; the current revised 508 standards were published in January 2017 and took effect on January 18, 2018.
Congress added Section 508 to the Rehabilitation Act and strengthened it in 1998 to attach enforceable standards and a complaint process to federal technology purchases. The 2017 refresh modernized those standards around a single idea: instead of bespoke federal criteria, accessibility of web and document content is measured against W3C's WCAG 2.0.
Who is covered
Who must comply with Section 508?
Federal agencies and departments comply directly: Section 508 covers the ICT they develop, procure, maintain or use. Vendors are pulled in through procurement — when an agency buys software, platforms or document services, the acquisition rules require the delivered technology to meet the revised 508 standards, which is why solicitations ask for an Accessibility Conformance Report.
| You are | Section 508 | Also covered by |
|---|---|---|
| A federal executive agency or department | Yes — directly | None |
| The US Postal Service and other entities the statute names | Yes | None |
| A vendor selling ICT — including document remediation — to federal buyers | Yes — through procurement | None |
| A state accepting Assistive Technology Act funds | By assurance | ADA Title II |
| A state or local government | Not directly | ADA Title II — WCAG 2.1 AA by April 26, 2027 or April 26, 2028 |
| A private business | No | Other law |
Many states adopt 508-style or WCAG standards in their own law; Section508.gov lists them.
The standard
What technical standard does Section 508 require?
The revised 508 standards incorporate WCAG 2.0 Level A and Level AA success criteria by reference, and apply them to web content and to non-web electronic documents alike. A federal PDF, word processor file or presentation must meet the same testable criteria as a federal web page — tagged structure, reading order, alternative text, contrast, title and language.
The document obligation comes from provision E205 of the standards: public-facing electronic content, and nine categories of official agency communication even when not public-facing, must conform. That is why 'we only publish it as a PDF' is not an exemption — the format is covered exactly like HTML.
Side by side
How is Section 508 different from ADA Title II?
Section 508 covers federal agencies and their ICT purchases, and has required WCAG 2.0 Level AA since January 2018. The Department of Justice’s ADA Title II rule covers state and local governments, applies the newer WCAG 2.1 Level AA, and phases in on April 26, 2027 and April 26, 2028. An organization can sit under both regimes at once.
| Comparison | Section 508 | ADA Title II |
|---|---|---|
| Covers | Federal agencies and their ICT vendors | Every state and local government entity |
| Standard | WCAG 2.0 Level AA | WCAG 2.1 Level AA |
| In force | Since January 18, 2018, no phase-in | April 26, 2027 (50,000 or more people) / April 26, 2028 |
| Written by | US Access Board (36 CFR Part 1194) | Department of Justice (28 CFR Part 35) |
| Enforced through | Agency complaints (29 U.S.C. § 794d(f)); procurement rejection | DOJ or federal-agency complaints; private lawsuits |
| Documents covered | Public-facing content plus nine categories of official communication (E205) | Web content including PDFs, with the 28 CFR 35.201 exceptions |
Who is covered
Section 508: federal agencies and the vendors that sell ICT to them. ADA Title II: every state and local government entity — cities, counties, school districts, public universities, special districts.
Which WCAG version
Section 508 incorporates WCAG 2.0 Level AA. The Title II rule requires WCAG 2.1 Level AA, which adds criteria for mobile use and low vision on top of 2.0 — content meeting 2.1 AA also satisfies 2.0 AA.
When it applies
The revised 508 standards have been in force since January 18, 2018 — there is no future phase-in. Title II compliance dates arrive on April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for everyone else.
Documents
What does Section 508 mean for PDFs and documents?
Electronic documents that a federal agency posts publicly, or circulates as official agency communication, must conform to WCAG 2.0 Level AA. In practice that means tagged PDFs with a correct reading order, a set document title and language, alternative text on meaningful images, labeled form fields and sufficient contrast in the text layer.
Scanned, image-only PDFs fail those criteria by default and need OCR plus tagging before they can conform. Agencies buying remediation instead of doing it in-house should note that the purchased service and its output are themselves ICT deliverables under the standards — ask vendors for per-file verification evidence, not just a marketing claim.
The work
What should a federal team do next?
Inventory the documents on your public sites and in your official communication channels first, because the backlog is usually far larger than assumed. Then prioritize public-facing and actively used files, remediate them to WCAG 2.0 AA — in practice, to WCAG 2.1 AA and PDF/UA so one pass satisfies every regime — and keep verification evidence per file.
Inventory: enumerate every PDF and Office document on your public domains and in covered official communications.
Prioritize: public-facing content and documents people currently need come first.
Remediate and verify: bring files to WCAG conformance and keep a machine verification report for each one.
Fix procurement: require conformance and per-file verification evidence in every ICT and document contract.
Procurement
If you are buying remediation, not doing it
Under the revised standards, the service you buy and the files it returns are themselves ICT deliverables. A vendor’s accessibility claim is part of what you procure, and you can require evidence for it.
| Ask for | Why |
|---|---|
| An ACR with criterion-by-criterion results | A blanket “508 compliant” is not a conformance report |
| Per-file verification evidence, not a sample | A sample proves the vendor can do it once |
| Which validator, and which version | “Industry-leading checker” is not a validator |
| What happens to files that fail | The answer reveals whether failures are detected at all |
| Whether scanned documents are in scope, and at what price | Image-only PDFs are the expensive part and the usual surprise |
What we do: every remediated file is checked against PDF/UA-1 with veraPDF(opens in new tab), an independent open-source validator we did not write; the result goes on the file’s verification report, and a document that fails its level’s verification is not charged. Our own ACR is a working draft, criterion by criterion, not yet a published report; its status is on our security page.
FAQ
Section 508 document questions, answered
General information, not legal advice: which rule applies to you, and when, is a question for your counsel.
Does Section 508 apply to state governments or federally funded organizations?
Not directly — Section 508 binds federal agencies. But states accepting Assistive Technology Act funds assure 508 compliance, many states wrote 508-style standards into their own law, and every state and local entity is separately covered by ADA Title II, which requires WCAG 2.1 AA by April 2027 or April 2028.
Does Section 508 require WCAG 2.0 or WCAG 2.1?
The revised 508 standards incorporate WCAG 2.0 Level A and AA. WCAG 2.1 is not yet required, but because 2.1 contains every 2.0 criterion, remediating documents to WCAG 2.1 AA — the ADA Title II and HHS standard — automatically satisfies Section 508's technical requirement as well.
What is a VPAT or ACR, and when is one needed?
A VPAT (Voluntary Product Accessibility Template) is the standard form a vendor fills in to produce an ACR — an Accessibility Conformance Report describing how a product meets the 508 standards. Federal buyers request one during procurement to compare offers; a credible ACR reports criterion-by-criterion results, not a blanket 'compliant'.
Do old PDFs on a federal website have to be fixed?
Legacy ICT that complied with the original 508 standards and has not been altered since January 18, 2018 has a safe harbor. Altering, republishing or updating a document ends that protection, and any content people currently need should be treated as active — the safe harbor is a narrow exception, not a backlog amnesty.
How is Section 508 enforced?
Through agency complaint processes and the Rehabilitation Act's administrative remedies: individuals can file a Section 508 complaint with the agency concerned, and procurement gives the standards day-to-day teeth — non-conforming offers can be rejected. Agencies also report government-wide 508 conformance in recurring assessments, which makes document backlogs visible.
Sources
Every regulatory claim on this page is cited to one of these primary sources.
- Section508.gov — GSA Government-wide IT Accessibility Program
- US Access Board — Revised Section 508 Standards (Information and Communication Technology)
- 29 U.S.C. § 794d — Section 508 of the Rehabilitation Act (Cornell LII)
- Federal Register, April 20, 2026 — Interim final rule: Extension of Compliance Dates for Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (91 FR 20902). This rule sets both compliance dates.
- eCFR — 28 CFR 35.200, the web and mobile accessibility requirements as currently in force
- W3C — Web Content Accessibility Guidelines (WCAG) 2.1
- Federal Register, April 24, 2024 — Final rule: Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (89 FR 31320). Creates the obligation and sets WCAG 2.1 AA; the compliance dates printed in it were later extended by one year.
Changelog
- Notice sources corrected; routing, comparison and procurement tables, the standards figure and product links added.
- Initial publication.
Reviewed quarterly, and whenever a cited source changes. Next review: December 18, 2026.