The ADA Title II Web Rule: New Deadlines, and Why They May Not Hold

For decades, US public bodies knew the Americans with Disabilities Act applied to their websites but had no technical standard telling them what that meant. In April 2024 that changed: the Department of Justice published a final rule under Title II of the ADA adopting a specific, testable standard for state and local government web content and mobile apps.

Then, four days before the first compliance deadline arrived, the DOJ postponed it by a year. And a month after that, it was sued over the postponement.

If you work for or with a US public entity, this is the sequence you need to understand — because the current deadlines are real, and they are also contested.

What the rule requires

The rule was published in the Federal Register on 24 April 2024 and took effect on 24 June 2024, adding a new subpart to the Title II regulations.

The technical standard is WCAG 2.1 Level AA — both the Level A and Level AA success criteria, plus the conformance requirements. Not WCAG 2.0, which Section 508 still uses for federal agencies, and not WCAG 2.2, which is the current version of the standard.

It applies to the web content and mobile applications of state and local government entities: cities, counties, school districts, public universities, transit authorities, courts, public hospitals, libraries, special districts.

The rule contains meaningful exceptions, and they are worth knowing because they materially reduce the work. Archived web content meeting a four-part test is excluded. So are pre-existing conventional electronic documents — word processing files, presentations, PDFs, spreadsheets — that were posted before the compliance date, unless they are currently used to apply for or access a service. So is third-party content not posted by or for the entity, individualised password-protected documents, and pre-existing social media posts. There are also allowances for conforming alternate versions, and for non-conformance with a minimal impact on access.

The deadlines, as they now stand

The original rule set compliance by population served, using 2020 Census data.

On 20 April 2026, the DOJ published an interim final rule, effective immediately, extending both dates by one year:

• Public entities serving a population of 50,000 or more: originally 24 April 2026, now 26 April 2027.
• Public entities serving fewer than 50,000, and all special district governments: originally 26 April 2027, now 26 April 2028.

The DOJ's stated reasons were that it had overestimated the staffing and technological capacity of covered entities; that generative AI cannot reliably automate remediation of inaccessible content at scale; that rushed compliance carried its own litigation risk; and that certain content, particularly STEM material, is genuinely difficult to remediate. The Department also signalled it may reconsider whether parts of the 2024 rule could be made less costly.

A parallel extension happened on the healthcare side: the Department of Health and Human Services had adopted WCAG 2.1 AA for recipients of its financial assistance with deadlines in May 2026 and May 2027, and issued its own interim final rule in May 2026 pushing those to May 2027 and May 2028.

Why the extension may not survive

On 21 May 2026, the National Federation of the Blind filed suit in the US District Court for the District of Maryland against both the DOJ and HHS.

The claims are procedural and substantive. Procedurally, both agencies issued interim final rules, which take effect immediately without the usual notice-and-comment period — and the complaint argues that skipping notice and comment violated the Administrative Procedure Act. Substantively, it argues the extensions were arbitrary and capricious: that the DOJ failed to weigh the harm to disabled people who continue to be excluded, and that HHS relied on anecdotal evidence.

The relief sought is not damages. It is a declaration that the interim final rules are unlawful, vacatur of the extensions, and reinstatement of the original 2024 deadlines.

At the time of writing no ruling has been reported. That leaves covered entities in an uncomfortable but clear position: the extended deadlines are currently in effect, and they are under active challenge. If the court vacates the extensions, the original dates could return — and the first of those has already passed.

What a sensible public entity does now

Treat the extension as breathing room, not as a reprieve. Three reasons.

The underlying obligation predates the rule. Title II has always required effective communication and program accessibility. The 2024 rule supplied a technical standard; it did not create the duty. An entity with an inaccessible website was exposed before April 2024 and remains exposed now, extension or no extension. Private plaintiffs and DOJ enforcement under the general obligation do not wait for the technical deadline.

The litigation could remove the extension. Planning to the extended date and losing that date leaves you with no runway at all.

State law may not have moved. Federal extensions do not change state obligations. Colorado, for example, requires state agencies and local government entities to meet WCAG 2.1 AA under its own statute, with rules finalised in May 2025 — and Colorado's technology office has said plainly that "a federal delay does not change our legal requirements here at home. In Colorado, we have our own laws that are independent of federal timelines." Several other states have their own IT accessibility laws and policies. Check yours.

Where to start if you are behind

The work does not begin with reading the standard. It begins with knowing what you have.

Inventory first. Most public entities do not know how many web properties they own. Departmental microsites, event sites, legacy applications and third-party portals all count. The exceptions for archived content and pre-existing documents are only useful if you can identify which content qualifies.

Prioritise by service, not by page count. The rule's purpose is that people can access programs and services. Benefit applications, permit processes, school enrolment, court forms, bill payment and emergency information matter more than the parks department photo gallery.

Deal with the document problem early. For most public entities the largest volume of inaccessible content is PDFs, and the exception for pre-existing conventional documents does not cover anything currently used to apply for or access a service — which is precisely the set of documents that matters most.

Get your third-party vendors on record. Much of a public entity's digital estate is procured software: payment portals, registration systems, learning platforms. Ask each vendor for an Accessibility Conformance Report and check that it addresses the right standard rather than being a marketing document.

Test continuously, not once. Sites change weekly. The UK's public sector monitoring programme found that when it retested 47 websites it had already assessed and notified, only three had no issues. A one-off remediation project without ongoing testing decays quickly.

*Rule details and dates are from the Federal Register: the Title II final rule published 24 April 2024, the interim final rule extending compliance dates published 20 April 2026, and the HHS interim final rule published 11 May 2026. The NFB lawsuit was filed 21 May 2026 in the US District Court for the District of Maryland; no ruling had been reported at the time of writing. This is general information about published regulation, not legal advice.*