The ADA Deadline for School and College Websites Just Moved. Don't Treat That as a Reprieve.

A one-year extension, not a change in the rule

In April 2024, the Department of Justice finalized a rule under Title II of the Americans with Disabilities Act that does something school and college IT departments had been able to treat as optional for years: it sets a specific, named technical standard, WCAG 2.1 Level AA, for the websites, apps, and digital services of every state and local government entity. That explicitly includes public K-12 districts and public colleges and universities.

The original compliance dates were tiered by population: entities serving 50,000 or more people had until April 24, 2026; smaller entities and special districts had until April 26, 2027. In April 2026, DOJ issued an interim final rule pushing both dates back a year, to April 26, 2027 and April 26, 2028 respectively, citing staffing, budget constraints, and the technical difficulty of remediating large content sets.

That extension is worth exactly what it sounds like: more runway, not less obligation. The rule itself didn't change. WCAG 2.1 AA is still the standard. The content that has to meet it, your enrollment forms, your course catalog, your parent portal, your PDFs, hasn't gotten any smaller while you waited.

Who's actually covered, and who just thinks they aren't

The 2024 rule applies to state and local government entities, which means public school districts and public higher-ed institutions are squarely inside it. If you're a public institution, this isn't a "best practice" conversation anymore. It's a federal compliance date with your population tier attached to it.

Private schools and colleges aren't covered by this specific rule; Title II only reaches government entities. But that's a narrower shield than it sounds like. Private institutions still fall under ADA Title III, and in the absence of a DOJ web rule written specifically for Title III, courts and plaintiffs' attorneys have converged on WCAG as the de facto standard anyway, through sheer volume of litigation. "The DOJ rule doesn't technically apply to us" is not the same as "we have no exposure."

One more detail that gets missed in vendor conversations: the obligation doesn't transfer to whoever built your site. If a public entity's website or portal was built and is maintained by an outside studio, the government entity is still the one on the hook for compliance. That needs to be an explicit, written deliverable in any web contract or RFP, not an assumption baked into "we'll make it look nice."

What the standard actually asks for

WCAG 2.1 AA isn't a vague aspiration. It's a checklist, and most of the line items are concrete engineering work, not design polish:

• Every image carries meaningful alt text, not a filename.
• Every interactive element, menus, modals, date pickers, multi-step forms, works with a keyboard alone, not just a mouse or touchscreen.
• Forms have properly associated labels, so a screen reader can tell a user what field they're in.
• Color contrast meets a minimum ratio, and no information is conveyed by color alone.
• Headings follow a real document structure, so screen reader users can navigate by section instead of scrolling through everything.
• Video has captions; audio has transcripts.
• PDFs are tagged, not scanned images of text. An untagged PDF of a registration packet is invisible to assistive technology no matter how clean it looks on screen.

Notice what's on that list: enrollment forms, registration flows, payment portals, and learning platforms, the transactional paths, not the marketing homepage. That's also where the real litigation risk concentrates, because that's where a failure actually blocks someone from doing something they have a right to do.

What doesn't satisfy it

Accessibility overlay widgets, the scripts that promise one-line compliance by adjusting font size, contrast, and adding a floating toolbar, are marketed hard into this exact anxiety, and they don't satisfy WCAG conformance. They've been specifically called out as inadequate in federal resolution agreements with school districts. An overlay changes how your site is presented to a browser; it doesn't fix an untagged PDF, a keyboard trap in your registration form, or a video with no captions. If a vendor's pitch for "ADA compliance" is a single script tag, that's the pitch to be skeptical of.

What this actually costs to get wrong

Remediation after a complaint is consistently more expensive than building correctly from the start, for a simple reason: a complaint usually arrives after someone was already blocked from registering, enrolling, or paying, which turns a web project into a legal one. Past cases involving school districts have combined compensatory damages, attorneys' fees, and remediation costs that ran well into six figures, on top of the original cost of fixing the site itself. A pre-emptive WCAG audit is a fraction of that, and it's a normal, scoped line item, not a crisis project.

What to actually do now

If you run a public school or college website and you've been treating this as a 2026 problem that quietly became a 2027 or 2028 problem: it's still a problem, just with a later due date. Three concrete steps, in order:

1. Get a WCAG 2.1 AA audit scoped against your actual transactional surfaces, enrollment, registration, payment, and any LMS-adjacent tools, not just your homepage.
2. Treat overlay widgets as a stopgap at best, never as the fix. Budget for the underlying remediation.
3. If you're procuring a new site or portal, put "WCAG 2.1 AA conformance, verified by audit" in the contract as a deliverable with an acceptance test, the same way you'd specify uptime or data ownership.

The takeaway

A later deadline is not a smaller obligation. The population tier changes when you have to be compliant; it doesn't change what compliant means. Audit against the transactional parts of your site now, while a fix is still a scoped project instead of a legal one.