Special districts: yes, the ADA web rule applies to you too

Why you almost certainly haven't heard about this

In April 2024 the U.S. Department of Justice published a final rule under Title II of the Americans with Disabilities Act, setting — for the first time — a specific technical standard for the websites and mobile apps of state and local government. The coverage that followed was written for cities. The webinars were run for city clerks. The vendor emails went to city halls.

But Title II regulates public entities, and a special district is one. The DOJ's compliance guide defines a special district government as "a public entity—other than a county, municipality, township, or independent school district—allowed by state law to provide one function or a limited number of designated functions with enough independence to be a separate government." If that sentence describes the board you report to, this rule is yours.

There are, by the Census Bureau's count in the 2022 Census of Governments, 39,555 special district governments in the United States. Most have no IT department; a great many have no full-time staff at all. Collectively they are the largest group of covered entities least likely to know they are covered.

The deadline: April 26, 2028 — and it isn't about your size

This is the part worth understanding properly, because the reasoning is not what people assume.

The rule sets two compliance dates and sorts entities between them by population — specifically, the population recorded in the 2020 decennial Census. Entities of 50,000 or more got the earlier date; entities under 50,000 got the later one.

Special districts don't have a Census population. A water district is not a place the Census counts people in; it is a legal body providing a service across an area that may cross city and county lines, overlap other districts, and correspond to no Census geography at all. There is no number to look up.

So rather than invent one, the DOJ placed special districts in the later group outright. The Department's guidance states it plainly: special district governments have until April 26, 2028 to comply.

Read the third row carefully, because it cuts both ways. A regional water authority serving 200,000 ratepayers is on the 2028 date if it is legally a special district. A mosquito abatement district with one part-time administrator is on the same 2028 date. Neither the size of your service area nor the size of your office moves you — the legal form decides.

Two useful consequences. You do not need to work out which side of 50,000 you fall on; you aren't on either side of it. And being tiny does not exempt you — population only ever sets the date, and your date is the same as every other district's.

What is actually covered

Everything your district publishes online, and this is broader than "the website." For a typical district it means:

• Your public-facing website, whatever it currently is.
• Your board agendas, packets and minutes — including the ones posted as scanned PDFs.
• Your rate schedules, tariffs and fee tables.
• Your budget and audit documents.
• Your service maps and district boundary maps.
• Your online bill-pay, if you have one.
• Your outage notices and boil-water advisories.
• Your board meeting recordings, which need captions.
• Your permit, hookup, and service-application forms.

The standard is WCAG 2.1 Level AA. In practice that means images carry meaningful text alternatives, everything works with a keyboard alone, text has adequate contrast, forms have properly associated labels, tables are structured so a screen reader can read them, and video is captioned. It is a checklist, not a philosophy, and we've written a plain-language version of it.

Your real problem is the PDFs

Here is where a special district's situation differs sharply from a city's, and where most generic advice will lead you astray.

A city has a large website. A district often has a small website with an enormous pile of documents hanging off it. A five-page water district site with three hundred PDFs behind it is an entirely ordinary shape: twenty years of board minutes, every annual budget since the district was formed, consumer confidence reports, rate studies, engineering reports, scanned notices.

And almost all of them are scans — images of text. To a screen reader, a scanned PDF is a blank page. There is nothing in it to read.

If you have just done the arithmetic in your head and gone pale, stop. The rule anticipated this.

The pre-existing document exception

Documents you posted before your compliance date do not have to be retroactively remediated. The DOJ's compliance guide sets three conditions, all of which must hold: the document must be a conventional electronic document (word processing, presentation, PDF, or spreadsheet); it must have been available before your deadline; and it must be "not currently being used to apply for, access, or participate in your state or local government's services, programs, or activities."

That third condition is the entire ballgame. The 2014 minutes nobody has opened since 2014 are historical, and sit under the exception. But a service-application form from 2019 that ratepayers still download and submit is not a historical artifact — it is a live part of a public program, and it needs to be accessible. So does the current rate schedule, even if the file was uploaded years ago, because people rely on it right now to understand what they owe.

So the question to take to your board is not "how many PDFs do we have?" It is:

Count that number before anyone quotes you for remediation. A vendor pricing per-page against your whole archive is pricing against a scope the rule does not require. We walk through that arithmetic in what it actually costs to fix an inaccessible website.

