The ADA Title II Deadline Moved Again. The Obligation Did Not.

Four days before the first Title II compliance date arrived, the Justice Department moved it. Large public entities now have until April 26, 2027, and smaller ones until April 26, 2028. Nothing about the standard changed, and nothing about the obligation paused.

What moved, and what did not

The rule itself dates to April 24, 2024, when the Department of Justice published a final rule adopting WCAG 2.1 Level AA as the technical standard for state and local government websites and mobile apps. The original compliance dates were April 24, 2026 for entities serving 50,000 or more people, and April 26, 2027 for smaller entities and special district governments.

The change came in an interim final rule effective April 20, 2026, published as 91 FR 20902. It moved the large-entity date to April 26, 2027 and the small-entity date to April 26, 2028. The Department was explicit about its reason: it had overestimated how fast covered entities could get their sites into conformance. The technical standard, WCAG 2.1 Level AA with its 50 success criteria, was not touched.

That distinction matters more than the new dates do. A moved deadline is not a repeal, and the Department paired the extension with a reminder that covered entities have an ongoing obligation to make their services accessible whatever the compliance date says. A city that treats 2027 as a start date instead of a finish line will be exactly as exposed then as it is now.

Who the rule covers

Title II covers every state and local government entity: cities, counties, school districts, public universities, courts, transit authorities, public hospitals, libraries, and special districts. It does not cover private businesses. A private Shopify store has no Title II deadline, though it can still face a Title III lawsuit, which is a different statute with no technical standard attached. Related reading: Focus Not Obscured: When a Sticky Header Hides the Keyboard.

The population line is the part teams get wrong. It is the population the entity serves, not the size of its web team or its budget. A small town with a big county website behind it needs to check which entity owns the site before assuming it falls in the later group. Special district governments, library districts and water districts among them, sit in the later group regardless of size.

Agencies that also receive federal funding carry a second obligation under Section 504 of the Rehabilitation Act, which now points at the same WCAG 2.1 Level AA standard for their web content. One remediation program can serve both, which is the only efficient way to run this.

What to do with the extra year

Start with the failures that show up in nearly every audit: images without alt text, forms without labels, keyboard traps in custom menus and date pickers, and body text below the 4.5 to 1 contrast ratio. Those four account for most of what plaintiffs testers find, and all four are fixable at the component level rather than page by page. More on this: Colour Contrast for Sale Badges and Promo Labels.

Then fix procurement, because new barriers are still being created while the old ones get fixed. A contract that requires WCAG 2.1 AA conformance and an accessibility conformance report from every vendor costs nothing to write and stops the next inaccessible widget from landing on the site. The agencies still getting sued in 2026 are mostly the ones that fixed their homepage and kept buying inaccessible tools.

And keep the evidence. The rule is enforced through complaints and litigation, not through a certification stamp, so the record that matters is the one showing what was tested, when, and what got fixed. A dated test log beats a vendor promise in every forum where this gets argued.

The check to run this week

Open the site, unplug the mouse, and try to complete the most common task on it: pay a bill, register for a program, find a meeting agenda. If the keyboard cannot finish it, the site fails the standard today, and the new deadline does not change that. The extension bought time. It did not buy a pass.

Frequently asked questions

Does the extension apply to private businesses?

No. Title II covers state and local government entities only. A private business faces Title III instead, which has never had a Justice Department technical standard for websites.

Did the extension change the standard from WCAG 2.1 to something else?

No. The standard is still WCAG 2.1 Level AA, all 50 success criteria. The interim final rule moved the dates and nothing else.

What happens on April 26, 2027?

For entities serving 50,000 or more people, that is the new compliance date. After it, a non-conforming website is a federal civil rights violation, enforceable through complaints to the Department and private action.

Is WCAG 2.2 required instead?

Not by this rule, which names WCAG 2.1. But 2.2 is the current W3C recommendation, and conforming to 2.2 covers 2.1, so teams aiming at the newer version are not doing extra work for nothing.