The Comment Window Closed Today. Here's the Timeline You're Now Planning Against.

The Window Closes Tonight

At 11:59 p.m. Eastern tonight, the comment period on docket DOJ-CRT-2026-0067 closes. If you filed the one-page submission the June 12 post walked through, good — you are on the record in the rulemaking that governs your market, and "we filed in the docket" is now a true sentence you can say to a procurement officer. If you did not, the window is gone and this post is not going to make you feel bad about it. The more useful thing to do today is shift the question.

For two months the question was should I comment. Starting tomorrow the question is what am I now planning against. The answer is not one thing. It is three separate clocks, running at the same time, each controlled by a different actor, and not one of them has a date you can write on a calendar. That uncertainty is itself the planning problem — and the contractor who understands the shape of it will make better decisions through the back half of 2026 than the one who treats "the deadline moved to 2027" as a settled fact and stops thinking about it.

This post maps the three clocks, lays out the four ways this can resolve, and lands on the posture that holds up under every one of them.

Clock One: The Rulemaking DOJ Controls

Start with what the closing of the comment period actually triggers, because it is less than most people assume.

An interim final rule is already in effect. That is the whole point of the mechanism — DOJ invoked the Administrative Procedure Act's "good cause" exception to skip notice-and-comment before the rule took force, published the April 20 IFR, moved the 28 CFR §35.200(b) compliance dates to April 26, 2027 and April 26, 2028, and opened a comment window after the fact. So the closing of that window tonight does not change the operative dates. The IFR stays in effect, word for word, on the morning of June 23.

What the closing triggers is an obligation, not a deadline. DOJ now has to read the comments and, when it issues a final rule, respond to the significant ones with a reasoned explanation. That is the APA's requirement, and it is the hook the NFB lawsuit is built around. But the APA gives DOJ no fixed clock for doing it. A final rule could follow in a few months or sit for more than a year. Agencies routinely take a year or longer to close out a controversial rulemaking, and a change of the magnitude this one drew — well over a hundred thousand Federal Register page views, organized opposition from the disability community, and support from the government associations — is not one DOJ will close out in a hurry.

Then there is the second move DOJ signaled inside the IFR itself, and it matters more to your market than the date change. DOJ said it may publish additional rulemaking — a notice of proposed rulemaking — to reconsider portions of the 2024 rule and make it less costly for small governments, and it explicitly invited comment on that. That is a separate, slower track from the date extension. If DOJ goes that route, you are looking at a full NPRM with its own comment period, its own analysis, its own multi-month-to-multi-year arc. And the thing it would reconsider is substance: the standard, the exceptions, the scope. That is the track that could actually reshape what "Title II compliance" means for a county permit portal — not the date track everyone is watching.

The honest read of Clock One: the dates hold for now, a final rule is coming on no schedule you can predict, and the more consequential question — whether DOJ weakens the underlying 2024 rule — is a separate process that has not even started. None of it resolves this summer.

Clock Two: The Lawsuit a Judge Controls

The second clock is the one most contractors still have not internalized, and it is the only one that can take the extra year away.

On May 21, 2026, the National Federation of the Blind — represented by Democracy Forward and the Baltimore civil-rights firm Brown, Goldstein & Levy — sued DOJ and HHS in the U.S. District Court for the District of Maryland. The complaint asks the court to declare both interim final rules unlawful under the APA, vacate them entirely, and order the agencies to enforce the original 2024 deadlines. The legal theory is the one that has trailed the IFR since the day it published: DOJ had no valid "good cause" to skip notice-and-comment, the extension was arbitrary and capricious because the agency leaned on cost information that was not actually new and did not seriously weigh the harm of delay to people with disabilities, and the interim-final-rule mechanism itself was unlawful as used here.

Here is what a contractor needs to take from the procedure, because the procedure is the timeline.

