Ten Days Left to Comment on the DOJ Extension — and the Lawsuit That Could Erase It

The Two Things That Happened While You Were Bidding

If you have been following this series since the DOJ published its April 20 Interim Final Rule, you know the headline facts: the Title II WCAG 2.1 AA technical-standard dates moved to April 26, 2027 and April 26, 2028, the underlying ADA obligation did not move, and the state laws that govern most of your procurement work did not move either.

Two things have happened since that deserve your attention this week, because both of them have hard dates attached.

First, the public comment period on the DOJ's Interim Final Rule closes June 22, 2026 — ten days from this post. The docket is DOJ-CRT-2026-0067 on regulations.gov, and the electronic system accepts comments until midnight Eastern Time on the last day. The parallel HHS Section 504 comment period runs until July 6.

Second — and this is the one most contractors have not heard — on May 21, 2026, the National Federation of the Blind sued the Department of Justice and the Department of Health and Human Services in the U.S. District Court for the District of Maryland, asking the court to declare both Interim Final Rules unlawful and vacate them entirely. If that lawsuit succeeds, the extension disappears and the original compliance dates snap back into place.

Read those two facts together and the posture for the next ten days becomes clear. The comment window is the one moment when the small-vendor perspective — your perspective — can enter the official record that shapes what DOJ does next. And the lawsuit is the reason the "extra year" your municipal clients think they have should not be treated as settled. This post covers both: what is actually in the docket, why the contractor voice is the missing one, the fifteen-minute mechanics of filing, and what the lawsuit means for how you plan the rest of 2026.

The Lawsuit: NFB v. DOJ

The NFB's complaint, filed by Democracy Forward and the Baltimore civil-rights firm Brown, Goldstein & Levy, challenges both extensions under the Administrative Procedure Act. The legal theory tracks the criticism that has followed the IFR since the day it published. DOJ skipped the normal notice-and-comment process by invoking the APA's "good cause" exception — an exception that, as disability-rights attorney Lainey Feingold noted in April, has never before been used for an accessibility regulation. The NFB argues the good-cause justification does not hold, that the extension was arbitrary and capricious, and that the court should vacate both the DOJ and HHS rules and order the agencies to enforce the original deadlines. The complaint goes further and asks the court to declare the interim-final-rule mechanism itself unlawful as the agencies used it here.

Nobody can tell you how that case comes out, and this post is not going to pretend otherwise. What a contractor can do is plan against both branches. If the court upholds the IFR, the 2027/2028 dates hold and nothing about your current posture changes. If the court vacates it, the original dates — April 24, 2026 for large entities, already passed — are restored, and every municipality that used the extension as a reason to pause is suddenly out of compliance with the technical standard on day one.

That second branch is not a remote hypothetical you can ignore in client conversations. It is the precise downside scenario the May 22 FAQ post flagged when it said a successful APA challenge "could theoretically vacate the extension and snap the original dates back into place." The theoretical challenge is now a filed case with a docket number and serious counsel. When your municipal client's IT director asks whether the work can wait until 2027, the honest answer just got shorter: a federal court is actively being asked to take that year away, and the state laws never gave it to you in the first place.

The planning move is the same one this series has recommended since April: treat the extension as runway, not pause. The contractor who keeps remediating, keeps documenting in the audit defense log, and keeps the accessibility line items in the FY27 renewals is positioned correctly under either ruling. The contractor who descoped is exposed under one of them.

What's Actually in the Docket

The comment record on DOJ-CRT-2026-0067 is smaller than you would expect for a rule this visible. As of this week the docket holds comments numbering in the low hundreds — against a Federal Register page that has drawn well over a hundred thousand views. The gap between attention and participation is enormous, and it means each substantive comment carries real weight in a record this thin.

The comments and public statements that do exist sort into two camps.

Opposition from the disability community. The NFB — in addition to suing — has urged its members to flood the docket with opposition, asking individuals to describe the concrete barriers they encounter on government websites and apps. The American Council of the Blind has committed to filing formal opposition. The American Association of People with Disabilities and a broad coalition called the delay unacceptable the day after it published and demanded withdrawal. The substantive arguments: the 2024 rule was the product of more than a decade of deliberation and merely implements an obligation the ADA has imposed since 1990; the good-cause exception was misused; and the delay rewards the entities that procrastinated while imposing the cost on the roughly one in four American adults who report a disability.

Support from government associations. The National League of Cities called the extension a sound decision, citing compliance costs for smaller communities. The National Association of Counties pressed for the extension before it published, citing analyses putting county-side compliance costs as high as a billion dollars nationally, with city-side estimates running higher still. Education groups raised staffing and technology constraints that DOJ cited in the rule's preamble.

Notice who is missing from that list. Advocacy organizations are on the record. Government associations are on the record. The vendors and contractors who actually perform the remediation work — who know what a WCAG 2.1 AA retrofit of a county permit portal actually costs, how long a third-party component vendor takes to ship a fix, and what procurement timelines do to remediation schedules — are almost entirely absent. The June 12 docket is a conversation about your work being held without you.

Why DOJ Specifically Asked for Your Input

Here is the part that makes a contractor comment more than a civic gesture. The IFR's preamble does not just accept comments on the date change. DOJ explicitly invited comment on whether it should publish additional rulemaking to consider regulatory alternatives that would make the 2024 rule less costly for small governments, and on the economic impacts of the rule, particularly on small governments.

