ADA Title II Web Accessibility: Standard, Deadlines, and Exceptions

Under ADA Title II web accessibility requirements, every state and local government website and mobile app must conform to the Web Content Accessibility Guidelines version 2.1, Level AA. The Department of Justice extended the original compliance deadlines by one year in April 2026: entities serving 50,000 or more people now have until April 26, 2027, and smaller entities and special district governments have until April 26, 2028.¹ Title II has required accessible services since 1990; the 2024 rule pins that obligation to a single measurable standard.²

Who Is Covered

The rule applies to every public entity subject to Title II. That means state agencies, counties, cities, towns, public school districts, public universities, courts, legislative bodies, and every department inside them. Special purpose districts such as transit authorities, water districts, and library systems are explicitly included, as is Amtrak.² Population size affects only your deadline. A town of 800 has the same substantive obligation as a city of two million.

Coverage follows the service, not the server. When a public entity delivers something through a contractor, vendor, or licensing arrangement, the accessibility obligation stays with the entity. A county that hires an outside firm to build its online permit portal is still on the hook for that portal.³ The regulation uses deliberately broad language — “contractual, licensing, or other arrangements” — to close the outsourcing loophole.⁴

What Content Must Be Accessible

All web content and mobile apps a public entity provides or makes available fall under the rule. In practice, that reaches the digital interactions that have replaced trips to a government counter: paying property taxes, applying for permits, registering for recreation programs, viewing public records, ordering mail-in ballots, and checking tax information.² Mobile apps for transit tracking or pothole reporting are covered the same way.

Digital documents count too. PDFs, spreadsheets, and presentations posted on a government site generally must be formatted so screen readers can interpret them. Video content, including council meetings and public hearings, needs captions. If an agency hosts content on a third-party platform, the accessibility responsibility stays with the agency.⁵

The Technical Standard

DOJ adopted WCAG 2.1, Level AA as the legally required benchmark.² Published by the World Wide Web Consortium, WCAG 2.1 organizes accessibility around four principles: content must be perceivable (images have text descriptions, videos have captions, color alone doesn’t carry meaning), operable (navigation works without a mouse), understandable (pages behave predictably and labels are clear), and robust (content works reliably across browsers and assistive technologies).⁶

Level AA sits in the middle of the three conformance tiers (A, AA, AAA) and is generally treated as the practical accessibility floor. The rule also allows “equivalent facilitation”: using a different approach that provides equal or greater accessibility satisfies the requirement. Content built to the newer WCAG 2.2 standard qualifies, since WCAG 2.2 includes everything in 2.1 Level AA.²

Compliance Deadlines

The interim final rule published on April 20, 2026 pushed both original deadlines back one year and took effect immediately, while DOJ solicits public comments on the revised dates.¹ The updated dates are in the current Code of Federal Regulations:⁴

April 26, 2027 for public entities (other than special district governments) serving a total population of 50,000 or more.
April 26, 2028 for public entities serving fewer than 50,000 people, and for all special district governments regardless of size.

Waiting for the deadline is a mistake. Title II has always prohibited disability discrimination in state and local services, and a website that creates real barriers can be challenged now under the general nondiscrimination requirement, without waiting for 2027 or 2028.²

What’s Excepted

Five categories of content don’t have to meet WCAG 2.1 AA. The exceptions are narrower than they look, so read the conditions closely.²

Archived web content, but only if it was created before the compliance date, is kept solely for reference or recordkeeping, lives in a designated archive area, and hasn’t been changed since archiving. A 2019 PDF still linked from an active service page doesn’t qualify.
Preexisting electronic documents (word processing files, PDFs, presentations, spreadsheets) posted before the compliance date. The exception disappears if the document is still being used to apply for or participate in a program. An old permit application form people still download and submit has to be made accessible.
Third-party content posted on a government website by members of the public, such as comments or reviews, when there’s no arrangement with the entity. Content from vendors or contractors doesn’t get this exception.
Password-protected individualized documents about a specific person, property, or account, like an individual utility bill or tax assessment.
Preexisting social media posts made before the entity’s compliance date. New posts after the deadline must meet the standard.

The Undue Burden Defense Is Narrow

A public entity can argue that a specific accessibility measure would impose an undue financial and administrative burden, or would fundamentally alter the nature of a service. The determination has to be made by the head of the entity (or a designee), after considering all resources available across the whole entity rather than just an IT budget, and it requires a written statement explaining the reasoning.⁷

Even a successful defense doesn’t end the obligation. The entity must still take alternative steps to provide access to people with disabilities to the maximum extent possible, such as offering a phone line or in-person alternative when an online form can’t be made accessible.⁵

Procurement Is a Compliance Decision

Most government sites and apps run on third-party software: payment processors, content management systems, scheduling platforms, document hosts. When services flow through those tools, the public entity carries the accessibility responsibility, and a vendor’s failure to build accessible software becomes the government’s compliance problem.⁵

Before you buy or renew a contract, request an Accessibility Conformance Report from the vendor. The common format is the Voluntary Product Accessibility Template, which documents how a product performs against accessibility standards and flags gaps.⁸ Build accessibility requirements into the contract itself and require updated reports when the vendor releases new versions.

Enforcement and Filing a Complaint

Anyone who runs into an inaccessible government website or app can file a complaint with the Department of Justice’s Civil Rights Division, online or by mail.⁹ DOJ may investigate, refer the matter to its ADA Mediation Program, or route it to another federal agency. Review can take up to three months; after that, you can check status by calling the ADA Information Line at 800-514-0301.

A DOJ complaint isn’t the only route. Title II provides a private right of action, so an individual can sue a public entity directly in federal court without waiting for a government investigation.⁵ Courts can order the entity to fix the problem and can award compensatory damages. Punitive damages are not available against government entities under Title II. The 2024 rule didn’t create this enforcement path, but by setting a concrete technical standard it gives plaintiffs and courts a clearer benchmark for judging whether a violation happened.