The April 24, 2026 deadline under the DOJ's ADA Title II final rule has come and gone. For many K-12 districts, full WCAG 2.1 AA compliance — across every website, app, and third-party edtech tool — wasn't achieved by yesterday. That's the reality, and it's more common than anyone is publicly admitting.
So: what happens now?
The short answer is that missing the deadline doesn't automatically trigger penalties, lawsuits, or federal investigation. The longer answer is that it creates real legal exposure that grows over time if you don't act — and that the most important thing you can do right now is start documenting what you're doing.
If your district serves a population under 50,000, your compliance deadline is April 26, 2027 — not April 24, 2026. Check your district's population classification before treating this as a missed deadline.
What enforcement actually looks like
The DOJ's ADA enforcement process is complaint-driven, not proactive. There is no federal office conducting regular audits of every school district in America. Enforcement begins when someone files a complaint — typically a parent of a student with a disability, a disability rights organization, or occasionally a staff member.
Once a complaint is filed, the DOJ (or the relevant state civil rights office) investigates. That investigation looks at whether the district is complying with ADA Title II's accessibility requirements — including the new WCAG 2.1 AA standard for digital content. What investigators also look at, and what matters enormously in determining outcomes, is whether the district has made a good-faith effort to comply.
A district that missed the deadline but can show:
- A documented inventory of their edtech tools and digital content
- Risk assessments for each tool (which is exactly what DistrictCheck is for)
- Written vendor outreach requesting VPATs and conformance documentation
- A remediation timeline with specific milestones
- Evidence of staff training on accessibility requirements
…is in a categorically different legal position than a district with no documentation, no awareness of the requirements, and no ongoing effort.
Good faith doesn't eliminate liability, but it is a significant mitigating factor in every ADA enforcement context — and it's within your control to establish starting right now.
The scenarios where real legal risk materializes
Not all non-compliance carries equal risk. The scenarios most likely to trigger complaints and subsequent enforcement action are:
A student with a disability is denied meaningful access to a tool
This is the highest-risk scenario. If a student who uses a screen reader, switch access device, or other assistive technology cannot participate in a required classroom activity because the edtech tool isn't accessible — and the district has no documented alternative — that's a direct, documentable harm. Assessment tools such as Edulastic and Formative, plus daily communication platforms such as ClassDojo, are the most exposed categories here.
A parent raises an accessibility complaint and gets no response
Complaint responsiveness is itself a compliance obligation under ADA Title II. Districts must have a functioning grievance procedure for accessibility complaints. A parent who contacts the district about an inaccessible tool and receives no response, or a denial, is very likely to escalate to the DOJ or a disability rights attorney. Having a documented grievance process — even if your tools aren't fully compliant yet — significantly changes this dynamic.
A tool vendor faces litigation and districts are named as co-respondents
This is less common but worth understanding. If a large-scale accessibility lawsuit targets an edtech vendor, districts that used that tool — particularly those with no record of having requested VPAT documentation — may face secondary exposure. Districts that can show they requested and reviewed vendor compliance documentation are better positioned to demonstrate they exercised appropriate due diligence.
What to do right now: the five-day documentation sprint
If your district doesn't have a structured compliance file, the following five actions will create one quickly. Each can be done by your district's technology director or IT coordinator without outside consultants.
-
1Build your tool inventory today Use DistrictCheck's tool database to look up every edtech tool your district actively uses. Record each tool's risk tier, VPAT status, and WCAG claim in a simple spreadsheet. This inventory is the foundation document for every compliance conversation you'll have going forward — with your board, with the DOJ, with parents. If you don't have it, start it now.
-
2Send vendor outreach emails for every tool without a VPAT For each tool rated Critical or High risk in your inventory — meaning no VPAT or no WCAG conformance claim — send a written email to the vendor requesting a VPAT and a timeline for WCAG 2.1 AA conformance. The date you send this email is the date your good-faith compliance effort is documented. Keep copies of every email and every response (or non-response).
-
3Identify students who need accommodation right now Cross-reference your IEP and 504 plan database with your edtech tool inventory. Which students use assistive technology? Which tools do those students interact with? Are any of those tools Critical or High risk? If yes, the district needs a documented alternative pathway for those students — in writing, in their accommodation files — before any complaint arises.
-
4Confirm your ADA grievance procedure is active ADA Title II requires a functioning grievance procedure for accessibility complaints. Check that your district has a designated ADA coordinator, that the coordinator's contact information is publicly posted on your district website, and that there is a documented process for reviewing and responding to complaints. If this infrastructure is missing, establishing it now takes priority over everything else.
-
5Draft a remediation timeline and get it in writing A remediation timeline doesn't need to promise full compliance by tomorrow. It needs to document your district's plan: which tools will be addressed first, what the criteria are for moving a tool from "non-compliant" to "compliant," and who is responsible for each step. This document should be formally approved by your superintendent or technology director and dated. The date matters.
Every day you don't act increases the gap between where you are and where you need to be. Every day you do act, you're building the documentation record that protects your district. The deadline has passed, but the clock on your good-faith effort hasn't — it starts whenever you start.
What "good faith" documentation looks like in practice
DOJ investigators and plaintiffs' attorneys in ADA cases look for specific evidence of good-faith compliance efforts. Based on DOJ guidance and existing ADA enforcement patterns in education, the following documentation is most protective:
- Dated tool inventory with risk assessments — shows you know what you have and assessed the risk
- Vendor outreach emails with dates, to specific contacts, requesting specific documentation — shows you demanded compliance evidence from vendors
- Vendor responses (or documented non-responses after 30 days) — shows the bottleneck is vendor-side, which is a materially different legal situation than district inaction
- Student accommodation documentation for students with disabilities who use high-risk tools — shows you protected the students most directly at risk
- A remediation timeline with specific milestones, approved by district leadership — shows this is an active, prioritized compliance effort
- Board or leadership communication documenting that compliance status was reported to district leadership — shows institutional awareness and responsibility
The tools that need your attention first
If you're triaging where to focus first, prioritize the tools with the highest risk tier and the widest student exposure. Based on DistrictCheck's database, the tools most commonly deployed in K-12 districts that carry Critical or High risk are ClassDojo, Edulastic, Kahoot, Prodigy, Formative, and Nearpod. Districts should also compare those against lower-risk anchors such as Canvas and Google Classroom to understand what stronger documentation looks like. Any district using these tools without a documented vendor outreach record has the most urgent gap to close.
Check every tool in your district's stack
DistrictCheck's free tool lookup shows risk tier, VPAT status, WCAG claim, and recommended next steps for 47 edtech tools — instantly, no signup required.
Check your tools now →Need a full district audit? Enter your work email and district name, then continue to the live intake form.
A note on smaller districts
If your district serves a population under 50,000, your compliance deadline under ADA Title II is April 26, 2027 — one year from now. You are not late. But the practical advice in this article applies equally to your district: use this window to build a compliance file, complete your tool inventory, and send vendor outreach. Every day of lead time you have over larger districts is an advantage — don't waste it.
The bottom line
The April 24 deadline was real, and its passing does create legal exposure for districts that haven't taken any compliance steps. But the enforcement mechanism is complaint-driven, and the most powerful protection against complaints — and against adverse outcomes if complaints do arise — is a documented record of genuine good-faith effort.
You can't change what happened before April 24. You can change what happens starting today. The districts that move now, document everything, and establish a structured remediation process will be far better positioned than those that treat the missed deadline as a reason to stop.
Start your tool inventory. Send your vendor emails. Date everything.