Counties Face the ADA Web Deadline. The Real Work Starts Now

On April 24, 2026, every U.S. county with 50,000 or more residents must meet WCAG 2.1 Level AA across its public web properties and mobile apps. That's the first compliance deadline embedded in the Department of Justice's Title II digital accessibility rule. Smaller counties and special districts get an extra year, until April 26, 2027, to catch up.

Conduit Street Blog, the National Association of Counties' policy publication, presses a different point in a recent piece titled "Deep Dive: Beyond the ADA Digital Accessibility Deadline." The substance isn't the date itself. It's what happens to operating budgets, vendor contracts, and remediation queues once the calendar flips.

The rule borrows its technical baseline from the W3C. WCAG 2.1 Level AA covers a wide surface: alt text on non-decorative images, visible focus indicators meeting a 3:1 contrast ratio, captions on prerecorded video, error suggestions on form inputs, and full keyboard operability across interactive components. Each success criterion maps to a failure pattern automated scanners can flag and a behavior pattern that human users actually hit.

Federal guidance on the rule makes clear that automation alone falls short. Industry audits show automated tools catching roughly 30 to 50 percent of accessibility issues, depending on scope. The rest requires manual testing with assistive technology: keyboard-only navigation, screen-reader walk-throughs in NVDA or JAWS, zoom testing at 400 percent without loss of content or function.

Three patterns draw the heaviest enforcement scrutiny:

• PDFs that serve as the only copy of a public meeting agenda, budget, or emergency notice.
• Form flows that drop keyboard users mid-process when applying for permits or licenses.
• Interactive maps and dashboards built with custom JavaScript widgets that bypass semantic structure.

Counties that began remediation in 2024 have a structural advantage. Shared components — header, footer, search, document viewer — get fixed once and then carry the rest of the estate forward. Page-by-page remediation multiplies the work for every new template or redesign, which is where the post-deadline costs concentrate.

The DOJ rule names no single enforcement mechanism. Complaints flow through the Department of Justice or the Department of Health and Human Services, and private plaintiffs can still litigate under Title III. The historical pattern after similar accessibility settlements: demand letters follow within months, with plaintiffs' firms scanning newly published accessibility statements.

What does the deadline actually change?

Very little for counties that have worked in earnest since 2024. A great deal for those that treated the rule as advisory. The post-deadline question isn't "are we compliant on April 24?" — auditors sample across the entire web estate — but "can we prove conformance, and can we keep proving it?"

What does WCAG 2.1 AA actually require?

The standard names 30 success criteria at Level AA across four buckets:

• Perceivable: text alternatives, captions, color contrast.
• Operable: keyboard access, focus order, motion alternatives.
• Understandable: consistent navigation, input assistance.
• Robust: compatibility with assistive technology.

The DOJ rule references the W3C's 2024 errata version of the standard.

What audit cadence makes sense after April 2026?

Annual is the floor. Conformance drifts: a new vendor ships a widget, a content editor uploads an untagged flyer, and the property quietly fails. Most compliance officers now bake a quarterly automated scan into the CMS workflow, reserve annual third-party audits for the formal report, and run spot checks whenever a major template changes.

What shifts after the deadline is the burden of proof. Before, counties filed accessibility statements. After, those statements become evidence in complaints that move faster and cost more to settle than the remediation would have. The compliance clock doesn't stop. It starts measuring.