DOJ’s accessibility delay moved one date and put the budget at risk

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. An interim final rule is a regulation that takes effect immediately, with public comments collected afterward rather than before, a shortcut agencies use sparingly.

The rules exist to prevent an everyday failure. A blind resident trying to pay a water bill online uses a screen reader, software that reads the page aloud and lets her move through it with the keyboard. If the payment form’s buttons have no text labels, the screen reader announces only “button, button, button.” She cannot finish, so she calls the utility, waits on hold, or takes the bus to a counter.

The 2024 rule implements Title II of the Americans with Disabilities Act, the part of the 1990 law that covers state and local governments. Under the delay, state and local governments serving populations of 50,000 or more now have until April 26, 2027. Smaller entities and special districts, such as water, transit or school districts, have until April 26, 2028.

The technical standard was unchanged: WCAG 2.1 Level AA. WCAG, the Web Content Accessibility Guidelines, is the internationally used checklist for making websites and apps usable by people with disabilities. Level AA is its middle tier, the one most laws point to. It covers things like text alternatives for images, captions for video, enough color contrast to read text, and pages that work with a keyboard instead of a mouse.

The rule took effect immediately, with public comments accepted through June 22, 2026. DOJ also said it planned future rulemaking on the 2024 rule’s substantive requirements and would consider proposing changes during the extension. The National Federation of the Blind opposed the delay and called for its reversal.

For a city manager or county administrator, the headline read like a reprieve. The fine print was more complicated: the work was unchanged, the duty was unchanged, and only the date had moved, possibly not for the last time.

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. First, a short explanation of what accessibility work actually involves, because at the leadership level it is often mistaken for a website cosmetic.

What WCAG asks of a web page

Digital accessibility means that people with disabilities can use a website, app or electronic document as fully as anyone else. That includes people who are blind or have low vision, people who are deaf or hard of hearing, people who cannot use a mouse because of a motor disability, and people with cognitive disabilities who need clear, predictable pages.

Many of them use assistive technology: tools that sit between the person and the screen. A screen reader turns a page into speech or braille. Screen magnifiers enlarge text. Some people move through sites entirely with a keyboard, a switch or voice commands. These tools work well only if the website is built to cooperate with them, much as a wheelchair works well only if the building has ramps and wide doors.

WCAG 2.1 Level AA translates that idea into testable checks. A few examples show how concrete it is:

• Every meaningful image has a text description a screen reader can announce.
• Videos, including recorded public meetings, have captions.
• Every function works with a keyboard alone, and keyboard users never get “trapped” in one part of a page.
• Text has enough contrast with its background to be read by people with low vision.
• Form fields have labels, and error messages explain what went wrong and how to fix it.

Two features of the work matter at the top of an agency. First, most of it is ordinary craftsmanship: when built in from the start, it adds little cost. Retrofitting an old site, a decade of PDF documents or a bought software platform is where cost concentrates. Second, accessibility is never finished. Every new page, document and software release can break what was fixed, which is why governance matters as much as the initial project.

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 also said it planned future rulemaking on the rule’s substance and would consider proposing changes during the extension. 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.

The arithmetic deserves precision. For the larger tier, the original date of April 24, 2026 became April 26, 2027. For smaller governments and special districts, the original April 26, 2027 became April 26, 2028. Larger governments now face the date that smaller ones originally had, and smaller ones were pushed out a further year.

That uncertainty cuts both ways. An agency that pauses its program hoping the requirements will soften may find the date, or the litigation, moving against it. An agency that keeps going loses nothing if the rules change, because work done to WCAG 2.1 Level AA serves residents regardless.

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.

Four reasons the date was never the main argument

A city manager, county executive or school board chair has reasons to care about this beyond the compliance box. There are four, and none of them depends on a date.

Residents. People with disabilities are not a small, separate group. They include older residents whose eyesight is fading, veterans with injuries, people recovering from a stroke and parents with a temporary injury. A government that moves its services online and does not make them accessible has, in effect, closed a door to part of the public it serves.

Money. Online transactions are usually the cheapest way for a government to serve someone. Every failed attempt that turns into a phone call or a counter visit costs staff time. Agencies that measure where those calls come from often find the same few broken forms behind many of them.

Law. The Title II duty applies now, as it has since 1990. The 2024 rule gave it a specific technical yardstick and dates. Moving the dates did not remove the duty, and residents and advocacy groups can still raise complaints about inaccessible online services.

