The DOJ Moved the Deadline. Your Municipal Client Is Going to Call. Here's What to Say.

The Call You Are About to Get

It is Tuesday morning. Your municipal client's IT director forwards you a link to a news article — the DOJ extended the ADA Title II web accessibility deadline by a year. The email has one sentence above the link: "Do we still need to do this?"

If you have been bidding on or delivering digital work to state and local governments for the last eighteen months, you have built your conversations, your scopes, and your invoices around April 24, 2026. That date is gone. On April 20, 2026 — four days before the original deadline — the Department of Justice published an Interim Final Rule that pushed the WCAG 2.1 Level AA compliance dates to April 26, 2027 for entities serving 50,000 or more people, and April 26, 2028 for everyone smaller. (Federal Register: 91 FR 20902, RIN 1190-AA82.)

Your client read a headline. They are going to ask you whether the work you scoped, the budget they approved, and the language in their RFP can all relax. The next thirty days are when those conversations happen. The contractors who handle them well are the ones who still have accessibility line items in their FY27 renewals. The ones who don't are the ones who agreed too quickly that everything could slow down — and then got descoped when procurement asked what they were paying for.

This post is the script for that call. The short version: the date moved, but the obligation, the state laws, the procurement language, and the litigation channel did not. The slightly longer version is below.

What the IFR Actually Did

The Interim Final Rule is short. It does exactly two things. It amends 28 CFR 35.200(b)(1) to change "April 24, 2026" to "April 26, 2027," and it amends 28 CFR 35.200(b)(2) to change "April 26, 2027" to "April 26, 2028." That is it. Every other word of the 2024 Title II final rule remains in effect.

DOJ's stated rationale rests on four threads woven through the IFR's preamble: that the Department overestimated how quickly covered entities could comply given staffing constraints, that generative AI has not delivered on automated remediation at scale, that WCAG 2.1's supplemental materials create some clarity concerns, and that the rule's litigation exposure is higher than originally modeled. The IFR also signals that DOJ may issue a separate Notice of Proposed Rulemaking during the extension period to revisit the substance of the 2024 rule. That second part is the one to watch — the dates moving is settled, but the substantive standard could be modified again before April 2027.

The procedural posture matters too. DOJ used the "good cause" exception under the Administrative Procedure Act to bypass notice-and-comment rulemaking. Lainey Feingold, the disability-rights attorney whose work has shaped most accessibility settlements of the last twenty years, has noted that this approach has never been used for an accessibility regulation. Ken Nakata, a former Senior Trial Attorney in DOJ's Disability Rights Section and now principal at Converge Accessibility, called several of the IFR's rationales legally weak in his April 17 commentary. A 60-day public comment period closes June 22, 2026 (docket DOJ-CRT-2026-0067). The American Association of People with Disabilities, the American Council of the Blind, and the National Federation of the Blind have all committed to filing opposition comments. Whether any of that produces an injunction or a date reversal before mid-2026 is unknown. The realistic planning baseline is that the new dates hold and the substance gets revisited in a future NPRM.

What the IFR Did Not Do

This is the part of the conversation your municipal client will not have read in the news article. The four channels below are what actually drive your accessibility work — and none of them moved on April 20.

| Channel | What changed on April 20 | |---|---| | WCAG 2.1 AA technical-standard date | Moved to April 26, 2027 (≥50K pop.) and April 26, 2028 (smaller entities) | | Underlying Title II obligation | Unchanged — still in force today | | State digital-accessibility laws | Unchanged — CO, VA, MA, MN, WA, CA operate independently of the federal date | | Municipal procurement language | Unchanged — VPAT and ACR demands hardening, not softening | | Demand-letter and litigation channel | Unchanged — 8,667 ADA filings in 2025, pro se filings up ~40% YoY | | DOJ enforcement posture | Unchanged — Alcazar v. Fashion Nova SOI (Feb 2026), Service Oklahoma settlement still on books |

The underlying Title II obligation never moved

The single most important sentence in the IFR's preamble is this one: covered entities have an ongoing obligation to ensure their services, programs, and activities offered through web content and mobile apps are accessible, in accordance with their existing obligations under Title II of the ADA. The technical-standard date is a deadline for conformance to a specific written standard. The duty to actually be accessible — to actually serve people with disabilities — is older than the rule and survives independently of it. A municipality whose website blocks a screen-reader user from paying a utility bill is violating Title II today, on May 4, 2026, regardless of what the conformance date says.

