It usually starts with one email. A parent who uses a screen reader cannot get through your online registration form. Or a father who is blind cannot read the PDF of the student handbook, because it was scanned as an image. Or a mother tells you she has been trying for two weeks to find the special-education contact page, and every link she tabs to reads as "click here." Nothing about that email is hostile. It is just a family telling a district that the front door is locked.
If you are the person who gets that email — a communications director, a technology director, a special-education administrator, or the superintendent who now owns the problem — you also have a date on the calendar. The Department of Justice's 2024 rule under Title II of the Americans with Disabilities Act sets a hard technical standard for public web content, and the compliance dates are close enough that "we will look at it next budget cycle" is no longer a plan. School website accessibility has moved from best practice to enforceable requirement.
What the Rule Actually Requires
On April 24, 2024, the Department of Justice published a final rule amending its Title II regulations to adopt a specific technical standard for web content and mobile applications: the Web Content Accessibility Guidelines, version 2.1, Level AA. Before this rule, Title II required accessible communication but did not name a measurable benchmark, which left districts arguing about what "accessible enough" meant. That argument is over. WCAG 2.1 AA is now the yardstick, and it is a published, testable standard.
An April 2026 interim final rule extended the original compliance dates by one year, which is where the current deadlines come from. The extension moved the dates; it did not soften the standard, narrow the scope, or pause the Title II obligations that already applied. Districts that read the extension as a reprieve generally lost the only thing it actually gave them, which was time to do the work in an orderly way instead of a panicked one.
In practice, WCAG 2.1 AA means things like: every image carries meaningful alternative text; every video with audio carries accurate captions; color contrast meets a minimum ratio; forms have properly associated labels and clear error messages; headings describe real document structure rather than being big bold text; and every function works by keyboard alone, in a logical order, with a visible focus indicator. If you want a concrete starting list, our post on the five WCAG 2.1 fixes every public website needs covers the failures we find most often.
Your District's Deadline Is Probably the Earlier One
This is the single most common and most expensive misreading of the rule. The two compliance dates are keyed to population, with an additional bucket for "special district governments" — and because school districts are, in ordinary conversation, a kind of special district, a lot of districts have quietly assumed they get the later date. Under this rule, they do not. Department of Justice guidance is explicit that a school district is not a special district government, and it explains how to find the population figure that governs your deadline.
| Your district type | Population figure that governs you |
|---|---|
| City school district | The population of the city |
| County school district | The population of the county |
| Independent school district | The population estimate in the most recent Small Area Income and Poverty Estimates (SAIPE) |
Once you have that number, the date follows: April 26, 2027 at 50,000 or more, April 26, 2028 under 50,000. Note that the figure is the population of the jurisdiction, not your enrollment. A district with four thousand students inside a city of two hundred thousand is on the earlier date. Confirm which one you are on before you build a remediation timeline, because the two dates imply very different budget years — and it is far better to discover this now than to discover it in a complaint response.
"Your Website" Is Much Bigger Than Your Website
Districts scope this work as a website project and then find the scope was never the website. Public digital content reaches the main district site and every school site under it, board meeting portals and agendas, the enrollment and registration flow, the student information system parent portal, the food service and payment platforms, the learning management system, athletics and activity signup tools, mobile apps, and the documents inside all of it. Most of that is software you license rather than software you build.
That does not move the obligation off your desk. There is an exception for content a third party posts independently on your site, but DOJ guidance draws a sharp line: content posted by your contractor or vendor is not covered by that exception. If you have a contract, license, or other arrangement with a company to deliver a service to your families, you remain responsible for whether that service complies. The accessibility conformance report your vendor sends you is a claim, not a certification, and the practical answer is to test the workflows your families actually use — register a fake student with a keyboard and a screen reader and see how far you get.
Not sure how far off your district actually is? We audit district sites, parent portals, and document libraries against WCAG 2.1 AA every week — and our free checklist walks you through the first pass yourself.
The Five Exceptions, and How Districts Misread Them
The rule includes five limited exceptions. Each one has conditions that must all be met, and districts routinely claim them on content that does not qualify.
- Archived web content. Only if it was created before your compliance date, is kept solely for reference, research, or recordkeeping, sits in a designated archive area, and has not been changed since archiving. Old board minutes still linked from your live policy page are not archived.
- Preexisting conventional electronic documents. Word, presentation, PDF, or spreadsheet files that were already posted before your compliance date and are not currently used to apply for, access, or participate in a service. A registration packet or a handbook families still rely on fails that second condition.
- Third-party content posted independently. Not your vendors and contractors, as above.
- Individualized password-protected documents. Word, presentation, PDF, or spreadsheet files about a specific person, property, or account, secured behind a password. An IEP posted to one family's portal can qualify; a district-wide form behind a generic login does not.
- Preexisting social media posts. Posts made before your compliance date. Everything after it is in scope, captions included.
And the exceptions are narrower than they look for one more reason. Even where content is excepted from WCAG 2.1 AA, the Department's guidance is clear that a district still has to meet its "other existing obligations under the ADA" — effective communication, reasonable modification, and an equal opportunity to participate. An excepted document that a parent cannot read is still a request you have to fulfill.
The Villain Is Not the Deadline
The deadline is a date. What actually sinks districts is the shortcut: the accessibility overlay widget bolted onto the homepage, the auto-generated captions on the board meeting stream, the scanned PDF uploaded because it was faster than exporting a tagged one, and the standing assumption that an issue is not an issue until somebody complains.
An overlay does not fix an untagged PDF, an unlabeled form field, or a keyboard trap in your registration flow. It puts a button on top of them. Auto-captions do not meet the accuracy the standard contemplates, and a caption that reverses a word in a nurse's instruction or a bus route change is a communication failure, not a typo.
The other quiet villain is a well-meaning one: capable staff doing this off the corner of their desks. Tagging document structure, writing alt text that conveys meaning rather than filenames, and remediating a decade of handbooks and forms is specialist work. Asking your webmaster to absorb it alongside their existing job is how districts arrive at the deadline with a partial fix and no documentation of effort.
A Simple Three-Step Plan
Districts that finish this do not do anything clever. They do three things in order.
- Confirm your date and inventory what you own. Establish which compliance date governs you using the population rules above. Then catalogue every public-facing property: district and school sites, portals, apps, and the document libraries inside them. Note which platforms are vendor-provided and which contracts are up for renewal, because renewal is your leverage.
- Fix worst-first, on the paths families actually use. Do not start at the top of a crawl report. Start with enrollment and registration, special-education communication, health and safety notices, calendars, and payments — the workflows where being locked out has real consequences. Audit those against WCAG 2.1 AA, remediate the templates so the fix holds for future content, and remediate the documents that are still in active use.
- Build it into how you publish. Train the people who post content, add accessibility language to vendor contracts and RFPs, and put a check in the workflow before anything goes live. Keep a written record of your audits and your remediation schedule; documented, good-faith progress is worth a great deal if someone does file.
Get those three right and the date stops being a threat. A parent who is blind registers their child without calling the office. A grandparent using a screen magnifier reads the handbook. A deaf family follows the board meeting. Get them wrong and you are handling an OCR complaint with an undocumented remediation history — and doing the same work anyway, on someone else's timeline, under counsel.
Why Districts Work With Taika
Language Access Hub, powered by Taika Translations, is a veteran-owned, GSA- and NASPO-contracted provider built for exactly this buyer. We handle ADA and Section 508 compliance work end to end: WCAG 2.1 AA audits, template and document remediation, tagged and accessible PDFs, and human-verified captioning for board meetings and instructional video. Because we are also a certified translation and interpretation provider for school districts, we handle the case most vendors cannot — content that has to be both accessible and in the languages your families speak, where remediation has to be redone per language rather than done once. One vendor, contract vehicles your procurement office already recognizes, and ATA-certified linguists on the language side.