WCAG & Accessibility·3 min read

ADA Title II Web Rule Explained: Deadlines and WCAG

State and local governments in the US now have something private businesses never got: a written technical standard for web accessibility with dates attached. Consider this the ada title ii web rule explained in plain language: the DOJ rule requires WCAG 2.1 Level AA for public entities' web content and mobile apps, the first compliance date has already arrived, and the second lands in April 2027. Here's who's covered, what the deadlines mean now, and how to measure where your site actually stands.

Open the tool All insights

The ADA Title II web rule explained: what it requires

One standard, no ambiguity.

For years, government web accessibility ran on interpretation. The DOJ rule ended that by naming a precise target: WCAG 2.1 Level AA, applied to web content and mobile apps alike. That includes the main site, subdomains, portals, online forms, and the conventional electronic documents, PDFs among them, that residents rely on to use a service.

The scope follows the service, not the server. Content a contractor publishes on a public entity's behalf falls under the rule too, which is why procurement language shows up in every serious Title II readiness plan.

Who counts as a public entity under Title II

Broader than city hall.

The covered list reaches well past the mayor's office: cities and counties, public schools and universities, courts, police departments, transit agencies, public hospitals, libraries, parks departments, and special district governments. If an organization delivers a public service on behalf of one of these, who counts as a public entity stops being an academic question and becomes its compliance scope too.

Size only affects timing, not obligation. A village of 3,000 carries the same WCAG 2.1 AA duty as a state government; it simply got a later date.

April 2026 deadline requirements, and the 2027 tier

One date passed, one pending.

The april 2026 deadline requirements applied to public entities serving 50,000 or more people: their web content and mobile apps were due to conform to WCAG 2.1 AA by April 24, 2026. That date is behind us, so for larger entities this is no longer preparation, it's exposure. Title II is enforced by the DOJ and through private lawsuits, and a documented remediation program is the difference between a gap and negligence.

Entities under 50,000 people and all special district governments have until April 26, 2027. That's real time if you start now: scan, fix the critical failures, remediate documents, and build the process items before the date arrives rather than after.

A worked Title II example: one flagged link on a transit page

Small failure, daily impact.

Picture a bus schedule page carrying this markup: Input: <a href="/routes/route-12.pdf">Click here</a>. A WCAG 2.1 AA assessment flags it under criterion 2.4.4 Link Purpose, because a screen reader user tabbing through links hears only "click here" with no idea where it leads. The generated fix is plain: Output: <a href="/routes/route-12.pdf">Route 12 schedule (PDF)</a>.

Multiply that by every schedule, permit form, and agenda on a government site and the stakes get concrete. Residents who can't read the link can't catch the bus. The ADA Title II Checker feeds your URL into a full-site scan against exactly these criteria, then pairs the results with a 12-step readiness checklist covering scope, fixes, and documentation.

Title II mistakes public entities keep making

The pattern across struggling agencies is rarely bad faith. It's these misjudgments, repeated.

Auditing the main site and forgetting the portals: payment systems, permit applications, and school platforms are where residents transact.
Treating PDFs as out of scope. Documents posted after your deadline must conform; only some older material qualifies for the archived-content exception.
Assuming a vendor's widget is the vendor's problem. Under the rule, services offered through third parties remain your responsibility.
Waiting for a complaint to start. Enforcement risk aside, retrofitting under pressure costs more than scheduled remediation ever does.
Declaring victory off one clean automated scan. Automated checks cover a subset of WCAG 2.1 AA; keyboard and screen reader testing complete the picture.

Practical moves for Title II teams this quarter

Three things that compound.

First, scan the service-critical sections before anything else: payments, permits, schedules, enrollment. Seeding a scan from those URLs finds the failures residents hit daily. Second, put WCAG 2.1 AA into every new contract and renewal now, because third-party tools age into your compliance record. Third, keep dated exports of every scan; a folder of improving reports is the strongest good-faith evidence a public entity can produce on short notice.

Where the ADA Title II Checker fits among the WCAG tools

Government first, then the rest.

The ADA Title II Checker is the starting point for public entities because it frames the scan around the rule's deadlines and readiness steps. The underlying crawl is the WCAG Accessibility Scanner, which any team can run directly for a plain audit. Private businesses facing Title III should work from the ADA Compliance Checklist instead, and every entity, public or private, eventually needs the Accessibility Statement Generator to publish its standard and feedback channel.

Try it now

Open ADA Title II Checker

The tool is one click away. No sign up, no upload, no payment.

Open ADA Title II Checker

Write a review