Every accessibility consultancy that has published guidance since the IFR landed has converged on this point. Deque, Siteimprove, Accessible.org, Converge Accessibility, Pivotal Accessibility, Aspiritech, Allyant, and on the government-vendor side CivicPlus — all of them are telling municipal clients the same thing: the deadline moved, the obligation didn't, keep going. The American Association of People with Disabilities called the delay "unconscionable" and on April 20 publicly commended the state and local governments moving forward on the original timeline. That is the institutional consensus your conversation has to take into account.

State laws did not move

The IFR is purely a federal regulation. State digital accessibility laws and procurement standards operate under their own statutes and their own timelines.

Colorado is the most aggressive. HB21-1110, codified at C.R.S. § 24-34-802, creates a private right of action in state court at $3,500 per violation plus actual damages and attorney's fees. The grace period under HB24-1454 expired on July 1, 2025 — Colorado is in active enforcement now, and has been for ten months. Virginia HB 2541 was signed by Governor Youngkin on March 24, 2025 and took effect for procurement contracts negotiated or renegotiated on or after July 1, 2025. The Virginia statute requires vendors to provide a third-party-evaluated Accessibility Conformance Report — self-attested VPATs do not satisfy the law. Failure to remediate within twelve months triggers contract credit up to $10,000 or cancellation with reimbursement.

Massachusetts requires accessibility conformance reports no older than twelve months and explicitly bans accessibility overlays in vendor contract language. Minnesota carries a $500-per-violation statutory penalty for inaccessible public records under § 363A.42. Washington's WaTech standard USER-01-01-S (approved December 10, 2024) references WCAG 2.2 Level AA. California's AB 2190 — currently active in the 2025–26 legislative session, and not the dead AB 1757 from the prior session — would impose direct civil liability on web developers and contractors who negligently or recklessly construct inaccessible websites for covered entities.

None of those statutes care what the federal date says. A municipal contractor working in Colorado, Virginia, Massachusetts, Minnesota, Washington, or California has obligations that are not affected by the April 20 IFR at all. The next post in this series, on May 18, will map all of them.

Procurement language is hardening, not softening

This is the part that catches contractors off-guard. Most municipalities that adopted accessibility-gating language in their FY2025 RFPs are not pulling it back in FY2026. The reverse is happening. Virginia's VITA published an April 14, 2026 implementation memo for HB 2541 vendor language. Massachusetts EOTSS continues to require ACRs no older than twelve months as a procurement gate. Minnesota's Office of State Procurement is adding pre-qualified accessibility vendors to its Master Contract Program — a procurement-ready short list that excludes contractors who can't demonstrate documented compliance work.

The procurement officials I've seen quoted publicly are saying versions of the same thing: the federal date moving doesn't change the city's exposure, doesn't change the underlying ADA obligation, and doesn't change what state law and the city attorney want to see in vendor files. The contracts they signed last year with accessibility clauses are not getting amended — they are getting renewed.

Litigation did not slow down

Per the Seyfarth Shaw 2025 federal-filings analysis published February 11, 2026, there were 8,667 ADA Title III lawsuits filed in or removed to federal district courts in 2025 — only two percent fewer than 2024. Government entities represented approximately fourteen percent of cases, roughly double the 2024 rate. Federal pro se ADA Title III filings rose roughly forty percent year-over-year, with pro se plaintiffs filing more lawsuits in the first nine months of 2025 than in all of 2024 combined. UsableNet's mid-year analysis found that forty-six percent of federal accessibility cases in the first half of 2025 involved repeat defendants. EcomBack reported that website-accessibility lawsuits surged thirty-seven percent in the first half of 2025, with Illinois federal filings up 745 percent over the same period.

DOJ's own posture has not relaxed either. On February 2, 2026, the Department filed a Statement of Interest in Alcazar v. Fashion Nova opposing a $5.15 million website-accessibility class settlement as inadequate. The Service Oklahoma settlement requiring WCAG 2.1 AA conformance for mobile apps remains on the books. The Alaska elections letter of findings from June 2024 remains on the books. The IFR moved a regulatory date. It did not pause the agency.

