ADA Title II's web accessibility deadline has arrived: what it means

In April 2024, the US Department of Justice finalized a rule under ADA Title II requiring state and local government web content and mobile apps to meet WCAG 2.1 Level AA. The first compliance date — April 24, 2026, for larger governments — arrived this spring, and days before it hit, the DOJ extended both deadlines by a year: April 26, 2027 for entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special districts. The standard itself did not change, and the ADA's underlying obligations never paused.

Here's what the rule requires, who's in scope (including vendors building for government), and how to use the extra year.

What the rule requires

The rule adopts WCAG 2.1 Level AA as the enforceable technical standard for the web content and mobile apps that state and local governments use to offer their services, programs, and activities (ADA.gov). That covers public websites, web apps, documents posted on them, and native mobile apps — whether built in-house or provided through a contractor.

WCAG 2.1 AA is a concrete, testable bar: around 50 success criteria covering keyboard operability, text alternatives, captions, color contrast, form labels, focus management, and more (Venable). It's the same standard that anchors accessibility law elsewhere — the EU's European Accessibility Act tests against EN 301 549, which incorporates WCAG 2.1 AA (Deque).

The deadlines moved — the rule didn't

On April 20, 2026, the DOJ issued an interim final rule extending the compliance dates by one year, with public comments accepted through June 22, 2026 (Federal Register):

Entity	Old deadline	New deadline
Population 50,000 or more	April 24, 2026	April 26, 2027
Under 50,000, or any special district	April 26, 2027	April 26, 2028

Population is determined from Census data for the entity's jurisdiction, not headcount or traffic (ADA.gov). Everything else — the WCAG 2.1 AA standard, the scope, the exceptions — is unchanged.

Two things keep the extension from being a reason to relax. First, Title II's general nondiscrimination obligations remain in force throughout; the DOJ framed the extra year as time to focus on compliance work, not to defer it (Deque). Second, adjacent deadlines didn't move with it: HHS's separate Section 504 rule for health care organizations that receive HHS funding carried a May 2026 compliance date that, as of this writing, has not been similarly extended (Jackson Lewis). If you build for hospitals or clinics, see our health care accessibility guide.

Who's in scope — including vendors and contractors

Every state and local government entity is covered: cities, counties, states, public schools and universities, libraries, courts, police departments, transit agencies, water districts (Venable).

The part agencies and software vendors most often miss: the rule expressly applies to web content a public entity makes available "through contractual, licensing, or other arrangements" with private companies (Venable). A parks-reservation platform, a school district's grade portal, a county's payment processor, an agency-built city website — if a government uses it to deliver services to the public, the government is on the hook for its accessibility, and that obligation flows into procurement. Expect WCAG 2.1 AA conformance to show up in RFPs, contract renewals, and vendor security questionnaires the way SOC 2 did. For vendors, "we're a private company, the ADA rule isn't ours" is true only in the narrowest sense: your government customers can't buy what they can't legally deploy.

The exceptions are real but narrow

The rule lists five exceptions (ADA.gov):

1. Archived web content — created before the deadline, kept only for reference, stored in a designated archive area, and left unchanged.
2. Preexisting conventional documents — PDFs, Word files, spreadsheets, and slides posted before the deadline, unless they're currently needed to use a service (a form you must submit doesn't qualify).
3. Third-party content — content posted by genuinely independent third parties, not by contractors or vendors acting for the entity.
4. Individualized password-protected documents — documents about a specific person or account behind a login.
5. Preexisting social media posts — posts made before the entity's compliance date.

Courts and the DOJ construe these narrowly (Venable), and there's a general escape valve only for undue burden or fundamental alteration — a high bar. Note the planning implication of the archive exception: it only helps for content you deliberately freeze and move to an archive before your deadline. Content you keep serving normally has to conform, no matter how old it is.

How to approach remediation with the time you have

ADA.gov's own first-steps guidance is a sensible outline (ADA.gov); here's how it translates into an engineering plan:

1. Inventory before you audit. List your sites, subdomains, apps, and document repositories, and identify what can honestly be archived or retired. Deleting or archiving low-value content is the cheapest remediation there is.
2. Scan everything, then prioritize by task. Automated WCAG scanning finds the bulk of contrast, labeling, structure, and alt-text failures fast. Prioritize the flows residents actually depend on — paying a bill, applying for a permit, checking a schedule — over long-tail pages. Our accessibility guides map the most common failures to fixes.
3. Fix in templates and components. Most government sites run on a small number of templates; one fixed header component can clear thousands of page-level failures.
4. Push obligations into vendor contracts now. New procurements and renewals should require WCAG 2.1 AA conformance with evidence — audit results, not just a VPAT checkbox.
5. Document continuously. A dated record of scans, fixes, and re-scans is how you demonstrate a good-faith program in progress if a complaint arrives before you're done.

That find-fix-verify loop is exactly what BugPort automates: scheduled WCAG scans that surface real failures on your actual pages, each finding turned into a ticket with element-level evidence (selector, screenshot, criterion) that a developer or vendor can act on directly, and a re-scan history that becomes your remediation record. It won't make anyone "compliant" — no tool can promise that — but it takes the manual drudgery out of getting there and proving it. Run a free WCAG audit on any public site to see what an auditor would see.

This article is for general information only and is not legal advice. Public entities and their vendors should confirm obligations and deadlines with counsel.

FAQ

Did the April 2026 deadline get canceled?

No — it was extended, not eliminated. The DOJ's interim final rule, effective April 20, 2026, moved the compliance date to April 26, 2027 for entities of 50,000+ population and April 26, 2028 for smaller entities and special districts (Federal Register). The WCAG 2.1 AA requirement is unchanged, and Title II's general obligations continue to apply in the meantime.

Does this rule apply to private companies?

Not directly — Title II covers state and local governments. But content and apps that private vendors provide for public entities "through contractual, licensing, or other arrangements" are covered on the government's side (Venable), so vendors inherit the requirement through procurement. Separately, health care organizations receiving HHS funding face their own Section 504 web accessibility deadline (Jackson Lewis).

Which WCAG version applies — 2.1 or 2.2?

The rule requires WCAG 2.1 Level AA (ADA.gov). Since WCAG 2.2 is backwards-compatible and adds criteria regulators may adopt later, testing against 2.2 AA is a safe way to meet the 2.1 AA requirement with headroom.

Do old PDFs on our site need to be fixed?

Conventional documents posted before your compliance date are excepted — unless they're currently needed to apply for, access, or participate in your services, in which case the exception doesn't apply (ADA.gov). Active forms, notices, and schedules need remediation regardless of when they were posted.