DOJ Extended the April 24, 2026 ADA Title II Deadline 12 Months — What State & Local Governments Must Do With the Runway

On April 24, 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 bring their websites and mobile apps into conformance with WCAG 2.1 Level AA. The original compliance date for large public entities was April 24, 2026.

On April 20, 2026 — four days before that date — the DOJ published an Interim Final Rule extending the compliance dates by 12 months. The substantive technical standard (WCAG 2.1 Level AA) did not change. Only the effective dates moved.

If your jurisdiction serves a population of 50,000 or more, you now have until April 26, 2027. Smaller jurisdictions (under 50,000) and special district governments now have until April 26, 2028. Public comments on the IFR close June 22, 2026. The window is not a grace period — it is runway. Treat it as an enforcement delay, not a waiver.

What exactly is required?

Every public-facing digital touchpoint is in scope: your main website, mobile apps, online forms, PDFs used to access government services, and even third-party content you host. If a citizen interacts with it online to access a government program, it must meet WCAG 2.1 AA.

WCAG 2.1 AA is built on four principles — content must be Perceivable, Operable, Understandable, and Robust (POUR). Practically, this means:

• Sufficient color contrast (minimum 4.5:1 ratio for body text)
• Full keyboard navigability — no mouse required
• Screen reader compatibility with proper ARIA roles and labels
• Captions on all video content
• Accessible forms with clear error handling and inline labels

What automated tools miss

This is the most misunderstood part of compliance. Automated scanning tools — even good ones — catch roughly 30% of WCAG issues. The other 70% require manual review: a human tester navigating your site with a screen reader, keyboard only, and assistive technology.

At ADAWCAG.org, our scan stack combines axe-core, pa11y, and Lighthouse for the broadest automated coverage available. Every enterprise audit also includes a live human review by Aaron Espinoza — a certified blind accessibility tester holding DHS Trusted Tester certification — who navigates exclusively with assistive technology every day.

Automated tools will not catch issues like:

• Logical reading order that sounds correct to sighted users but is nonsensical to screen reader users
• Interactive elements that are technically keyboard-reachable but have no visible focus indicator
• Form fields with labels that are technically associated but contextually unclear
• PDFs with improperly tagged headings, missing alt text, or incorrect reading order

The legal risk is real

Over 4,600 ADA Title III web accessibility cases were filed in federal court in 2023 alone, according to Seyfarth Shaw. Title II enforcement is now ramping up. The DOJ can investigate complaints directly and mandate remediation — and unlike Title III, there is no opportunity to cure the violation before a complaint is filed with the federal government.

Being "in progress" on compliance is not a legal defense if a complaint is filed after the new April 26, 2027 / April 26, 2028 dates. Jurisdictions that cannot demonstrate good-faith effort and documented remediation progress will be the most exposed when the runway runs out — and DOJ has been clear in its rulemaking preamble that the extension is operational, not substantive.

The right documentation posture includes a current VPAT/ACR (Voluntary Product Accessibility Template / Accessibility Conformance Report) that accurately describes your current conformance level — not a declaration of full compliance you cannot support.

What to do right now

1. Run an automated scan to baseline your current accessibility issue count by page and severity
2. Prioritize your highest-traffic and highest-function pages first — login, forms, search, maps, emergency services pages
3. Engage a certified human tester for what scanners miss — screen reader navigation, keyboard-only use, cognitive clarity
4. Generate a VPAT/ACR to document your conformance posture for procurement and legal review
5. Set up ongoing monitoring — compliance is not a one-time event; every content update is a potential regression

ADAWCAG.org was built specifically for this deadline. Government agencies, universities, healthcare systems, and law firms use our platform to audit, monitor, remediate, and document WCAG 2.1 conformance — with evidence-grade reports built for legal and procurement review.

The deadline is not moving. Start your free scan today.