Official sources
These are the primary sources for the rule itself, the supporting guidance from DOJ, and the technical standards the rule references.
-
DOJ Fact Sheet: Web and Mobile App Accessibility Final Rule (opens external site)
Plain-language summary published by the Department of Justice's Civil Rights Division.
-
The final rule (89 Fed. Reg. 31,320 — April 24, 2024) [PDF] (opens external site)
The full Federal Register publication, including DOJ's preamble explaining how the rule applies in practice.
-
28 C.F.R. § 35.205 — Minimal-impact exception (opens external site)
The text of the minimal-impact exception that excuses small WCAG deviations not actually affecting access.
-
WCAG 2.1 — Web Content Accessibility Guidelines (opens external site)
The W3C standard the rule incorporates by reference. Level AA is the conformance level required.
-
WCAG at a Glance (opens external site)
A high-level summary of WCAG's four principles — perceivable, operable, understandable, robust — aimed at non-specialists.
-
Section508.gov (opens external site)
U.S. General Services Administration's hub for federal accessibility requirements. Useful for the "best meets" procurement analysis the Title II rule effectively imports.
Example government accessibility roadmaps
Three Colorado local governments developed digital-accessibility plans as part of their state HB21-1110 compliance. They're worth reading because they show what a credible, day-one roadmap actually looks like. None promises to fix everything immediately; each acknowledges the scope and outlines the approach.
-
Arapahoe County, CO — Digital Accessibility Plan [PDF] (opens external site)
A county-level roadmap covering web, applications, documents, and governance.
-
City of Centennial, CO — Digital Accessibility Plan [PDF] (opens external site)
A municipal plan with clear categorization of work types and a phased approach.
-
El Paso County, CO — Digital Accessibility (opens external site)
A public landing page tying the accessibility plan to user-facing information and feedback channels.
Frequently asked questions
Wasn't the deadline April 24, 2026? What happened?
The original 2024 rule set two staggered deadlines — April 24, 2026 for governments serving 50,000+ and April 26, 2027 for everyone else. On April 20, 2026, DOJ published an Interim Final Rule (RIN 1190-AA82) extending both deadlines by one year. The new dates are April 26, 2027 for 50,000+ entities and April 26, 2028 for smaller entities and special-district governments. The substantive rule did not change — only the dates. A public comment period on the IFR closes June 19, 2026.
Does the rule apply to us if our city is under 50,000?
Yes — but your effective date is April 26, 2028, not April 26, 2027. (Both dates reflect the one-year extension DOJ issued in its April 2026 Interim Final Rule.) If your entity is a "special-district government" (a single-purpose public entity like a transit, library, water, fire, or school district), the April 26, 2028 date applies regardless of the population served.
What's the difference between WCAG 2.1 and Title II compliance?
WCAG 2.1 Level AA is the technical standard the rule adopts. Title II compliance is the legal obligation. The difference matters because Title II preserves the undue burden, fundamental alteration, and minimal-impact defenses — meaning you can fall short of perfect WCAG conformance and still be in legal compliance, as long as you've done the work and documented it.
Do we have to remediate every PDF on our website?
No. The rule reaches documents currently used by the public to access programs, services, or activities. Documents that aren't in active use to deliver services aren't covered on day one. The right approach is to triage: separate active documents from archival, prioritize the active set, and offer an auxiliary aid (such as a human-agent service) for documents you haven't remediated yet.
What if our vendor's application isn't accessible?
You don't have to take the application down. DOJ acknowledged in the preamble to the final rule that not every third-party application would be accessible on day one and pointed governments toward the undue burden and fundamental alteration defenses. Document your vendor outreach, prioritize, and use the time those defenses give you. Replacement should be a last resort after the vendor has failed to engage meaningfully.
How do we conduct accessibility testing on dozens of vendor applications without spending hundreds of thousands of dollars?
You don't conduct a full WCAG audit on every application. You do lightweight functional testing on the priorities — can a person with a disability actually use the application for its intended purpose? — and you push detailed audit work to the vendor where appropriate. The minimal-impact exception and the undue burden defense are what make this approach legally defensible.
What does "best meets" mean in procurement?
When no commercial product fully conforms to WCAG 2.1 AA, you're obligated to acquire the most accessible product that meets your business needs and to document how you made that choice. This is the same "best meets" analysis Section 508 already requires of federal agencies, so most vendors that sell to government know how to support it.
Are automated accessibility scanners enough?
Not by themselves — but combined with periodic expert review and a sensible ruleset, they're a strong quality control system for the content side of your website. Where automated tools shine is exactly where content creators introduce issues: alt text, headings, contrast, list and table structure. Keep the ruleset focused; don't try to make scanners do interactive-component review they can't reliably do.
What should our accessibility statement say?
At minimum: that the entity is working toward WCAG 2.1 AA conformance under the ADA Title II rule, the status of its work, how a user can request accessible versions of content or report an accessibility barrier, and how the user can reach a human if they can't access the digital service. A link to your published roadmap signals diligence and gives the public somewhere to go.
Who enforces the rule?
The U.S. Department of Justice. Title II also creates a private right of action, so private plaintiffs can sue to enforce it. State attorneys general may also bring enforcement actions in some circumstances under state-law parallels.
What if we just need help getting started?
That's what most state and local government teams need — not a 200-page audit, but a partner who's done this work elsewhere and can shorten the learning curve. Reach out and we'll talk about what your team actually needs.
Selected reading from the Converge Accessibility blog
Articles from our team that go deeper on specific aspects of the rule and the surrounding legal landscape.
-
DOJ Delays the Title II Web Accessibility Deadline — Don't Sit Back (opens external site)
Ken Nakata's analysis of DOJ's April 2026 Interim Final Rule extending both deadlines by one year — the rationales offered, what may come next, and how to file a public comment before the June 19, 2026 close.
-
Getting Past the FUD: A Day-One Compliance Strategy (opens external site)
The full-length essay this site's Compliance Roadmap is adapted from. Includes the legal citations and additional commentary on each step.
-
How to Comply With DOJ's Seemingly Impossible Web Accessibility Regulation (opens external site)
An earlier deep dive on how the rule's defenses interact with each other and how to use them in practice.
-
DOJ Questioning the New Title II Web Regulation (opens external site)
What it means — and doesn't mean — when DOJ signals a possible regulatory revisit.
-
Accessibility Scanners vs. Manual Testing (opens external site)
Where automated tools work, where they don't, and how to set up the right combination of both.
-
All posts on the Converge Accessibility blog (opens external site)
Including the monthly Legal Update series and ongoing analysis from Ken Nakata, Jeff Singleton, and the team.
Looking for an answer that isn't here?
If you have a specific question about how the rule applies to your government, we'd be glad to help.