Most school districts didn't think of their website as a legal risk. It was a place to post lunch menus, calendars, and news updates, not something that could trigger a Department of Justice complaint. That's changing, and the timeline for it is now set.

In April 2024, the DOJ finalized new rules under Title II of the Americans with Disabilities Act that require state and local government websites and mobile apps to meet WCAG 2.1 Level AA accessibility standards. School districts, as public entities, are covered. In April 2026, the DOJ extended the original compliance dates by a year: districts serving populations of 50,000 or more now have until April 26, 2027, and smaller districts and special district governments have until April 26, 2028. The extension bought time. It didn't change what's required, and the DOJ has said directly that it expects to enforce at the new dates.

Web accessibility law isn't new. Section 508 has applied to federal agencies for years, and Section 504 already requires school districts receiving federal funding to make programs and communications accessible to students and families with disabilities — a separate but related obligation that predates this rule and hasn't gone away. What's new with Title II is that it spells out, in specific technical terms, what "accessible" means for a website: WCAG 2.1 Level AA, a defined and testable standard, rather than a general nondiscrimination principle districts had to interpret on their own. That specificity is exactly why enforcement is expected to pick up. It's much easier to bring a complaint, and much harder to argue you were in compliance, when the standard is written down in detail.

The rule covers more than the district homepage. It applies to every page on the public-facing website, including individual school sites and any subdomains; online forms like enrollment, event registration, volunteer sign-ups, and feedback surveys; PDFs and other documents posted for the public, including board meeting minutes, handbooks, newsletters, and budget reports; and videos and other multimedia, which need captions and, in some cases, audio description.

That last category catches a lot of districts off guard. A PDF newsletter uploaded five years ago, still sitting in an archive folder, is just as much in scope as anything published today. There's no grandfather clause for old content. If it's publicly accessible on the site, it's covered.

The most common violations aren't complicated to describe, just tedious to fix at scale. Images without alt text are the biggest offender — a screen reader either skips the image entirely or reads out a meaningless file name like "IMG_4021.jpg" instead of describing what's actually there. Text and background color combinations with too little contrast make content hard to read for anyone with low vision, and fail an objective, measurable standard under WCAG. PDFs that were scanned as flat images, or exported without proper heading structure, are often completely unreadable to assistive technology even though they look fine visually. And interactive elements — dropdown menus, calendar widgets, embedded forms — frequently can't be operated with a keyboard alone, which locks out anyone who can't use a mouse.

Individually, none of these look like a legal issue. They look like small, easy-to-miss details. Add them up across a district site with a few hundred pages built over a decade by different staff using different tools, and they become the legal issue — a pattern a complaint or an audit can point to directly.

Compliance under Title II isn't just about avoiding a hypothetical DOJ investigation. Complaints can come from a parent who couldn't register a child for an event because the form didn't work with their screen reader, or from an advocacy organization that runs automated scans against public school sites looking for violations. The DOJ's Office for Civil Rights and the Department of Education's Office for Civil Rights both accept and investigate complaints, and private lawsuits under the ADA are common in other public-entity contexts already. None of this requires a district to be a large or high-profile target. Enforcement tends to follow whoever gets a complaint filed against them, not just the biggest districts.

Compliance isn't a single fix — it's auditing the current site to find every instance of these issues, remediating what's broken, and then putting something in place so that new pages, new PDFs, and new forms don't reintroduce the same problems six months later. That last part is where most districts underestimate the effort, because a website is never actually finished. New content goes up every week.

Starting the year before the deadline isn't a strategy. It's a scramble, and scrambles produce incomplete fixes.

The starting point isn't picking a vendor or a tool. It's finding out, concretely, what's on your site right now — how many pages have contrast issues, how many images are missing alt text, how many PDFs in your document library would fail a screen reader test. Most districts are surprised by the number once they actually look, not because anyone was careless, but because a site built over years by many hands accumulates gaps nobody was tracking. Knowing the real scope of the problem is what makes every decision after that easier.