An APA challenge like this one is normally decided on the administrative record, which means it usually resolves on cross-motions for summary judgment rather than a trial. Both sides brief the question, the judge rules on the papers, and the loser can appeal to the Fourth Circuit. That arc is measured in months at the fast end and well over a year if it runs its full course through appeal. NFB could also ask for faster relief — a preliminary injunction — but that is a heavier lift and there is no public indication of the schedule as of today. The realistic planning assumption is that this case does not produce a final, settled answer in the summer of 2026, and possibly not in 2026 at all.

But the outcome, whenever it lands, is binary and severe, and that is what makes it a planning factor today rather than a thing to watch passively. If the court upholds the IFR, the 2027/2028 dates hold and nothing about your posture changes. If the court vacates it, the extension disappears and the original dates snap back into place — and the original date for entities serving 50,000 or more people, April 24, 2026, is already in the past. The morning after a vacatur, every municipality that treated the extension as permission to pause is out of compliance with the technical standard on day one, with no runway left to get back into it. That is not a remote hypothetical. It is the precise scenario the May 22 FAQ flagged as a live risk, now upgraded from theory to a filed case with a docket number and serious counsel.

You cannot predict how the case comes out. You can refuse to bet your clients' compliance posture on either branch.

Clock Three: The Section 504 Window Still Open Until July 6

The third clock is the one that is easy to forget because it belongs to a different agency, and it is still ticking for two more weeks.

DOJ's Title II extension had a sibling: HHS issued its own interim final rule extending the Section 504 web-accessibility deadline for recipients of HHS funding, and the NFB lawsuit challenges both in the same complaint. The HHS comment window does not close tonight with DOJ's — it runs until July 6, 2026. For most SLED contractors that is a footnote. For the subset who build or maintain digital services for county health departments, public hospitals, community health centers, or any other HHS-funded program, it is a second, still-open chance to put the same firsthand cost-and-timeline facts on a second record. The comment you wrote for the DOJ docket adapts to the HHS docket with minor edits to the standing paragraph. If that describes any of your clients, July 6 is the date that is still in front of you, not behind you.

And note the asymmetry the reg-watch baseline has flagged from the start: the Section 504 web deadline for HHS-funded entities was not extended on the same generous terms as Title II, so the 504 side of a mixed portfolio may already be operating against a tighter clock than the 2027/2028 dates your municipal clients keep citing. If you serve health-program entities, do not let the Title II headline set the schedule for the 504 work.

The Four-Scenario Planning Matrix

Put the three clocks together and there are four ways the next year or so can resolve. The point of laying them out is not prediction. It is to find the move that survives all four.

Scenario A — the IFR holds. The court upholds the extension, DOJ issues a final rule keeping the 2027/2028 dates, and the NPRM either never comes or leaves the standard intact. This is the "everyone relaxes" branch. Your municipal clients have until April 26, 2027 or 2028 on the federal technical standard. What still binds you anyway: the underlying Title II obligation, every state law, and every contract clause — none of which moved. More on that below.

Scenario B — the IFR is vacated. The District of Maryland sets the extension aside. The original dates snap back; the large-entity date is already in the past. Every client who paused is non-compliant on day one. The contractor who kept working is fine; the one who descoped is exposed and out of runway. This is the branch that punishes anyone who treated the headline as permission to stop.

Scenario C — the dates hold but DOJ weakens the standard. The extension survives, but the signaled NPRM reconsiders the 2024 rule and softens it — looser treatment of third-party content, broader exceptions, a lower bar for small governments. This sounds like relief and is partly a trap: a weaker federal rule does not weaken the state laws and contract clauses driving most of your actual deliverables, so the gap between "what federal law requires" and "what your contract requires" widens, and the contractor who reads only the federal headline misjudges the job.

Scenario D — prolonged limbo. The case grinds through briefing and appeal, the final rule sits unissued, the NPRM is "anticipated" but unpublished, and 2026 ends with all three clocks still running. This is, frankly, the most likely near-term state of the world. It is also the one that rewards a stable operating posture and punishes anyone waiting for certainty before acting, because the certainty does not arrive.

