ADA Title II Web Rule: 2027–2028 Deadlines

If your organization is a city, county, state agency, public university, school district, transit authority, court system or a utility run by a government, the ADA Title II web rule applies to your websites and mobile apps. This article explains what the rule requires, who it covers, what changed on April 20, 2026, what is still open in court, and how vendors that build for public clients should plan for 2026 to 2028. For the US overview, see our USA compliance page.

What the ADA Title II web rule requires

Title II of the Americans with Disabilities Act prohibits disability discrimination by state and local governments. In April 2024 the Department of Justice issued a final rule under Title II that sets a specific technical standard for the web content and mobile apps of these entities for the first time: WCAG 2.1 Level AA (89 FR 31320, April 24, 2024).

WCAG is organized around four principles: content must be perceivable, operable, understandable and robust. Level AA includes requirements that many public sites fail in practice, such as:

• Text contrast of at least 4.5:1, or 3:1 for large text
• Every function usable with a keyboard alone, with visible focus
• Text alternatives for meaningful images, and labeled form fields
• Captions for prerecorded video

Who is covered: public entities, not private businesses

The rule applies to “public entities” as defined in the Title II regulation at 28 CFR 35.104. That definition covers any state or local government, and any department, agency, special purpose district or other instrumentality of a state or local government.

In our reading, that reaches a wide range of public bodies:

• State agencies, cities, counties and townships
• Public universities and community colleges
• Public school districts and public schools
• Public transit agencies and other special districts
• Courts and municipally owned utilities

If you are unsure whether your organization falls under the definition, ask your counsel. Private businesses are not covered by Title II. A private online store, bank or hospital falls under Title III of the ADA, which has no specific federal web standard but is applied to websites in private lawsuits.

The new deadlines after the April 2026 interim final rule

On April 20, 2026 DOJ published an interim final rule (91 FR 20902, FR Doc. 2026-07663) that extended both compliance dates. The rule took effect on publication, and public comments were due June 22, 2026.

The extension changes timing only. DOJ wrote that it had “overestimated the capabilities (whether staffing or technology) of covered entities,” and that “advanced technology, such as generative AI, does not yet reliably automate the remediation of inaccessible content at scale.” DOJ also said it “fully anticipates implementing the regulation at the new deadline” absent a further proposed rule or new circumstances. Plan around the new dates, not around the hope of another delay.

The NFB lawsuit: still open

On May 21, 2026 the National Federation of the Blind filed suit against DOJ and HHS in the U.S. District Court for the District of Maryland (No. 1:26-cv-02007). According to coverage of the complaint, the plaintiffs argue that the extensions were issued without the notice-and-comment process the Administrative Procedure Act normally requires, and that the delay was arbitrary. They ask the court to declare the interim rules unlawful.

In the most recent coverage we found (June 2026) there was no ruling on the merits or any injunction, and the Clearinghouse listing shows the case as ongoing. Check the docket on PACER or CourtListener for the current status. Disability Scoop reported that DOJ indicated it might reopen the rule for changes.

What happens if a government misses the deadline

Title II gives individuals a private right of action. The interim final rule states that private plaintiffs can obtain injunctive relief and attorneys’ fees for noncompliance, and that because of the private right of action DOJ “does not have the option to take no enforcement action.”

We did not verify a Title II dollar penalty schedule, so this article does not quote one. The practical exposure is a court order requiring remediation, plus the other side’s legal fees, and the reputational cost of a public case.

Private businesses face different numbers under Title III. DOJ civil penalties can reach $118,225 for a first violation and $236,451 for later ones (28 CFR 85.5, amounts adjusted in July 2025 that DOJ kept for 2026). Federal private suits under Title III give injunctive relief and attorneys’ fees, but no compensatory or punitive damages. According to Seyfarth Shaw, federal website accessibility lawsuits reached 3,117 in 2025, up from 2,452 in 2024.

Why vendors and contractors should prepare now

The obligation sits with the public entity, but governments buy most of their websites, apps and content platforms from outside vendors. A government that must meet WCAG 2.1 AA by April 2027 will want its vendors to show the same thing. This is a practical prediction about procurement, not a legal finding. In practice it tends to appear as accessibility questions in bids, contract clauses on WCAG conformance and requests for documentation.

For example, an agency that maintains twenty city websites on one shared theme can fix a template once and reach every site, but it will be asked to prove it. Start with the following:

• Document current conformance for each product you sell to public clients, in a dated accessibility conformance report such as a VPAT or equivalent
• Fix shared templates and components first, since one fix reaches every client site built on them
• Add WCAG 2.1 AA checks to your release process, not only to a one-time audit
• Review existing contracts for accessibility warranties, support obligations and who pays for remediation

A 2026–2028 roadmap

The milestones below are suggested internal targets. Only the April 26 dates are compliance dates set by the rule.

1. 1Inventory now (Q4 2026). List every public website and mobile app, including third-party platforms, PDFs and embedded tools. Name one owner for accessibility.
2. 2Test key pages (Q4 2026). Run an automated scan of key templates and high-traffic pages, then add manual keyboard and screen reader tests. A free audit is a fast starting point, not a final conformance finding.
3. 3Prioritize blocking barriers (Q1 2027). Fix failures that stop people from completing tasks first: login, forms, checkout, payment, and navigation. Fix shared templates before single pages.
4. 4Update procurement (Q1 2027). Put WCAG 2.1 AA into new RFPs and contract renewals, and ask vendors for conformance documentation.
5. 5Meet the first date (April 26, 2027). For entities with 50,000 or more people, aim to have the main services fixed and a dated record of remaining work.
6. 6Build it into releases (2027). Test each change before launch, set rules for PDFs and images, and retest after every redesign or platform update.
7. 7Meet the second date (April 26, 2028). Smaller entities and special districts finish remaining fixes and complete a final retest.
8. 8Watch the courts (ongoing). Track the NFB case and any final rule, and update your plan if either changes the dates.

This article is general information, not legal advice. Talk to your counsel about how the ADA Title II rule applies to your organization.