ADA Title II Deadline Extension: The New 2027 and 2028 Dates

The Department of Justice has extended the ADA Title II web accessibility deadlines by one year. Under an interim final rule published in the Federal Register on April 20, 2026, state and local governments with a population of 50,000 or more now have until April 26, 2027 to comply, and smaller public entities and special district governments have until April 26, 2028. The required standard did not change: it is still WCAG 2.1 Level AA.

Most coverage of this news is written for city attorneys. This post is for the other people who actually have to hit the date — the web shops, freelancers, and in-house developers who build and maintain sites for cities, counties, school districts, transit agencies, and public universities. Here is what changed, what didn’t, and what the extra year is actually for.

What are the new Title II compliance dates?

The extension moves each deadline back one year from the dates set in the original 2024 rule. The DOJ published the interim final rule on April 20, 2026 — four days before the first deadline would have hit — and it took effect the same day; the public comment window closed June 22, 2026 (Federal Register).

Note which population figure applies: the rule uses the total population of the government entity, so a county web portal and a small village site can sit on different deadlines even if the same contractor builds both. If you serve a mix of clients, you now have two dates to track, not one.

What didn’t change in the Title II web rule?

Everything except the dates. The technical standard is still WCAG 2.1 Level AA, and the rule’s scope, coverage, and exceptions remain exactly as adopted in April 2024, as law firm Reed Smith’s analysis confirms. Mobile apps are still covered. The limited exceptions for archived content and certain third-party material are unchanged. We walk through all of that in our explainer on the DOJ Title II web rule.

The DOJ also made clear this is a delay, not a retreat. In its alert on the extension, Duane Morris notes the Department stated it “fully anticipates implementing the regulation at the new deadline.”

One thing to watch: Reed Smith reports the DOJ signaled it plans a future notice of proposed rulemaking that could revisit parts of the rule. That is a maybe-someday. The April 2027 date is on the books now, and building to a rumor instead of a regulation is how agencies and their vendors end up scrambling.

Why did the DOJ extend the deadline?

The Department’s own explanation is unusually blunt: it said it had “overestimated the capabilities (whether staffing or technology) of covered entities to comply” within the original timeframes, according to the Duane Morris alert on the interim final rule. Public entities could not find enough skilled people, and the tools they hoped would do the work for them did not deliver.

The most interesting sentence in the rule is about AI. The DOJ wrote that generative AI “does not yet reliably automate the remediation of inaccessible content at scale” (Federal Register IFR), and Duane Morris notes the Department specifically cited the unreliability of automated remediation tools on complex material like educational and STEM content.

Read that again if a vendor is pitching you an AI-powered compliance shortcut. The federal agency that wrote the accessibility rule looked at automated remediation and concluded it could not close the gap — which is why the fix was more time for human work, not a blessing for more tooling. That matches what we found when we tested whether AI can make a website ADA compliant, and it is consistent with what automated scanners miss even before remediation enters the picture.

Does the extension pause litigation risk? No.

The extension changed when the web-specific rule kicks in. It did not pause the ADA. Title II’s general nondiscrimination and effective-communication obligations have applied to government digital services all along, and they still do during the extension. Duane Morris put it plainly: “Private plaintiffs and advocacy organizations can (and likely will) still sue during the extension period” (Duane Morris).

The disability community’s reaction shows how live that risk is. The American Association of People with Disabilities called the extension “a profound disappointment and a serious setback,” with President and CEO Maria Town adding that “the Department is rewarding inaction with more time” (AAPD statement).

Then came the lawsuit. On May 21, 2026, the National Federation of the Blind sued both the DOJ and HHS in the U.S. District Court for the District of Maryland, arguing the agencies violated the Administrative Procedure Act by skipping notice and comment and that the extensions were arbitrary and capricious (Deque’s summary of the NFB suit). If the NFB wins, the original deadlines could be restored — meaning an agency that spent the extra year idle would be instantly behind. Meanwhile, private-sector ADA suits never slowed; see the lawsuit numbers for how active the plaintiffs’ bar remains.

Did the HHS Section 504 deadline move too?

Yes — on its own track. Recipients of HHS funding (hospitals, clinics, health departments, and other healthcare organizations) face a parallel web accessibility requirement under Section 504. Per Deque’s breakdown, HHS extended its dates as well: recipients with 15 or more employees now have until May 11, 2027 (was May 11, 2026), and smaller recipients until May 10, 2028 (was May 10, 2027).

Both extensions are named in the NFB’s lawsuit, so both sets of dates carry the same asterisk. If you build for a county health department, you may be covered by Title II and Section 504 at once — two rules, one standard, and now two clocks that a court could reset.

What should web shops and contractors do before April 2027?

Treat April 26, 2027 as a delivery date, not a start date. A year sounds like a lot until you multiply it across every site, portal, PDF library, and mobile app a public entity runs. Here is the order of operations we recommend:

1. Inventory every property you’re responsible for. Main site, department microsites, payment portals, board-meeting archives, mobile apps, and the PDFs — public-entity sites are usually buried in them.
2. Audit against WCAG 2.1 AA now. A real accessibility audit — automated scanning plus manual keyboard and screen-reader testing — tells you the true size of the job while there is still budget-cycle time to fund it.
3. Fix it in the code, not on top of it. The DOJ just said automated remediation can’t reliably do this at scale. Manual remediation of the actual HTML, ARIA, and content is the work the extra year was granted for.
4. Write WCAG 2.1 AA into contracts and RFP responses. Agencies are going to start asking vendors to warrant conformance. Being able to document your process — or hand over a VPAT / conformance report — is becoming a bid requirement, not a bonus.
5. Document progress as you go. With the NFB case pending, dated audit reports and remediation logs are your proof of good faith under any deadline a court lands on.

The one-year extension is real, but every signal around it says the same thing: the standard is settled, the enforcement date is coming, litigation never paused, and the shortcut tools were just ruled out by the government itself. The contractors who win public-entity work in 2027 will be the ones who spent 2026 doing the manual work.

If you build or maintain a government site and want to know where it stands today, run a free accessibility scan — it takes minutes and gives you the baseline your audit plan starts from.