Look down the column. There is exactly one posture that is correct in A, correct in B, correct in C, and correct in D: keep doing the work, keep documenting it, and keep the accessibility scope in the contracts. The extension was always runway, never a pause — and the matrix is just the long-form proof of it.

What Does Not Move on Any of These Clocks

The reason the dominant strategy is so clean is that the things that actually govern your deliverables sit outside all three clocks. None of them is affected by the comment period closing, the lawsuit's outcome, or a future NPRM.

The underlying ADA obligation. Title II has prohibited disability discrimination by state and local governments since 1990. The 2024 rule set a technical standard and a date for digital access; it did not invent the duty. Moving or vacating the date does not touch the baseline obligation, which is why a demand letter can land regardless of what the calendar says — the ground the day-after-the-deadline post covered in full.

The state laws. Virginia's HB2541, and the procurement-accessibility regimes in Illinois, New York, Minnesota, Oregon, Washington, and now Texas, run on their own statutory schedules. Virginia, notably, wrote the original federal dates into state law and requires third-party-evaluated ACRs — so the federal extension bought Virginia contractors nothing. A federal vacatur would not change that, and a federal weakening would not either.

The contract clauses. The indemnification, flow-down, and cure-period language you signed does not have a regulatory off-switch. If your contract warrants WCAG 2.1 AA conformance and flows the obligation down to you, that warranty is enforceable on its own terms no matter what the District of Maryland decides. The clause, not the Federal Register, is what a tender of defense will quote back to you.

The FTC posture and the overlay problem. The accessiBe consent order and the FTC's position that "automated tools make your site compliant" is a deceptive claim are unaffected by any of this. An overlay widget is exactly as much of a liability today as it was in April.

Four things that govern your work, none of them on any of the three clocks. That is why the planning answer is stable even though the regulatory answer is not.

The Operating Checklist for the Uncertain Window

Concrete moves for the months while the three clocks run, none of which require you to predict the outcome:

• Keep remediating on the original schedule. Treat April 2026 as the date that mattered, because under Scenario B it retroactively was. The work you do now is the work that protects you if the extension is vacated.
• Keep the audit defense log current. Dated evidence of ongoing, good-faith remediation is the single most valuable artifact you can hold under every scenario — it answers a demand letter, satisfies a state ACR requirement, and documents the warranty performance your contract demands.
• Hold the accessibility line items in FY27 renewals. When a client tries to strip accessibility scope from a renewal because "the deadline moved," that is the descoping pressure the rulemaking record needed to hear about — and the contract exposure you do not want under Scenario B. The conversation script from May 4 is built for exactly that call and is as current today as it was then.
• File the HHS comment by July 6 if any client is HHS-funded. The window is still open.
• Track the docket and the case. Watch DOJ-CRT-2026-0067 for a final rule or an NPRM, and watch the District of Maryland for movement in NFB v. DOJ. This series will cover both when they land; in the meantime, "we are tracking the rulemaking and the litigation" is a sentence that signals to a procurement officer you are the contractor who reads past the headline.
• Do not forget the mobile half of the portfolio. Every clock in this post runs identically for the apps in your portfolio — the rule, the dates, the lawsuit, and the snap-back risk all reach mobile on the same terms, as Monday's post laid out.

The One-Line Version

The comment window closed tonight, and nothing you can put on a calendar replaced it. DOJ has a final rule to write on no schedule, a judge has an extension to uphold or erase on no schedule, and a second comment window stays open until July 6. The only thing that is certain is that uncertainty is the operating condition for the rest of 2026 — and the contractor who keeps remediating, keeps documenting, and keeps the scope in the contract is correct under every way it resolves. The extension was runway, not a pause. Tonight does not change that. It just removes the last excuse to pretend otherwise.

---

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