The ADA Website Deadline Is Coming: What State and Local Agencies Need to Know

Accessibility · Field notes

In April 2024, the Department of Justice published a final rule under Title II of the Americans with Disabilities Act that does something the web has been waiting on for years: it names a specific technical standard for state and local government websites. That standard is WCAG 2.1 Level AA, and it now has dates attached.

If your organization serves 50,000 or more people, the compliance date is April 26, 2027. Smaller entities and special district governments have until April 26, 2028. Both dates were extended by one year in April 2026, but the standard did not change, and the extra year disappears fast once procurement, budgeting, and board approvals enter the picture.

What the rule actually covers

The rule applies to all state and local government entities: cities, counties, towns, special districts, public schools and universities, courts, police, and state agencies. It covers websites and mobile apps, and importantly, it covers content delivered through third-party tools. If residents pay a bill, apply for a permit, or register for a program through a vendor platform, that experience is part of your obligation.

WCAG 2.1 AA sounds technical, but the principles are plain. Content must be perceivable (sufficient contrast, alt text, captions), operable (everything works with a keyboard, nothing traps focus), understandable (predictable navigation, labeled forms, clear errors), and robust (it works with assistive technology). Level AA includes roughly 50 success criteria, and conformance is measured against the real rendered page, not against a widget sitting on top of it.

How to find out where you stand

Start with the free tools. axe DevTools, WAVE, and Lighthouse will each scan a page and flag machine-detectable issues: missing alt text, contrast failures, unlabeled form fields, bad ARIA. Run them against your homepage, your top ten pages by traffic, and your most important service flows.

Then accept what the scanners cannot tell you. Research consistently shows automated tools catch only about 30 to 40 percent of WCAG issues. A scanner cannot judge whether your alt text is meaningful, whether the focus order makes sense, whether an error message actually helps someone recover, or whether your navigation is usable without a mouse. That requires manual testing: unplugging the mouse for an afternoon, turning on VoiceOver or NVDA, and zooming the page to 400 percent.

• Automated scan of key templates with axe, WAVE, or Lighthouse.
• Full keyboard pass through navigation, forms, and checkout-style flows.
• Screen reader pass on the same flows with VoiceOver or NVDA.
• Zoom and reflow test at 400 percent.
• Review of your highest-traffic PDFs and third-party tools.

Where sites usually fail

Across the audits we have run, the same problems appear again and again, and most of them live in the design system rather than on any single page:

• Contrast ratios that fail across an entire color palette, not just one button.
• Forms with placeholder text instead of labels, and errors announced only in red.
• Navigation menus that cannot be opened or escaped with a keyboard.
• PDFs: agendas, minutes, permits, and reports published as untagged scans.
• Heading structures that skip levels and break screen reader navigation.
• Third-party widgets for payments, calendars, and chat that were never tested.

The good news in that list is structural. When you fix a template or a component, you fix hundreds of pages at once. This is why we recommend remediating the design system first and individual pages second.

A realistic timeline, working backward

A focused WCAG 2.1 AA audit takes two to four weeks. Remediation of a typical municipal or nonprofit site runs two to six months depending on how many templates, documents, and vendor tools are involved. Working backward from April 2027, entities on the first deadline should be scoping an audit now. Entities on the 2028 deadline have more room, but that room disappears fast once procurement, budgeting, and board approvals enter the picture.

The sequence that works: audit first, then a prioritized roadmap ranked by user impact and legal risk, then remediation of templates and components, then verification and documentation. Documenting the work matters. Demonstrated, dated progress toward conformance is meaningfully different from doing nothing, both for the public and in any enforcement conversation.

The PDF question

Documents are where most agencies feel the rule most acutely. Years of agendas, minutes, forms, and reports cannot all be remediated by hand, and the rule includes limited exceptions for genuinely archived content. The practical strategy is triage: convert high-traffic documents to accessible HTML pages, remediate the PDFs that must remain PDFs, and archive outdated material under the exception with clear labeling.

What about accessibility overlays?

Overlay widgets that promise instant compliance with one line of JavaScript do not fix the underlying code, and they have been named in hundreds of lawsuits. Disabled users frequently report that overlays make sites worse, interfering with the assistive technology people already use. There is no shortcut here, and any vendor selling one should be treated with skepticism.

Where to start this week

Run a free scan on your homepage and your three most-used service pages. Try to complete one real task with only a keyboard. Then look at your ten most-downloaded PDFs. That hour of testing will tell you more about your exposure than any sales deck.

If you want a professional read, we offer a free accessibility assessment for public entities and nonprofits. We review your key templates and flows, flag the highest-risk issues, and give you an honest picture of scope and timeline. Accessibility has been central to our work for organizations like the Mary Tyler Moore Vision Initiative, where we designed for an audience living with vision loss from the first wireframe. This is work we know how to do, and we are glad to help you figure out what it will take.

A note: we are designers and engineers, not attorneys. Nothing here is legal advice. For counsel on your specific obligations, talk to your attorney.