ADA Title II April 24 Deadline: What Government Websites Must Do NOW
The DOJ's ADA Title II WCAG 2.1 AA deadline is April 24, 2026 — 46 days away. Every state and local government serving 50,000+ residents must comply. Here's what it means, what's at stake, and how to check your site fast.
The deadline is not a rumor. April 24, 2026 is when the DOJ's ADA Title II rule takes effect for every state and local government entity in the US serving populations of 50,000 or more. That means cities, counties, public universities, transit agencies, school districts, water utilities, and parks departments — all of them.
If your web team hasn't started, you have 46 days.
What Happened and Why It Matters
In April 2024, the U.S. Department of Justice finalized a rule under Title II of the Americans with Disabilities Act requiring government entities to make their public-facing websites and mobile applications meet WCAG 2.1 Level AA — the internationally recognized standard for accessible web design.
This isn't new law. Title II has always prohibited discrimination against people with disabilities by government entities. What's new is a clear, enforceable technical standard. For the first time, "accessible" has a specific, auditable definition: pass WCAG 2.1 AA or you're out of compliance.
The DOJ has been enforcing Title II accessibility obligations for years through complaint investigations and settlement agreements. The April 24 deadline makes the exposure much more concrete — and plaintiff attorneys have already begun scheduling automated audit runs for April 25.
Who Must Comply by April 24, 2026
The first compliance tier covers government entities serving populations of 50,000 or more:
- Cities and municipalities — any city with 50,000+ residents
- County governments — most mid-to-large counties across all 50 states
- State agencies — departments of transportation, health, education, housing, and more
- Public universities and community colleges serving large populations
- Special districts — transit authorities, water districts, regional parks
There are an estimated 5,000+ entities in scope for the April 24 deadline. Smaller entities (under 50,000 population) face a second deadline of April 26, 2027, but many are choosing to comply now to avoid future exposure.
What WCAG 2.1 Level AA Actually Requires
WCAG 2.1 AA is a technical standard with 50 specific success criteria across four principles. In plain terms, your website must be:
Perceivable — All content must be available in multiple formats. Images need alt text. Videos need captions. Color can't be the only way information is conveyed.
Operable — All functionality must work with keyboard navigation alone. No keyboard traps. Interactive elements must be reachable and usable without a mouse.
Understandable — Language must be identified. Error messages must explain what went wrong and how to fix it. Navigation must be consistent.
Robust — HTML must be valid and parseable by assistive technologies. Interactive components must follow ARIA authoring practices.
The most common violations we find scanning government sites:
- Missing or empty image alt text
- Form inputs without labels
- Low color contrast (fails 4.5:1 ratio requirement)
- Focus indicators missing or invisible
- PDFs not tagged for screen reader navigation
- Inaccessible dropdown navigation menus
- Missing skip-navigation links
- Page titles that don't describe the current page
What's at Stake for Non-Compliance
Non-compliance with the April 24 deadline creates meaningful legal exposure:
- Federal complaints — Any resident can file a complaint with the DOJ's Civil Rights Division. The DOJ investigates and can compel compliance.
- Private lawsuits — Title II allows private citizens to sue government entities for discrimination. Plaintiff firms are actively targeting non-compliant sites.
- Settlement agreements — DOJ settlements typically require 18-24 months of monitored remediation, third-party audits, and staff training — far more disruptive and expensive than proactive compliance.
The DOJ has settled cases against cities, counties, universities, and transit agencies. The April 24 deadline concentrates attention. Automated scanning tools can identify non-compliant sites at scale in hours.
We Scanned Six Government Sites Last Week
To understand the real landscape, we ran AccessiGuard on six mid-size US city websites that fall under the April 24 rule. Every single one had violations. Here's what we found:
| City | Score | Critical Issues | Status |
|---|---|---|---|
| Waco, TX | 55/100 | 3 serious | 🔴 High risk |
| Pomona, CA | 77/100 | 1 critical | 🟡 Moderate |
| Clovis, CA | 77/100 | 4 serious | 🟡 Moderate |
| Roseville, CA | 84/100 | 3 serious | 🟡 Moderate |
| Lakeland, FL | 85/100 | 1 critical | 🟡 Moderate |
| Boise, ID | 84/100 | 2 serious | 🟡 Moderate |
None of these sites would pass a WCAG 2.1 AA audit today. All of them fall under the April 24 deadline. None of them appear to have published a public compliance roadmap.
Waco's score of 55/100 with three serious issues across the homepage alone represents real legal exposure in 46 days.
The Compliance Gap Is Real
Most government web teams are understaffed and under-resourced. Accessibility expertise is rare in municipal IT departments. The April 24 deadline wasn't well-publicized until recently — many teams learned about it this year or late last year.
That's not an excuse the DOJ accepts, but it is a real operational challenge. The practical response for most agencies looks like this:
Step 1: Audit — Know exactly where you stand. You can't prioritize remediation without knowing which pages have which violations.
Step 2: Prioritize — Focus on high-traffic pages first. Homepage, services index, permit applications, payment portals, emergency information. These are the pages users depend on and the ones DOJ scrutinizes.
Step 3: Remediate — Work through the violation list systematically. Alt text, form labels, and color contrast are often fast fixes. Navigation and focus management take more dev time.
Step 4: Document — Keep records of your audit, remediation work, and ongoing testing process. Documentation matters in complaint investigations.
Step 5: Monitor — Accessibility breaks when content changes. New pages, CMS updates, third-party widgets — all can introduce violations. Regular automated scanning catches regressions before they become complaints.
How AccessiGuard Helps
AccessiGuard scans any government website against WCAG 2.1 AA and delivers a full report of every violation — critical, serious, moderate — with the specific page location, the rule violated, and how to fix it.
A $15 full report gives your IT team the exact remediation roadmap they need. No sales process, no procurement delay. Just a URL and 60 seconds.
For government IT teams with 46 days on the clock, the audit isn't optional — it's the starting point for everything else.
Scan your government website now →
The Smaller Entities Have More Time, But Not Much
If your entity serves a population under 50,000, your compliance deadline is April 26, 2027 — a full year after the first tier. But three reasons to start now anyway:
- Remediation takes longer than expected. Teams that start in early 2027 often can't finish in time.
- DOJ complaint investigations aren't limited to the deadline date — anyone can file a complaint at any time under existing Title II obligations.
- The accessibility standards don't change. The work you do now counts toward both deadlines.
The April 24 deadline is the most concentrated legal pressure the accessibility industry has seen in years. Government IT teams that act now have 46 days to get ahead of it. That's enough time — if you start today.