Reputation. A public body that visibly slows its accessibility work the moment a deadline moves invites an uncomfortable story: that it was only ever doing the work because it had to. One that keeps going can say, credibly, that it serves all residents on the same terms.

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, the work can be cut back or stretched out.
• Positions. Roles created for the project, such as a digital accessibility coordinator, can be left vacant.
• Platform upgrades. Improvements 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.

Making the case again, on firmer ground

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. A resident who cannot finish a form online does not disappear; she becomes a phone call, a letter or a counter visit, each handled by paid staff.

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. Buying a system does not transfer the legal duty to the vendor.

A contract renewed in 2026 without conformance reports, accessibility requirements and remediation terms can lock a nonconforming platform in place well past April 2027. A conformance report is the vendor’s documented statement of how its product measures against the standard, criterion by criterion; asking for one, and checking it, is basic due diligence. For bought systems, the renewal is often the only point at which an agency can insist on changes. Miss it, and the next opportunity may be three or five years away.

Spending the extra year

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.

Suppose a mid-sized city with a population above 50,000 does exactly that. Its digital team identifies eight critical transactions. Testing with a screen reader and keyboard shows that utility payments and recreation registration fail outright, permit applications partly work, and the rest pass with minor issues.

The utility payment portal is bought, and its contract renews in the fall. The recreation system is also bought, with two years left on its contract. The permit forms are the city’s own. That map sets the order. The payment portal goes first, because the renewal is the moment of greatest influence: the city writes conformance, testing and remediation terms into the new contract. The permit forms are fixed in house. For the recreation system, the city opens a conversation with the vendor now and plans for the renewal, while offering residents a supported alternative in the meantime.

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. The city converts its twenty most downloaded forms and sets a rule that new documents are checked before posting. Its old council minutes, rarely opened, wait.

The city also starts counting. It asks its contact center to tag calls from residents who could not complete a task online, and to note which task. Within a couple of months, the tags confirm what testing suggested: a large share of those calls concern utility payments. That gives the budget office a figure it understands, the staff time spent handling calls that a working form would have prevented, and it gives the accessibility program an argument that will still hold if the federal date moves again.

By the end of the year, the city has not finished. But its most used services work, its contracts no longer lock in failures, and it can show its council, and if necessary a court, a plan that is being carried out.

Keeping the fixes fixed

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.

Good governance also means knowing, at any moment, where things stand. A one-page quarterly report can do it: each critical transaction, whether it passed its latest test with assistive technology, the vendor and contract date if it is bought, and the number of related complaints and calls. A council or board can read that in two minutes and see whether the program is moving. It turns accessibility from a technical topic into a service performance measure, which is where it belongs.

Ownership matters as much as reporting. Accessibility touches web teams, IT, procurement, communications, legal and every department that publishes content. Without one person with authority across all of them, each assumes another is handling it. The owner does not have to do the work; she has to be able to insist that it gets done.

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.

The ways programs stall are predictable. One is relying on automated scanning tools alone; they catch some problems, such as missing image descriptions, but cannot tell whether a form actually makes sense to someone using a screen reader. Another is buying an “overlay,” a widget that promises to fix accessibility with a line of code, instead of fixing the underlying pages. A third is treating every PDF as equally urgent and running out of money before reaching the services people use. A fourth is leaving procurement out of the program, so that bought systems are renewed unchanged. The fifth, after April 20, is pausing everything because the date moved.

Where the deadline risk sits now

• What are our ten most important online transactions, and has each been tested with assistive technology?
• Which of those transactions run on bought systems, when does each contract renew, and do our contracts require conformance reports and remediation terms?
• How many calls and counter visits come from people who could not complete a transaction online?
• Who owns accessibility across departments, and is it funded as an ongoing cost or a one-time project?
• If the federal date moved again tomorrow, in either direction, which parts of our plan would change, and which would we keep doing anyway?

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, the federal law that sets the ground rules for how agencies make regulations. It argued, among other things, that the agencies should not have extended the deadlines through an interim final rule, skipping the usual step of taking comments before the rule takes effect, and asked the court to vacate it, meaning to cancel 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. Agencies are therefore planning against a date that could still move, in either direction.

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.

The episode says something broader about how public organizations justify spending. A regulatory deadline is a convenient argument: clear, external and hard to dispute. It is also fragile, because it belongs to someone else and can move without warning. Arguments grounded in the organization’s own obligations, costs and contracts are slower to build but much harder to knock over.

The practical answer is to fund accessibility the way one funds road maintenance or payroll: as a permanent part of running services, owned by someone with authority, and measured by whether residents can actually complete the transactions that matter. Organizations that did so in 2026 were insulated from the change in dates. Those that did not were left exposed to the next one.