WCAG & Accessibility·4 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. In plain language, the DOJ rule requires WCAG 2.1 Level AA for public entities' web content and mobile apps. The DOJ's April 2026 interim final rule moved the compliance dates back one year, to April 26, 2027 for larger entities and April 26, 2028 for smaller ones and special districts. Here's who's covered, what the dates mean, and how to measure where your site stands.

Open the free ADA Title II Compliance Checker 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, Word files, spreadsheets and slides among them, that residents rely on to use a service.

The scope follows the service, not the server. Content a contractor or vendor provides 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 libraries, parks departments, and special district governments. If an organization delivers a public service on behalf of one of these under a contract or license, that content is inside the 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 gets a later date.

The 2027 and 2028 compliance dates

Moved once already, so check again.

The DOJ's 2024 rule originally set April 24, 2026 for public entities serving 50,000 or more people and April 26, 2027 for everyone else. An interim final rule dated April 20, 2026 pushed both back one year. Under it, entities with a population of 50,000 or more must conform by April 26, 2027, and entities under 50,000 plus all special district governments by April 26, 2028. Because the dates have changed once, check the current rule on ada.gov before you plan around them.

The extra year is time to use, not time to wait. Title II is enforced by the DOJ, through complaints, and through private lawsuits, and a documented remediation program is what shows good faith. The ADA Title II Compliance Checker includes a deadline calculator: pick your population tier and it shows your date and the days left.

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

Small failure, daily impact.

Picture a bus schedule page carrying this markup: <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 fix is plain: <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 checker sends your domain to a full-site scan against checks like this one, then pairs the results with a 16-item readiness checklist covering scope, technical fixes, documents, procurement and training. When you're done, Download readiness report (PDF) gives you a dated record of your tier, date, exceptions and checklist status.

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 every old PDF as exempt. The preexisting documents exception doesn't cover files people still use to apply for or access a service, such as a current permit form.
Assuming a vendor's widget is the vendor's problem. Under the rule, services offered through third parties remain your responsibility.
Claiming an exception without writing down why. The rule has five exceptions, including archived content and preexisting social media posts, each with conditions. The checker's exceptions self-check lists them, and a short written reason for each is what holds up later.
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 and readiness report; a folder of improving records is strong good-faith evidence a public entity can produce on short notice.

Where the ADA Title II Compliance Checker fits among the WCAG tools

Government first, then the rest.

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

Try it now

Open ADA Title II Compliance Checker

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

Open ADA Title II Compliance Checker

Write a review