School Districts and ADA Title II: What Your Website and Documents Have to Do

A school district is a public entity under Title II of the Americans with Disabilities Act. That means the Department of Justice’s web accessibility rule applies to your district in full — your main site, every school site under it, your parent portal, your mobile app if you have one, and every document you publish for families.

Districts are also the entities most likely to be caught out by the documents rather than the website, because a district publishes far more paper-shaped material than a typical city of the same size.

Does the rule really apply to us?

Yes. Public school districts are covered public entities. So are charter schools operated by a public entity, county offices of education, and intermediate units.

Your compliance date depends on the total population your district serves. The current dates, and which tier you fall into, are in the ADA Title II deadline post — that is the only place we keep them, so it stays correct.

The technical standard is WCAG 2.1 Level AA. There is no exemption for small or rural districts.

What counts as our web content?

More than the district website. Under the rule, it includes anything you make available to the public through the web, which in a district typically means:

• The district site and every school site, including sites maintained by individual schools on different platforms.
• The parent and student portal, including grade and attendance views.
• Enrollment and registration systems, whether you built them or bought them.
• Board meeting materials — agendas, packets, minutes, budget documents.
• Every letter, form and notice you post for families. Immunisation forms, free and reduced-price meal applications, field trip permissions, calendars, handbooks, discipline policies.
• Video you publish — board meetings, announcements, recorded lessons on a public channel.
• Third-party tools you link to, which is where districts have the least control and the most exposure.

The third-party problem deserves a flag. If your registration platform is inaccessible, the fact that a vendor built it does not remove your obligation to the family trying to use it. It moves the conversation to your contract with that vendor — which is exactly why accessibility language belongs in your procurement, not just in your remediation plan.

Why do documents hit districts harder?

Because a district’s relationship with families runs on documents, and almost all of them started life in Word or a scanner.

The two patterns that cause the most trouble:

Scanned paper. A scanned form is an image. A screen reader finds nothing in it at all — not badly structured text, no text. Any form your office scanned and posted is currently unusable to a blind parent, and no amount of remediation software fixes it without the text being recovered first.

Exported Word. Export to PDF without setting up headings, table headers, and alt text, and you get an untagged file with no reading order. Our guide to making Word, PowerPoint and Excel files accessible covers fixing this at the source, which is much cheaper than fixing it afterwards.

The bit that catches districts that do translation well

Districts are often ahead of other public entities on language access. Many already translate enrollment packets, handbooks, and family notices into Spanish and whatever else their community speaks, because Title VI obligations and simple practicality demand it.

Here is the trap: a translated document is not exempt from accessibility, and translating an inaccessible document produces a second inaccessible document.

Worse, translated documents fail in a way monolingual ones cannot. WCAG requires the language of a passage to be declared programmatically. If your Spanish enrollment form is not marked as Spanish, a screen reader pronounces Spanish words using English rules, and the result is not merely accented — it is unintelligible. A Spanish-speaking blind parent gets nothing from a document you paid to have translated specifically for them. We wrote that failure up in detail in translated documents and WCAG language of parts.

The same applies to alt text. If the image description inside a Spanish document is still in English, the description is useless to the reader it was written for.

If you are building or refreshing a language access plan alongside this work, how to build a Title VI language access plan is the companion piece — and note that Executive Order 13166 was revoked in 2025, so what actually obliges agencies now has changed even though Title VI itself has not.

What should we do first?

1. Count the documents. Every district that does this is surprised. Include each school’s own site.
2. Separate the scanned from the exported. They need different work, and scanned material takes longer.
3. Prioritise by what families actually have to use. Enrollment, meals, health forms, and anything with a deadline attached come before three-year-old board minutes.
4. Fix the outbound process. Train the staff who publish, and set a rule that nothing gets posted untagged. Otherwise the backlog regenerates.
5. Put accessibility in your vendor contracts, including a conformance report requirement, so the next platform you buy is not a new problem.
6. Handle translation and accessibility as one job. Doing them in sequence means paying twice and still ending up with a file that fails.

Where Taika fits

We remediate documents to WCAG 2.1 AA and Section 508, and we translate — which means a district can send us an English enrollment packet and get back a tagged, correctly-structured English version and a tagged, correctly-language-marked Spanish version, with alt text written in Spanish. One vendor, one pass, both obligations.

For the document estate, start at document accessibility. For the sites themselves, ADA website accessibility. For families and the broader language-access picture, education language access.

Not sure how big your job is? Request a quote with a rough document count and the languages your families read, and we will come back with a sequence and a realistic timeline. If you want a data point before you talk to anyone, run one of your enrollment forms through the PDF accessibility checker — for most districts, that single result starts the conversation internally.