Document a public roadmap
Publish a high-level accessibility plan that explains how you'll approach existing apps, PDFs, new content, and procurement. It signals diligence to the public, regulators, and your own staff.
How to write your roadmap
For state, local & special-district governments
The ADA Title II web rule is closer than you think — and more manageable than you've heard.
A clear, plain-language resource for the public servants, communicators, and IT teams working to make their digital services accessible. Built by accessibility practitioners who do this work every day.
Update: DOJ extended both deadlines by one year
On April 20, 2026, the Department of Justice published an Interim Final Rule (RIN 1190-AA82) pushing both Title II web-rule deadlines back by twelve months. The substantive rule did not change — only the dates. A public comment period is open through June 19, 2026. Read Ken Nakata's analysis — and why you should keep working anyway (opens external site).
What this site is for
In April 2024, the U.S. Department of Justice finalized a rule under Title II of the Americans with Disabilities Act requiring state and local governments to make their web content and mobile apps accessible to people with disabilities. This site explains what the rule actually requires, breaks down the deadlines, and lays out a practical roadmap your team can start using today.
Two compliance deadlines
DOJ's April 2026 Interim Final Rule extended both deadlines by one year. Your deadline depends on the population your entity serves.
Upcoming
April 26, 2027
Governments serving 50,000 or more people
Includes state agencies and larger cities, counties, and public universities. Originally April 24, 2026 — extended by one year in DOJ's April 2026 Interim Final Rule.
Upcoming
April 26, 2028
Smaller governments & special-district governments
Smaller cities, towns, counties, and special-purpose districts (transit, water, fire, etc.). Originally April 26, 2027 — extended by one year in DOJ's April 2026 Interim Final Rule.
More time — but the obligation hasn't changed.
The deadline moved. The underlying duty to make web content and mobile apps accessible under Title II of the ADA did not. Governments that keep building credible, documented compliance programs through the extension period are right where they should be. The defenses built into Title II — undue burden, fundamental alteration, and minimal impact — still exist to protect thoughtful, resource-constrained efforts. Learn how the defenses work
A straightforward three-step approach
You don't need to make every page perfect by your deadline. You need a credible plan, a system for executing it, and the people trained to keep it going.
Implement the roadmap
Inventory your apps, engage your vendors, set up automated testing on your CMS, triage your PDF library, and bake accessibility into procurement. Use the legal defenses where they apply.
See the five categories of workTrain the right people
A short foundational module for everyone, and a deeper, role-specific module for the people who actually create web content and documents. That's where most accessibility issues are introduced — and prevented.
What good training looks likeCommon misconceptions about the rule
A lot of the fear circulating about the rule comes from reading the regulation at face value and skipping the parts that actually make it workable.
"Every page has to meet WCAG 2.1 AA on day one."
The rule's technical standard is WCAG 2.1 Level AA, but the legal obligation is compliance with Title II of the ADA — which includes the undue burden, fundamental alteration, and minimal impact defenses. Perfect WCAG compliance was never the bar.
"We have to remediate every historical PDF."
Only documents currently used by the public to access programs, services, or activities are subject to the rule on your effective date. Historical and archival material can be handled on a phased basis, and an auxiliary-aid plan covers the gap.
"We'll get sued the day we miss the deadline."
That hasn't been the pattern in Colorado, which has had a stricter state-level rule in force since 2024. Governments that publish a roadmap and document their work are in a strong defensive position.
"Automated scanners are useless."
Automated scanners can't catch everything — but they're very good at catching the issues content authors actually introduce: missing alt text, broken heading order, low contrast, bad table structure. Pair them with expert review and they work.
Start here
About the Rule
A plain-language walkthrough of what the regulation requires, who it covers, when it applies, and the defenses it preserves.
Understand the ruleCompliance Roadmap
The practical, step-by-step approach we recommend — adapted from work with state and local governments in Colorado and beyond.
See the roadmapResources & FAQ
Official DOJ resources, example government roadmaps, answers to the questions teams ask most often, and curated reading.
Browse resourcesNeed a partner for the work?
This site is published by the team at Converge Accessibility — practitioners who help state and local governments build credible, documented accessibility programs. If your team needs hands-on help, we're a phone call away.