Section 508 (Rehabilitation Act)
Section 508 of the Rehabilitation Act of 1973 (amended) requires federal agencies and federal contractors to make their information and communication technology (ICT) accessible to people with disabilities. The current technical standards (Revised Section 508, effective January 2018) reference WCAG 2.0 Level AA as the conformance baseline. VPAT 2.5 INT is the standard documentation format.
Also called: Section 508, Section 508 of the Rehabilitation Act · Last updated: May 27, 2026 · By Joseph W. Anady
Why it matters.
Section 508 is the federal accessibility law that makes ADA-style requirements binding on federal agencies and federal contractors. Where ADA Title III applies broadly to private businesses, Section 508 specifically governs federal ICT procurement and use. Non-compliance creates contract risk for vendors and operational risk for agencies. Most federal ICT procurement now requires Section 508 conformance as a contract clause.
How it works.
The Revised Section 508 standards (effective January 18, 2018) align with WCAG 2.0 Level AA — the U.S. Access Board adopted WCAG 2.0 AA by reference rather than maintaining a separate U.S. standard. In practice, 2026-era federal procurement targets WCAG 2.2 AA (more rigorous than the WCAG 2.0 AA legal minimum) to future-proof. Conformance is documented via VPAT 2.5 INT.
2026 reality check.
Section 508 enforcement has intensified. Federal agencies face audit pressure to comply, and federal contractors face contract-clause obligations. Civil rights advocacy groups increasingly challenge non-conforming federal ICT via the Section 508 complaint process. Vendors with documented WCAG 2.2 AA conformance (exceeding the legal WCAG 2.0 AA baseline) have a procurement advantage.
Data points
- Section 508 of Rehabilitation Act of 1973 (amended)
- Revised Section 508 effective January 18, 2018
- Adopts WCAG 2.0 AA as conformance baseline (incorporated by reference)
- 2026 practitioner target: WCAG 2.2 AA (exceeds legal minimum)
- VPAT 2.5 INT is the standard documentation format
First-hand insight from ThatDeveloperGuy.
ThatDeveloperGuy delivers WCAG 2.2 AA conformance on every site we build, exceeding the Section 508 WCAG 2.0 AA baseline. Our methodology combines axe-core + Pa11y automated CI testing, manual NVDA + JAWS + VoiceOver screen reader testing, keyboard-only navigation verification, and design-system-level color contrast validation. VPAT documents are delivered for federal engagements. The Section 508 commitment is integral to our SDVOSB federal contracting positioning.
How TDG approaches it
TDG targets WCAG 2.2 AA (exceeds Section 508 WCAG 2.0 AA legal minimum), automated CI testing via axe-core + Pa11y, manual screen reader testing on NVDA + JAWS + VoiceOver, keyboard navigation verification, color contrast at design-system level, VPAT 2.5 INT documentation, quarterly post-launch accessibility reviews. The Section 508 + WCAG 2.2 AA stack is integral to our federal contracting eligibility under FAR Subpart 19.14.
Common mistakes.
- Confusing Section 508 (federal ICT) with ADA Title III (private business)
- Targeting WCAG 2.0 AA when WCAG 2.2 AA is the 2026 practitioner target
- Using accessibility overlays (don't satisfy Section 508 — federal courts have ruled)
- Skipping VPAT in proposals (federal CO's often require VPAT at proposal stage)
- Treating Section 508 as one-time conformance (must maintain through product lifecycle)
FAQ.
Who must comply with Section 508?
Federal agencies (in their ICT procurement and use) and federal contractors providing ICT to federal agencies. Indirect application via flowdown to subcontractors on federal contracts.
What's the difference between Section 508 and WCAG?
Section 508 is U.S. federal law. WCAG (Web Content Accessibility Guidelines) is the W3C international technical standard. Section 508 currently adopts WCAG 2.0 AA by reference. WCAG 2.2 AA is the 2026 practitioner target (exceeds the legal minimum).
Does Section 508 apply to my private business?
Only if you're selling ICT to federal agencies. For private business accessibility, ADA Title III applies (different but related law). Most practitioners target WCAG 2.2 AA as the standard for both.
How is Section 508 enforced?
Federal agencies face Office of Management and Budget audits. Federal contractors face contract clause obligations. Individuals can file Section 508 complaints with the Access Board or DOJ.
What about state-level accessibility laws?
Many states have their own accessibility laws (often referencing WCAG). California (Unruh Act), New York (Human Rights Law), and others actively enforce.
Maintained by Joseph W. Anady at ThatDeveloperGuy. Back to glossary · Suggest a term