What the ADA Title II Web Rule Actually Requires

For twenty-five years, public agencies asking "what does the ADA require of our website?" got the same unsatisfying answer: nobody's entirely sure, but probably something like WCAG. The Department of Justice's Title II rule ended that. There is now a named standard, a defined scope, and a date.

The standard is WCAG 2.1 Level AA

Not "substantially accessible." Not "reasonable efforts." A specific version of a specific technical standard at a specific conformance level. That precision cuts both ways: it's harder to argue you're close enough, and much easier to know what to build toward.

The deadlines are tied to population

Public entities serving 50,000 or more people were required to comply by April 24, 2026. Entities serving fewer than 50,000, and special district governments of any size, have until April 26, 2027.

Note what that second group includes: water districts, transit authorities, library systems, school districts, and every small municipality in the country. Many of them have no in-house web staff at all.

The scope is wider than your website

This is where agencies consistently underestimate the work. The rule reaches web content and mobile apps that a public entity provides or makes available — which in practice means:

• The main site, and every department microsite nobody remembers commissioning
• Mobile applications offered to residents
• Documents published to the public: agendas, minutes, budgets, permit forms, notices
• Content posted by contractors and vendors on the entity's behalf

And the part that causes the most difficulty: third-party portals. If residents pay a utility bill, apply for a permit, or file a 311 request through a vendor's platform, that is still a service you provide. The vendor's accessibility problem is your program access problem.

What "compliance" looks like in practice

There is no certificate. What you can produce is a conformance claim supported by evidence — and that evidence is what matters if a complaint arrives:

1. An inventory. You can't claim conformance for content you never catalogued. Most agencies find more properties than they expected.
2. Real testing. Automated scanning alone doesn't establish conformance against most of the criteria in the standard.
3. A dated remediation plan. With owners. Progress against a written plan is the single most useful thing to have when someone asks.
4. A working feedback path. A published accessibility statement, a real contact, and a record of how reported barriers were resolved.
5. A way to stop the bleeding. Trained content authors and procurement language, or you will be remediating the same site again in two years.

See the live countdown to April 26, 2027 and a working-backwards plan for the time remaining.

If you're in the 2027 group

You have roughly one budget cycle and one procurement cycle left. In public-sector time, that's tight — an assessment, a remediation contract, and a document backlog don't fit comfortably into a single fiscal year if the first one starts late.

The most useful thing a small entity can do right now is not a full program. It's a scoped baseline: what do we actually run, how bad is it, and what would a realistic sequence cost? That's a number you can take into a budget request. "We should probably look at accessibility" is not.

The honest framing

The rule is a deadline, but the underlying obligation isn't new — Title II has required program access since 1990. What changed is that the technical ambiguity is gone.

For most agencies, that's a net positive. A clear standard is far easier to budget against, write into an RFP, and hold a vendor to than a decade of "make a good faith effort."