The Conversation Script

Now to the actual call. Your municipal client's IT director or city attorney will open with some version of "do we still need to do this?" The structure of a good response has three parts.

Open by acknowledging what changed. Yes, the DOJ extended the technical-standard date by a year. The headline is correct. Your client is not wrong to have noticed.

Then explain what didn't change. The Title II obligation is still in force today. The state law your municipality operates under (Colorado, Virginia, Massachusetts, whatever it is) does not reference the federal date and was not extended. Procurement language already in your contracts has not been modified. Demand letters are not slowing down — federal ADA Title III filings stayed essentially flat in 2025, government entities are a growing share of cases, and pro se filings spiked forty percent. The remediation work you were going to do still needs to be done; the only thing that changed is when the DOJ technical-standard date arrives.

Close by reframing the runway. The right way to use the extra year is not as a pause — it is as the breathing room to do the work properly rather than ship a procedural box-check. That is exactly the framing Deque, Siteimprove, and Accessible.org are using publicly. It also happens to be the right frame for keeping accessibility scope in the contract: a municipality that uses the runway to deepen remediation, complete a full audit, and document a conformance posture is in a meaningfully stronger legal position by April 2027 than one that uses the runway to do nothing. That is the difference between paying for results and paying for a date.

If your client pushes back — "can't we just defer all the accessibility line items to FY28?" — your counter is direct. Title II is in force today. The first demand letter your client receives will not care that the DOJ pushed the conformance date. The audit defense log we have been building, the accessibility statement we drafted, the audit defense documentation — all of those are protective regardless of the federal date. Slowing the procurement of accessibility work does not change the underlying exposure; it just leaves the city with less documentation when something happens.

If the client still wants to amend the contract, the question to ask before signing anything is whether the city attorney has reviewed the proposed change. In every state-law jurisdiction listed above, the city attorney has independent reasons to keep the accessibility language intact. Letting them say no on your behalf is sometimes the cleanest exit from a conversation that would otherwise descope your work.

What to Do in the Next Thirty Days

For the contracts in your active book of business, three short tasks. Each one takes less than an hour and each one closes a specific risk.

Send a one-page memo to every active municipal client. Two paragraphs. Paragraph one acknowledges the IFR and the new dates. Paragraph two explains the four channels above and confirms that your scope, your invoicing, and your remediation timeline remain unchanged. Send it before your client asks. Contractors who lead with this conversation control the narrative; contractors who wait for the question are answering on their client's terms.

Audit your FY27 renewals for accessibility line items. If you have FY27 renewals that priced accessibility work assuming an April 24, 2026 hard stop, those line items are now exposed to "we don't need it this year" pushback at renewal time. Decide now what your defense is for each one. Most of the time the defense is one of the four channels above. Sometimes the defense is a state law your client may not be tracking. Either way, do the work in May, not in October.

Update your standard MSA and SOW templates. If your contract templates reference April 24, 2026 anywhere — in a recital, in a deliverable date, in a milestone — those references need to come out before your next bid goes out. Replace specific federal-date language with the broader Title II / state-law / procurement-conformance language used in the original deadline post. The substantive obligation does not depend on the federal date and your contract language should not either.

What Comes Next

In two weeks (May 18) the next post in this series will be the state-law map: a single contractor reference for every state-level digital accessibility statute that did not move when DOJ moved the federal date. If you serve municipalities in Colorado, Virginia, California, Massachusetts, Minnesota, Washington, Maryland, or Illinois, that post will be the one to bookmark.

The DOJ also signaled in the IFR that a substantive NPRM may be coming during the extension window — a separate rulemaking that could revisit WCAG 2.1 versus 2.2, the conformance level, the exceptions, or any combination. That is the federal action worth watching for the rest of 2026. The dates are settled. The substance might not be.

In the meantime, the right frame for the next twelve months is the one most accessibility consultancies converged on within seventy-two hours of the IFR: a year of additional runway is not the same as a year of pause. The contractors who treat it as runway — to deepen remediation, document conformance, harden procurement language, and finish work that would have been rushed — are the ones who reach April 26, 2027 with a defensible posture. The ones who treat it as pause are the ones who get the demand letter call on a Tuesday afternoon and have nothing to show.

The clock did not stop on April 20. The face just changed.