The part that isn't really about compliance

We'll make this point once and then leave it alone.

For a city, the most-read page is usually a permit schedule or a garbage calendar. For a district, the most important thing you will ever publish is a boil-water advisory, a service outage, a hydrant flushing notice, a fire district update during an evacuation.

That content is urgent by definition. It goes out in a hurry, by whoever is at a keyboard, and often as a hastily scanned image or a photographed sign — which is exactly the format a blind resident's screen reader cannot read at all. Which means the resident who most needs to know the water is unsafe is, structurally, the one least likely to be told.

That is not a compliance abstraction, and it is not a lawsuit risk. It is a failure to do the thing the district exists to do. Districts are unusual among public entities in that their most critical content is also their most urgent — and urgency is precisely when accessibility gets dropped. So fix the system, so that the accessible version is the one that goes out by default, rather than relying on someone remembering under pressure at 11pm.

Practical first steps for a two-person office

Assuming no IT staff, no budget line for this, and no time. In order:

1. Write the date down. April 26, 2028. Put it on a board agenda once, so that it is minuted that the district is aware of the obligation. That is a five-minute action and it materially changes your position.
2. Inventory what you actually have. Not an audit — an inventory. A list of every page and every document you publish, in a spreadsheet. Most districts have never had one. It usually takes a morning and it is the foundation of everything else.
3. Mark the load-bearing documents. Go down the inventory and flag anything a ratepayer uses to do something. Forms. Current rates. The current budget. Anything with a deadline on it. That's your real scope.
4. Fix the emergency path first. Before anything else, make sure an outage or boil-water notice can be published as real text on a real page — not a scanned image, not a PDF, not only a Facebook post. This is the highest-value change available to you and it is often free.
5. Stop making the problem bigger. From today, post agendas and minutes as text-based documents rather than scans. Your scanner has an OCR setting. This costs nothing and it means the pile stops growing.
6. Run a free automated scan, then distrust it. Automated tools catch only the machine-detectable subset of WCAG issues. They will find real problems worth fixing. A clean report is not a compliant website.
7. Ask, honestly, whether the platform can even get there. If your site is built on something whose templates generate inaccessible markup, no amount of careful publishing by your staff will fix it. That's a replacement conversation, not a remediation one.

"But we barely have a website"

Plenty of districts don't have one in any meaningful sense. Yours might be a single page hosted on the county's site, a page on a state association's portal, a template untouched since 2011, or — very commonly — a Facebook page doing the job of a website. Two honest observations for that reader.

The rule does not require you to have a website. It requires that what you do publish online be accessible. If your entire web presence is one county-hosted page, then one accessible page is what compliance looks like for you. That is a genuinely small job, and you should not let anyone tell you otherwise.

But a Facebook page is not a solution to this — or to much else. Pre-existing social media posts are exempt; posts you make after your compliance date are not, and you have little control over the platform's accessibility. More to the point, you cannot post a rate schedule there in a findable way, you don't own the content, and if the account is ever locked out you lose your public record with it. A district whose only channel for a boil-water notice is a social feed has a resilience problem well before it has a compliance problem.

The good news, if you're in this position: you're not remediating anything. No legacy site to unpick, no ten-year archive of broken templates. You're starting clean, and starting clean is much cheaper than starting from a mess.

Where Munikit fits — and where it doesn't

We build municipal and district websites that are built to WCAG 2.1 AA from the templates up, rather than retrofitted toward it. Emergency alerts, meetings with agendas and minutes, bylaws, and forms are built into the product, because for a district those aren't add-ons — they're the whole job. Launch is typically six to eight weeks, it's a one-time cost of $17,500–$27,500 all-in with no annual platform fee, and you own the code outright.

We'd rather be straight with you than sell you something. If your district's entire web presence is one county-hosted page and it's serving your ratepayers fine, a new website is not your compliance answer — fixing that page is, and you don't need us for it. Where we're worth talking to is when you've got a real site that can't get to AA no matter how carefully your staff publish to it, or you're standing up a proper web presence for the first time and would rather it be accessible by construction than accessible by heroic effort.

If you're not sure which of those you are, tell us what you've got and we'll tell you honestly — including when the answer is that you don't need us.

This page is maintained. If the rule changes again, we update it here and change the "last reviewed" date above. It is a guide, not legal advice — for a determination about your district's obligations, talk to your attorney.