Section 508 of the Rehabilitation Act (29 U.S.C. 794d) + DOJ Title II rule

Record: software-cert-027 — Section 508 of the Rehabilitation Act + DOJ Title II rule
Issuing body / enforcer: Section 508 — U.S. Access Board (standards), enforced via federal procurement and agency accountability (GSA/OMB oversight); Title II — DOJ Civil Rights Division
Jurisdiction: United States — federal agencies and federal contractors (508); state and local governments (Title II)
Record type / importance: regulation / license
Last verified: 2026-09-30

What it is

Two related but distinct U.S. digital-accessibility regimes that software engineers selling to or building for government must satisfy. Section 508 requires federal agencies' electronic and information technology (ICT) to be accessible, which flows down to vendors through procurement: you cannot sell software to the federal government without a credible accessibility conformance claim (VPAT/ACR). The DOJ Title II rule (2024) separately mandates WCAG 2.1 AA for state and local government web content and mobile apps — the first U.S. regulation to name a WCAG version for public-sector digital services.

Scope: who/what it applies to, triggers, thresholds

Section 508: all federal agencies' ICT — software, websites, documents, kiosks, telecom. Contractors are bound through FAR accessibility clauses; a VPAT (Voluntary Product Accessibility Template, now called Accessibility Conformance Report) is the standard evidence artifact in solicitations.
Title II: state and local governments, including public universities, transit agencies, courts, and special districts — covering their websites and mobile apps.
Technical standards: Section 508 incorporates the Revised 508 Standards (2017 refresh, effective Jan 2018), which still reference WCAG 2.0 AA — one full WCAG generation behind. The Title II rule adopts WCAG 2.1 Level AA (28 CFR Part 35).
Title II compliance dates (extended April 2026 by interim final rule): entities serving ≥50,000 people: April 26, 2027; <50,000 and special districts: April 26, 2028. Five narrow exceptions: archived content, pre-existing conventional electronic documents, third-party-posted content (no contractual arrangement), password-protected individualized documents, pre-existing social media posts.

Key requirements and compliance obligations

508: agencies must procure and maintain accessible ICT; vendors must deliver ACRs, remediate barriers, and support agency testing. The GSA's FY2025 governmentwide assessment scored agency alignment at 1.96 out of 5 — compliance is broadly poor, and GSA's recommendations push Congress to strengthen enforcement and require independent validation for high-use public-facing products. Practical vendor obligations: accurate ACRs (misrepresentation is a procurement risk), accessible authoring workflows, and remediation roadmaps.
Title II: covered entities must ensure web content and mobile apps conform to WCAG 2.1 AA (50 success criteria) — including documents, forms, videos (captions), and third-party embedded content they control. The extension rationale (DOJ, April 2026): generative AI has not delivered reliable automated remediation at scale, and entity resources fell short of 2024 expectations.
ADA Title III (private sector): no WCAG regulation — obligations arise through litigation (notably Robles v. Domino's), with WCAG 2.1 AA as the de facto settlement standard. Kept distinct here because the record covers 508 + Title II; the Title III brief is separate.

Penalties and consequences

508: no fixed penalty schedule — consequences run through procurement (lost awards, contract termination), agency complaints, and potential False Claims exposure for materially false ACRs.
Title II: DOJ enforcement actions and settlement agreements; private suits for injunctive relief and damages. No per-violation fine schedule in the rule itself.

Version/edition status and LIVE changes (verified 2026-09-30)

Section 508 still references WCAG 2.0 AA. No Access Board rulemaking to adopt 2.1/2.2 has been announced as of mid-2026; commentary predicting a 2026 update did not materialize — check access-board.gov/ict directly. The Section 508 Refresh Act (S.4766, 118th Congress) did not become law.
Title II dates moved: the April 2026 interim final rule (91 FR 20902) extended both deadlines by one year (now Apr 2027 / Apr 2028); comment period closed June 2026. The rule survived a change of administration — treat it as durable, with no basis to expect a second extension.
Net effect: U.S. federal procurement (WCAG 2.0) is now a generation behind state/local government (WCAG 2.1); vendors should build to 2.1/2.2 AA regardless, since VPATs are increasingly requested against newer versions.

None of the catalogue's software certifications (AWS SA Pro, DevOps Pro, GCP Architect, CKA, CISSP) test accessibility content. Accessibility competence sits with specialist credentials outside the catalogue's flagship tier — a genuine coverage gap for government-facing software engineers.

Honest flags

The Title II extension dates are well-corroborated (Federal Register 91 FR 20902, DOJ ada.gov). The "no 508 rulemaking announced" status reflects practitioner monitoring as of mid-2026, not an official Access Board statement of intent.

Original ETS reference writing, verified against public sources on 2026-09-30. Thin sourcing is flagged inline. Not legal advice — confirm current editions with the issuing body.

Section 508 of the Rehabilitation Act (29 U.S.C. 794d) + DOJ Title II rule