Special Districts and the ADA Web Rule: Yes, It Applies to You

Special district governments are covered public entities under Title II of the Americans with Disabilities Act. Water districts, fire protection districts, transit authorities, library districts, park and recreation districts, irrigation districts, hospital districts, mosquito abatement districts — if you are a unit of local government with a defined purpose, the Department of Justice web accessibility rule applies to you.

This surprises people, and understandably so. The rule gets discussed as though it were about city and county websites. But it reaches every public entity, and special districts got their own treatment in the timeline precisely because they are different.

When is our deadline?

Special districts land on the later of the two compliance dates, regardless of the population served. That was a deliberate choice: a fire district serving 200,000 people may still have no web staff at all, so DOJ did not tie districts to the population tiers that apply to cities and counties.

The current dates are in the ADA Title II deadline post, which is the single place we keep them so they cannot drift across articles.

The technical standard is WCAG 2.1 Level AA. There is no exemption for small districts, volunteer-run districts, or districts whose website is three pages long.

What does it cover for a district like ours?

Everything you publish on the web. For a typical district that means:

• The district website, however modest
• Board agendas, packets, and minutes — usually the largest single category
• Rate schedules, tariffs, and fee tables
• Service applications and permit forms
• Public notices: hearings, boil-water advisories, burn bans, service interruptions, elections
• Annual reports, budgets, and audits
• Any online payment or account portal, including a vendor-hosted one
• Recorded board meetings, if you publish them

Two of those carry outsized risk.

Board materials. Open meetings law already requires you to publish them. The accessibility rule now governs how. A scanned agenda packet is an image file with no text in it — a blind resident attempting to follow a rate increase gets nothing at all from a document you are legally required to make public.

Emergency notices. This is the one worth acting on first regardless of your deadline. A boil-water notice or an evacuation advisory is the highest-consequence content a district publishes, and it is often posted fastest and least carefully — a photographed sign, a scanned letter, an image with the text baked in. If it is an image, it is invisible to a screen reader, and it is invisible at exactly the moment it matters.

We have no web staff. Where do we even start?

The honest answer is that most of your work is documents, not code, and documents are the part you can control without a developer.

A sequence that fits a district’s actual capacity:

1. Confirm your date and write it in the board minutes. It creates a record that the district is aware and acting, and it puts the budget conversation on the calendar.
2. Fix how emergency notices go out. Post the text as text — in the page itself, not as a picture of a letter. This costs nothing and removes your worst exposure.
3. Deal with scanned material. Anything scanned needs its text recovered before it can be made accessible. Identify how much of your archive is scans versus exports; they need different work and different budgets.
4. Change the board packet process. If packets are produced from Word or a template, fixing the template fixes every future packet. Remediating packets one at a time forever does not.
5. Ask your website vendor for a conformance report. Many district sites run on a small number of specialist platforms. If your vendor already conforms, a large part of your problem is solved and you should know that. If they do not, you need to know that too. What is a VPAT explains what to ask for.
6. Work backward through the archive by what the public actually opens, not by date.

Do we have to remediate everything we have ever published?

This is the most common question, and it deserves a careful answer rather than a reassuring one.

The rule covers web content the entity provides. Practically, the sensible approach — and the one that survives scrutiny — is to prioritise by use and by consequence: forms and applications people transact with, notices that affect health and safety, current rate and service information, then the archive. What you must not do is decide the archive is out of scope and stop thinking about it.

If your district genuinely cannot fund the whole estate at once, a documented, dated, prioritised plan is a materially better position than an undocumented hope. It is also what a resident’s complaint or a review will ask to see.

The language question

If your district serves a community that does not read English — an irrigation district with a largely Spanish-speaking ratepayer base, a transit authority in a multilingual metro — you likely already translate some notices.

Be aware that translating a document does not make it accessible, and that a translated document can fail in a way an English one cannot: if the Spanish is not marked as Spanish in the file, a screen reader reads it with English pronunciation rules and the result is unusable. Translated documents and WCAG language of parts covers that specific failure, which is very common in exactly the kind of bilingual notice a district publishes.

Where Taika fits

We remediate documents and web content to WCAG 2.1 AA and Section 508, and we translate — so a district can send a board packet or a rate notice and get back a tagged, correctly structured file, in every language it needs to exist in. For a district without technical staff, that is usually the practical route: hand over the documents, fix the template, and keep the process from refilling the backlog.

Start at document accessibility if the archive is the issue, ADA website accessibility if the site itself is, or an accessibility assessment if you need to know the size of the job before the next board meeting.

Need a number for a budget conversation? Request a quote with a rough count of documents and how many are scans rather than exports — that distinction drives most of the cost, and we can give you a realistic range from it. To bring evidence to the board, run one agenda packet through the PDF accessibility checker and take the result with you.