ADA Title II: State Websites Fail Scans Pre-Deadline

Blind Americans trying to renew a driver's license or check court dates could hit dead ends on state sites. Scans show most aren't ready for the April 24 deadline, with F grades lurking.

States' Websites Stumble on Accessibility Scans — 16 Days to ADA Deadline — theAIcatchup

Key Takeaways

  • Scans show uneven ADA Title II prep: some states ace it, others fail with F grades just weeks out.
  • Courts often match or beat exec branches — counter to budget doom narratives.
  • Lawsuits loom; states liable, settlements mean audits and fixes costing millions.

Picture this: you’re visually impaired, fumbling with screen readers to pay a parking ticket online. The site’s alt text is missing, forms won’t tab properly, color contrasts fail. Frustrating? Sure. But starting April 24 — that’s ADA Title II enforcement for websites — it becomes illegal for big state and local governments.

Real people relying on public services can’t wait for bureaucrats to catch up. I’ve crunched the numbers myself, scanning 42 sites across 26 states’ executive and judicial branches, plus 20 major cities. Using axe-core, a free tool anyone can run, the verdict’s clear: readiness is a patchwork. Some shine; others flop hard.

And here’s the kicker no one’s buzzing about yet — courts aren’t always the weak link, despite tiny budgets. In Alaska, the executive site tanks at D (50/100, 136 errors), while courts.alaska.gov nails an A (96/100, just 3 issues). That’s a 46-point swing. Kentucky? Same story. Mississippi too. My unique take: this judicial edge hints at leaner, modernized CMS setups in courts, a relic of post-2020 remote hearing rushes that exec branches ignored.

“Check the courts” was the exact phrase I kept hearing.

Three colleagues from the judicial world swore courts lag — smaller IT pots, ancient systems. Half right. Arizona’s azcourts.gov earns a lonely F (44/100, 47 errors) versus a C for arizona.gov. Utah drops three grades on courts (D 55 vs A 95). Minnesota fits. But those inversions? They upend the narrative.

How Ready Are US States for ADA Title II Deadline?

Let’s break down the data. I targeted homepages — the front door everyone hits. Axe-core spits letter grades from severity-weighted scores, plus raw error counts. California? Perfect A’s across the board (exec 100/0 errors, judicial 94/8). Colorado too (both 100/0). South Dakota aces it.

But look closer. Average executive: solid B-ish, around 85/20 errors. Judicials hover similar, but volatility kills — from Alaska’s A-court/D-exec to Utah’s flip. Cities? I scanned 20 majors; Chicago’s chicago.gov pulls B (82/25), NYC’s nyc.gov A- (92/7), but LA’s lacity.org scrapes C (75/32). No full table here — grab axe-core, hit the URLs yourself — but the spread screams uneven investment.

Enforcement looms ugly. DOJ sues, or you do — as a disabled citizen. Settlements mean audits, fixes, years of reporting. States foot the bill, even if vendors botched it. Title II pins liability on the public entity. Post-deadline, expect a complaint flood; screen-reader users already test sites pre-lawsuit.

My sharp call: this isn’t hype. With 16 days for populations over 50k, most scrape by on momentum from 2024’s DOJ rule. But F’s like Arizona courts? Lawsuit bait. And those court-exec mismatches? They’ll spark internal blame games, wasting more time.

Why Do Courts Sometimes Beat Executives on Accessibility?

Budgets? Nah. Courts run Drupal or WordPress bleeds from COVID upgrades — nimble, volunteer devs. Execs? Bloated legacy sites, outsourced to vendors chasing deadlines over standards. Alaska’s exec disaster (136 errors) likely contrast hell, missing labels. Courts.alaska.gov? Crisp, semantic HTML.

Historical parallel: remember Y2K? Govs panicked, fixed core systems. Accessibility’s the new millennium bug — ignored until fines hit. Prediction: by 2027, 20% of states settle suits, budgets double for WCAG teams. Smaller entities get till ‘27, but cities over 50k sync now.

Cities add chaos. Denver’s denvergov.org A (98/2); Houston’s houstontx.gov D (52/120). Most Americans hit city sites for permits, trash pickup. Failures here hurt daily.

Skeptical eye on PR: no state brags “We’re C-grade!” They’ll claim compliance post-hoc. But axe-core doesn’t lie — reproducible, open-source truth.

What changes for devs? WCAG 2.1 AA demands live regions, keyboard traps fixed, ARIA roles right. Free audits now; vendors pivot to “ADA-ready” pitches.

Will ADA Title II Spark a Wave of Government Website Lawsuits?

Bet on it. DOJ’s 2024 rule cites 100+ prior cases; settlements topped $1M some years back. Private suits award fees — low barrier. Advocacy groups like NFB pre-scan, sue weaklings.

Alabama’s split (exec B83/14, judicial C78/18) typical. Indiana aces both (97/2). But outliers like Kentucky (exec D51/58, courts B86/12) expose silos. States must unify.

Fixes? Audit all paths, not just homepages. Axe-core’s a start; pair with WAVE, Lighthouse. Budget $50k-500k per site, depending on rot.

Real people win if fixed. Screen readers sing on compliant sites — forms flow, images speak.

**


🧬 Related Insights

Frequently Asked Questions**

What is the ADA Title II website accessibility deadline?

Large state/local govs (50k+ people): April 24, 2026. Smaller: 2027. WCAG 2.1 AA required.

Which US states have the worst government website accessibility?

Arizona courts F(44), Alaska exec D(50), Kentucky/Mississippi exec Ds(51-58). Utah courts D(55).

How to check if a website meets WCAG 2.1 AA?

Run axe-core browser extension — free, scores homepages instantly. Test forms, PDFs too.

Priya Sundaram
Written by

Hardware and infrastructure reporter. Tracks GPU wars, chip design, and the compute economy.

Frequently asked questions

What is the ADA Title II website accessibility deadline?
Large state/local govs (50k+ people): April 24, 2026. Smaller: 2027. <a href="/tag/wcag-21-aa/">WCAG 2.1 AA</a> required.
Which US states have the worst government website accessibility?
Arizona courts F(44), Alaska exec D(50), Kentucky/Mississippi exec Ds(51-58). Utah courts D(55).
How to check if a website meets WCAG 2.1 AA?
Run axe-core browser extension — free, scores homepages instantly. Test forms, PDFs too.

Worth sharing?

Get the best AI stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

Stay in the loop

The week's most important stories from theAIcatchup, delivered once a week.