Is the ADA Title II Deadline Still Happening? A 2026 FAQ for Government Contractors

Updated May 22, 2026. The DOJ public comment period on the Interim Final Rule closes June 22, 2026; the HHS comment period closes July 6, 2026. This page is maintained as those dates approach.

The short version: yes, the federal deadline moved, but almost nothing else did. If you deliver digital work to municipalities, the extension is far less of a reprieve than the headlines suggest — and in several states the binding deadline is now earlier than the federal one. Here are the questions government contractors are actually asking, answered in order.

Did the ADA Title II web accessibility deadline get extended?

Yes. On April 20, 2026, the Department of Justice extended the compliance dates by one year. The new dates are April 26, 2027 for public entities serving 50,000 or more people, and April 26, 2028 for smaller entities and special-district governments.

The change came through an Interim Final Rule published in the Federal Register (91 FR 20902, RIN 1190-AA82). It took effect immediately on publication, four days before the original April 24, 2026 deadline would have hit. The rule amends 28 CFR 35.200(b) — the section that sets the conformance dates — and changes only the dates.

Is the April 2026 ADA deadline still in effect?

No. The original April 24, 2026 deadline has been replaced. Public entities serving 50,000 or more now have until April 26, 2027. Everyone smaller has until April 26, 2028.

If you scoped, bid, or invoiced municipal work around an April 2026 hard stop, that specific date is gone. But — and this is the part that matters for your contracts — the underlying legal obligation to provide accessible digital services did not go anywhere. More on that below.

What did the DOJ actually change in the April 20, 2026 Interim Final Rule?

Two dates. Nothing else. The rule moved the WCAG 2.1 Level AA conformance deadline for large entities from April 24, 2026 to April 26, 2027, and for smaller entities from April 26, 2027 to April 26, 2028.

Everything else in the 2024 Title II rule stayed exactly as written:

• The technical standard is still WCAG 2.1 Level AA.
• The scope of covered web content and mobile apps is unchanged.
• The five exceptions (archived web content, preexisting conventional electronic documents, third-party content not posted under contract, individualized password-protected documents, and preexisting social-media posts) are unchanged.
• The underlying Title II obligation to not discriminate on the basis of disability is unchanged and remains in force today.

DOJ was explicit in the rule's preamble that it "fully anticipates implementing the regulation at the new deadline." This is a delay, not a repeal.

Did WCAG 2.1 Level AA change?

No. The conformance standard is still WCAG 2.1 Level AA. The work required to make a site or app conform is identical to what it was on April 19, 2026 — the only thing that moved is when the federal clock runs out.

This matters for contractors because your deliverable spec did not change. A municipal website that needed to meet WCAG 2.1 AA in March still needs to meet WCAG 2.1 AA. If your statement of work referenced the standard, that reference is still accurate. If it referenced the April 2026 date, that reference now needs updating — but the substantive target is the same.

Did the HHS healthcare accessibility deadline also move?

Yes. On May 7, 2026, HHS extended its parallel Section 504 deadline by a year. Recipients of HHS funding with 15 or more employees now have until May 11, 2027; smaller recipients have until May 10, 2028.

This matters if you serve healthcare-adjacent government clients — county hospitals, public health departments, federally qualified health centers, Medicaid-funded clinics. Those entities are often covered by both Title II (because they are state or local government) and Section 504 (because they take HHS money). Both of their federal deadlines moved in lockstep. The HHS comment period closes July 6, 2026.

The pattern is now clear: the federal agencies are extending across the board. The state governments, as the next answer explains, are not.

Does the extension stop ADA lawsuits?

No. The extension moves a regulatory conformance date. It does not pause the Americans with Disabilities Act, and it does not slow down private litigation.

For scale: according to the Seyfarth Shaw ADA Title III blog, there were 8,667 ADA Title III lawsuits filed in or removed to federal district courts in 2025 — only about 2% fewer than 2024. (Title III covers private businesses; Title II covers government. The point is that accessibility litigation as a whole has not slowed, and government-entity cases have been a growing share of filings.) Title II carries a private right of action and fee-shifting, which means a plaintiff's attorney can recover fees for a successful claim — the economic engine behind accessibility litigation is fully intact.

A municipality whose website blocks a screen-reader user from paying a utility bill is exposed to a Title II claim today, on May 22, 2026, regardless of the conformance date. The first demand letter your client receives will not care that DOJ moved the calendar.

Does my municipal client still need WCAG 2.1 AA in my contract?

Yes — and you should resist any move to strip it out. The conformance standard did not change, the underlying obligation did not change, and the state-law and procurement requirements did not change. A contract that drops accessibility scope because "the deadline moved" leaves your client more exposed, not less, and leaves you with weaker documentation if a claim arrives.

There is also a flow-down dimension specific to contractors. Under Title II's "provides or makes available" framework, a public entity is responsible for accessibility even when the inaccessible content was built or supplied by a vendor. That responsibility flows through procurement language and indemnification clauses to you. The federal extension does nothing to interrupt that chain. If anything, the extra year is the window to get your deliverables genuinely conformant rather than rushed — which is the stronger contractual and legal position for both you and your client.

If a client asks to defer all accessibility line items to FY28, the cleanest response is to point them to their own city attorney, who in most of these states has independent state-law reasons to keep the requirements intact.

