The ADA Deadline Moved.
Your Budget Calendar Did Not.

In April, the Department of Justice extended the compliance dates for the ADA Title II web accessibility rule. Smaller public entities now have until April 26, 2028.

For two years before that, accessibility vendors had been warning public agencies about an earlier date. When the date moved, a lot of them went quiet. The reasonable conclusion for a city manager or a county administrator was that this had stopped being urgent.

I want to make the opposite argument, and I want to make it with a calendar rather than a warning.

The federal deadline moved. Your appropriation calendar did not. And public money does not become available continuously. It becomes available in discrete windows, once a year, on a schedule set long before anyone at the Department of Justice picked a date.

Count the windows instead of the months and the extension buys far less than it appears to.

What the Rule Actually Requires

The short version: web content and mobile apps provided by state and local governments have to meet the Web Content Accessibility Guidelines, version 2.1, Level AA.

That covers the main website. It also covers the documents posted on it, the online permit and license forms, the agendas and minutes, the payment portal, the calendar and reservation tools, and anything a vendor posts on your behalf.

Your date depends on the population of the government you belong to, which for most entities comes from the 2020 Census. Departments inside a larger government, a police department or a public library, use the population of the government that runs them. Special districts are on the 2028 date regardless of size. School districts are handled separately and are not classed as special districts: a city school district uses the city's population, a county school district uses the county's.

Count Budget Cycles, Not Months

Here is the part I have not seen anyone lay out plainly.

Twenty months sounds like plenty. But an agency cannot spend money it has not been appropriated, and appropriation happens once a year. So the honest question is not how many months remain. It is how many budget cycles remain, and how many of those leave enough runway afterward to actually do the work.

Scoping, procurement, remediation, and verification on a public sector website is not a four week job on any site I have looked at. Money that lands a month before the deadline is money that arrives too late to matter.

Work it out against your own calendar. Three common patterns:

Most states, and a large share of municipalities, run July to June. If that is you, note what the table says: the fiscal year beginning July 1, 2028 starts after the deadline has already passed. FY2028 is not the comfortable option. It is the last one.

I live in New Hampshire, where most towns still appropriate at an annual meeting in March, so this arithmetic is unusually stark in my own backyard. Two meetings remain before the deadline, and the second one falls about a month before it. That leaves exactly one. But the shape of the problem is the same wherever you are. Whatever your fiscal year, there is a last cycle, and the request for it gets drafted well before the cycle opens.

If you budget biennially, as a number of states and a handful of municipalities do, the arithmetic is harsher rather than easier. Two-year cycles mean fewer windows, not longer ones, and there is a real chance the budget being assembled now is the only one you get.

That is the whole argument. Not that the deadline is close. That the number of remaining opportunities to fund the work is small, and the paperwork for the good one is due sooner than the date suggests.

The Exception Everyone Reads Wrong

The rule contains a handful of exceptions. The one that gets misread most often is the exception for documents that were already on the site.

Read quickly, it sounds like every PDF posted before the compliance date is exempt. That is not what it says.

A word processing, presentation, PDF, or spreadsheet file already published before the compliance date generally does not have to meet the standard. But the exception falls away for any document currently being used to apply for, access, or participate in a service.

Think about what that covers on a typical government website. The building permit application. The business license renewal. The public records request form. The utility billing enrollment. The school registration packet. Most of those files were posted years ago, which is exactly why people assume they are safe. They are also the documents residents actually use, which is precisely what removes them from the exception.

There is a second misread worth naming. Content posted by a third party is excepted, but content posted by your own web vendor is not third-party content. If a company builds and updates your site, what that company posts is yours.

The Rule Is Less Absolute
Than Its Reputation

It is worth saying clearly, because the marketing around this subject has been unhelpful, that the rule is not a purity test.

It includes a provision recognizing that a shortfall so small it would not actually change anyone's access is not a violation. The Department's own illustration is a text contrast ratio of 4.45 to 1 where the standard asks for 4.5 to 1.

What the rule has no tolerance for is having done nothing.

So the practical goal is not a flawless website. It is a documented, funded, good-faith effort that is genuinely underway and can be shown to be underway.

A Budget Request Needs a Number

Here is the real obstacle for most agencies, and it has nothing to do with the law.

No finance director, council, or budget committee can appropriate money for "accessibility." They need a scoped figure attached to a defined piece of work. Without one, the item does not survive the first round of cuts, and the conversation rolls into next year, which is a year you may not have.

That is what an assessment produces. Not a fix. A number. A written account of what exists, what conforms, what does not, how much of it there is, and what remediation would actually involve. It is a small piece of work, it is defensible in front of whoever holds the purse, and it turns an abstract federal obligation into a line item somebody can vote on.

It also produces the record. If a complaint ever arrives, the distance between an agency holding an assessment, a plan, and an appropriation, and an agency holding none of those, is not a small distance.

Where I Stand on This

I want to be precise about what I am and am not saying.

I am not an attorney and none of this is legal advice. WCAG is a conformance standard, not a legal safe harbor, and no vendor can sell you legal protection. What careful accessibility work does is reduce risk and, more to the point, make your services usable by residents who currently cannot use them. The second reason is the better one, and it is the one I would lead with in front of a governing body.

I also want to be clear that I am not manufacturing urgency. The deadline genuinely did move, and anyone telling you otherwise is wrong. The urgency here is not federal. It comes from your own appropriation calendar, and you know that calendar better than any vendor does.

---

Wilson Digital Strategy is based in New Hampshire and works with clients across the country. We build and maintain accessible websites and run WCAG 2.1 AA assessments for small businesses, nonprofits, and public agencies. If your finance office or governing body needs a scoped figure for the next budget cycle, I am glad to look at what you have and tell you plainly what is there. The current compliance dates and the full text of the rule are published at ADA.gov (opens in a new tab), and I would encourage you to read it yourself rather than take any vendor's summary at face value, including this one.