DOJ’s accessibility delay moved one date and put the budget at risk
The one-year delay of the ADA Title II web rule left the standard, the underlying duty and residents’ experience where they were. Its sharpest effect was on budgets that had used April 2026 to justify the work.
Looking Back revisits one week at a time, from January 2020 to today, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
The week
On April 20, 2026, four days before the first compliance date, the Department of Justice published an interim final rule delaying its 2024 web and mobile accessibility deadlines by one year. The 2024 rule implements Title II of the Americans with Disabilities Act. State and local governments serving populations of 50,000 or more now have until April 26, 2027; smaller entities and special districts have until April 26, 2028. The technical standard, WCAG 2.1 Level AA, was unchanged. The rule took effect immediately, with public comments accepted through June 22, 2026. DOJ also said it was considering separate rulemaking that could revise requirements for K-12 schools. The National Federation of the Blind opposed the delay and called for its reversal.
A deadline postponed four days before it arrives produces two reactions in public agencies. Teams that were behind feel relief. Teams that had done the work wonder whether they should have waited. Both reactions focus on the calendar. The more consequential effect sat in budget documents that had used April 2026 to justify accessibility spending.
We separate the effect of the delay into three parts: what the interim final rule moved, what it left in place, and what it put at risk. The first is narrow and the second is broad. The third is where program directors had the most to lose.
What the rule moved
The rule moved two dates and little else. Under the 2024 rule, state and local governments serving 50,000 people or more had to make their web content and mobile apps conform to WCAG 2.1 Level AA by April 24, 2026. Smaller governments and special districts had until April 26, 2027. Each tier gained a year. For an agency months away from conformance, that lowered the risk of missing the specific regulatory date.
The form of the change also mattered. DOJ used an interim final rule, effective on publication, with comments taken afterward. It said it was considering a separate rulemaking that could revise requirements for K-12 schools. A date set this way can move again, in either direction, through further rulemaking or litigation. Agencies should treat April 2027 as the current date rather than a settled one, and check with counsel as the record develops.
What it left in place
Three things did not move.
The first is the standard. WCAG 2.1 Level AA remained the technical benchmark, along with the rule’s limited exceptions for archived content, preexisting documents and certain content posted by third parties. Nothing about what conformance means changed on April 20, and work done to that standard counts in full.
The second is the underlying duty. Title II has required state and local governments to give people with disabilities equal access to their services, programs and activities since 1990. DOJ has long applied that duty to services delivered online. The 2024 rule made the requirement specific and dated. The delay postponed the dates, not the duty. Complaints and lawsuits alleging inaccessible online services never depended on the new deadlines, and agencies should take counsel’s view on their own exposure.
The third is the residents. A permit application that cannot be completed with a screen reader, a meeting video without captions, or a payment page that traps keyboard users fails the same people on April 27 as on April 23. Those failures push residents to phones and service counters, which cost the agency more to run than a working web form.
Taken together, the work itself was unchanged. What changed was the date on which an outside party could point to a specific rule and say the agency had missed it.
What it put at risk
The most direct effect landed on funding. Many agencies justified accessibility work as compliance with an April 2026 deadline. That argument is strong while the deadline is near. Once the date moves a year out, the same request competes with public safety overtime, aging infrastructure, cybersecurity and shrinking federal grants. Budget offices reasonably ask why a project with a 2027 date needs full funding now.
Three kinds of spending are most exposed. Contracted remediation, where a vendor was retained to fix sites and documents by a date, can be cut back or stretched out. Positions created for the project, such as a digital accessibility coordinator, can be left vacant. Platform upgrades bundled into vendor renewals can be deferred to the next cycle. Each deferral looks sensible on its own. Together they can leave an agency where it stood in early 2026, with a year less to finish.
The defense is to restate the case on grounds the delay did not touch. One is the existing Title II duty and the agency’s own complaint history. Another is service cost, because every transaction that fails online returns as a call or a visit. The strongest is the procurement calendar. Payment portals, permitting systems, court e-filing, scheduling tools and learning platforms are mostly bought, and the agency remains responsible for their accessibility. A contract renewed in 2026 without conformance reports, accessibility requirements and remediation terms can lock a nonconforming platform in place well past April 2027. For bought systems, the renewal is often the only point at which an agency can insist on changes.
That suggests how to spend the year. List the critical transactions, such as paying a bill, applying for a permit, registering for a program or filing a court document. Test each one with assistive technology. Map each to its vendor and contract end date, and fund fixes in that order. Documents follow similar logic. Few agencies can remediate every legacy PDF, but forms that people still use can become accessible web forms, and new documents can be required to conform at publication.
Governance protects whatever is achieved. Accessibility funded as a one-time project regresses as content changes and staff move on. A standing operating budget, an owner with authority across departments and a quarterly report on critical transactions survive changes in the regulatory calendar. They also give the budget office a steady figure to plan around instead of a deadline-driven spike.
For agencies that had already finished, the delay changed little. Their task is maintenance: checks built into publishing and release processes, accessibility terms in every renewal, and training for the staff who post content. Their residents were simply served sooner.
With hindsight
The delay took effect at once, and comments closed on June 22, 2026. In May, the National Federation of the Blind sued the Justice Department and HHS under the Administrative Procedure Act. It argued, among other things, that the agencies should not have extended the deadlines through an interim final rule, and asked the court to vacate it. We have not seen a ruling, so the dates remain open to change through litigation as well as rulemaking. The WCAG 2.1 Level AA standard and the tiered structure of the 2024 rule stayed in place.
The budget risk proved the more practical concern. Many state and local governments set their next budgets during 2026, with the new deadline for larger entities still a year away. Agencies that restated their accessibility case on legal duty, service cost and procurement timing kept their programs moving. Those that had relied on the April 2026 date had to make the argument again with less urgency behind it.