Did state digital accessibility laws change?

No. None of the major state laws moved when the federal date moved. This is the single most important point for contractors working multiple state markets, because in several states the state deadline is now earlier than the federal one.

• Colorado (HB21-1110): Live enforcement since July 1, 2025. Per the Colorado Office of Information Technology, the grace period expired and government entities must now demonstrate compliance or face liability. Damages run at $3,500 per violation, plus actual damages and attorney's fees, through a private right of action in state court.
• Virginia (HB 2541): The statute wrote the compliance dates April 24, 2026 and April 26, 2027 directly into Virginia law — the original federal dates — and the federal IFR did not change them. Virginia covered entities have a state deadline that is now earlier than the federal deadline. The statute also requires third-party-evaluated Accessibility Conformance Reports; self-attested VPATs do not satisfy it.
• Massachusetts: EOTSS enterprise standards require accessibility conformance reports under twelve months old, both automated and manual testing, and explicitly prohibit accessibility overlays in vendor contracts.
• Minnesota: Statute § 16E.03 ties procurement to the state accessibility standard, and §§ 363A.42–363A.43 carry $500-per-violation penalties for inaccessible public records.
• Washington: WaTech Standard USER-01-01-S references WCAG 2.2 Level AA — a step ahead of the federal WCAG 2.1 AA baseline.
• California: The Unruh Civil Rights Act incorporates ADA violations with statutory damages of $4,000 per violation, and two active bills (AB 2190 and AB 1757) would extend liability directly to web developers and contractors.

We covered all six in detail in The State Laws That Didn't Move. If you serve any of these markets, that post is the companion to this one.

Is DOJ planning more changes to the rule?

Possibly. In the Interim Final Rule, DOJ signaled it may issue a separate Notice of Proposed Rulemaking during the one-year extension window to revisit aspects of the 2024 rule — potentially the WCAG version, the conformance level, or the exceptions. As of May 22, 2026, no such NPRM has been published or sent to the Office of Information and Regulatory Affairs.

What this means for contractors: the dates are a settled planning baseline, but the substance of the rule is not guaranteed to stay fixed. Watch the Federal Register through the rest of 2026. If a substantive NPRM appears, the conformance target itself could shift before April 2027.

When does the public comment period close?

June 22, 2026 for the DOJ rule; July 6, 2026 for the HHS rule. Both rules were issued as Interim Final Rules, which take effect immediately but still invite public comment.

The DOJ docket is DOJ-CRT-2026-0067 on regulations.gov. If you have a contractor's-eye view of the practical impact — for example, how the date change is affecting municipal procurement scopes or vendor pricing — that is exactly the kind of real-world input the comment process is designed to capture. Disability rights organizations including the National Federation of the Blind have already filed opposition to changes to the rule; the contractor and procurement perspective is comparatively underrepresented in the record.

Could the IFR be pulled or struck down?

It is possible, though no challenge has been filed as of May 22, 2026. DOJ issued the rule using the Administrative Procedure Act's "good cause" exception to skip notice-and-comment rulemaking. Some legal commentators have questioned whether that justification holds, since the 2024 rulemaking record already evaluated a longer compliance timeline as an alternative. A successful APA challenge could theoretically vacate the extension and snap the original dates back into place.

Disability advocacy organizations have condemned both IFRs in writing — the National Federation of the Blind's leadership filed a letter opposing changes to the rule, and a coalition led by the American Association of People with Disabilities issued a statement against the HHS extension. None has filed suit yet. The realistic contractor posture is to plan to the new dates while keeping the original dates in mind as a downside scenario, because a court could in principle restore them.

What should a municipal contractor do between now and April 2027?

Five concrete moves. Each one protects your contracts regardless of what happens federally.

1. Send a one-page memo to every active municipal client. Acknowledge the new dates, then confirm that your scope, invoicing, and remediation timeline are unchanged because the underlying obligation and the state laws did not move. Lead the conversation before your client asks.

2. Audit your contract templates for hardcoded dates. Anywhere your MSA or SOW references "April 24, 2026," replace it with language tied to WCAG 2.1 AA (or the higher applicable state standard) and the underlying Title II obligation. The standard, not the calendar, is what your contract should reference.

3. Use the extra year to do the work properly. A municipality that uses the runway to complete a full audit, document conformance, and build an audit defense log reaches April 2027 in a defensible position. One that uses it to do nothing reaches April 2027 with the same problems and twelve fewer months of documentation.

4. Check which state laws bind your clients. If you work Colorado, Virginia, Massachusetts, Minnesota, Washington, or California, the binding deadline may already have passed or may be earlier than the federal one. Map your portfolio against the state-laws guide.

5. Keep your accessibility documentation current. A current accessibility statement and a clean conformance record are what protect your client — and you — when a demand letter arrives. The extension does not change what good documentation looks like; it just gives you more time to build it.

---

For the full breakdown of the April 20 rule and a script for the "do we still need to do this?" call you are getting from clients, see The DOJ Moved the Deadline — Here's What to Say. For the broader context on how the federal extension fits into the picture of ongoing obligations, see Title II After the Deadline.

The deadline moved. The obligation, the lawsuits, the state laws, and the contract language did not. Plan accordingly.