That question is the doorway to the substantive NPRM this series has been tracking since May — the possible future rulemaking that could revisit the WCAG version, the conformance level, or the exceptions before April 2027. DOJ's regulatory agenda signaled that intent back in September 2025. When that NPRM is drafted, the agency will draw on the record it is building right now. The comments filed by June 22 are the raw material.

And on the specific question DOJ asked — what compliance actually costs small governments — nobody in the current record is better positioned than the contractors who invoice for it. The advocacy groups can speak to harm. The county associations can speak to budgets in the aggregate. Only the vendor who has scoped, bid, and delivered the work can speak to the line items: what a baseline audit costs for a 200-page municipal site, what share of the remediation burden traces to third-party components the municipality licensed and the contractor cannot patch, what a vendor-paid third-party ACR runs in Virginia, and how the twelve-month cure clocks in state procurement language interact with vendor release cycles. Agencies are legally required to respond to significant comments in the final rule. A comment that puts real numbers and real mechanics into the record is, by definition, significant.

There is a self-interested reading of this too, and it is worth being honest about. If DOJ's future NPRM makes the rule "less costly" by weakening the standard, the procurement-gate market this blog serves gets murkier — but the state laws and contract clauses driving your actual work do not weaken with it, as the indemnification post laid out in detail. The contractor's interest is not in a weaker rule or a stronger one. It is in a rule whose costs and timelines reflect how the work actually gets done — realistic remediation windows, clear treatment of third-party content, and exceptions that don't create traps. That perspective only enters the record if someone who does the work writes it down.

How to File: The Fifteen-Minute Version

The mechanics are simpler than most contractors assume.

Go to regulations.gov and search for docket DOJ-CRT-2026-0067. The commentable document is the Interim Final Rule itself (document DOJ-CRT-2026-0067-0001). Click the Comment button. You can type directly into the form or attach a file — a one-to-three-page PDF on your letterhead reads as more substantive than a paragraph in the text box, and you can attach supporting material like a redacted cost breakdown. The form lets you file as an individual, as an organization, or anonymously. Anonymous comments are accepted, but if you choose that route, keep identifying details out of the comment body, because everything you submit becomes a permanent public record. The deadline is midnight Eastern Time on June 22.

One mechanical note that changes how you should write: agencies do not count comments like votes. Ten thousand identical form letters register as one comment. One well-reasoned submission with specific facts the agency has not seen registers on its own. Length is not the metric — specificity is.

What a Substantive Contractor Comment Looks Like

A comment that earns a response in the eventual final rule does four things. It identifies who you are and why you have firsthand knowledge. It cites the specific provision or question you are addressing. It supplies concrete facts from your own experience. And it tells the agency what you think it should do.

A working outline:

Paragraph one — standing. Who you are: a small firm or solo practice that builds and maintains digital services for state and local government clients, in which states, at what typical contract sizes. This establishes that what follows is firsthand, not advocacy.

Paragraph two — the provision. Name what you are commenting on: the compliance dates in 28 CFR 35.200(b), and DOJ's request for comment on economic impacts and lower-cost alternatives for small governments.

Paragraphs three through five — the facts only you have. Pick two or three and be concrete. What a WCAG 2.1 AA baseline audit and remediation cycle actually costs for the size of entity you serve, with real ranges. How much of the non-conformance you encounter lives in third-party vendor components — payment widgets, video platforms, GIS embeds — that neither the municipality nor its contractor can remediate directly, and how long those vendors take to ship fixes. How the extension has interacted with state law in practice: that your Colorado, Virginia, Massachusetts, Washington, Minnesota, or California clients gained nothing from it because the state statutes and procurement clauses did not move, and that the divergence between federal and state dates is itself generating confusion and descoping pressure in live contracts. If you have watched a client try to strip accessibility scope from a renewal because of the headline, say so — that is exactly the real-world consequence data the record lacks.

Closing paragraph — the ask. Whatever your actual view is. That the dates should hold but the future NPRM should preserve the WCAG 2.1 AA standard because contractors have already built delivery processes around it. That any small-government cost relief should address third-party vendor content, where the cost burden actually concentrates. That federal-state date divergence imposes its own costs the agency should weigh. The ask does not need to be grand. It needs to be yours.

What to leave out: legal argument about the APA (the lawyers have that covered), restatements of the rule's history, and anything you would not want permanently public under your business's name. And do not let the perfect kill the filed — a focused single page submitted by June 22 beats a comprehensive memo that misses the window.

The Posture for the Next Ten Days

Three dates to put on the calendar. June 22: the DOJ comment window closes; file before then if you are going to file. July 6: the HHS Section 504 window closes — relevant if you serve county health departments, public hospitals, or other HHS-funded clients, and the same comment can be adapted for that docket. And whenever the District of Maryland rules in NFB v. DOJ: that decision either confirms the 2027/2028 runway or erases it, and this series will cover it when it lands.

In the meantime, nothing about the operational guidance changes. The extension was never a pause — the conversation script from May 4 is as current today as it was then, and the lawsuit only sharpens it. The contractor who files a comment this week adds one more thing: a documented, on-the-record professional position on the regulation that governs their market. When a procurement officer or a municipal attorney asks whether you are tracking the federal landscape, "we filed in the rulemaking docket" is a better answer than any marketing page.

Monday's post turns to the other half of the Title II rule that almost nobody is preparing for: mobile apps — the WCAG2ICT mapping, the testing stack, and why the Service Oklahoma settlement is the enforcement precedent every contractor with an app in their portfolio should read.

Ten days. One page. File it.

---

This post is for informational purposes only and does not constitute legal advice. Consult with qualified legal counsel for guidance specific to your situation.