The April 24, 2026 ADA Title II Deadline: What Every K-12 District Must Do Before Time Runs Out

On April 24, 2026, a federal rule takes effect that will change how every K-12 school district in the United States must evaluate, procure, and document its digital tools. The Department of Justice's updated ADA Title II web accessibility rule requires state and local government entities — including public school districts — to ensure their websites, web applications, and digital content conform to WCAG 2.1 Level AA.

If your district uses any of the dozens of edtech platforms that have become standard classroom infrastructure — Google Classroom, Kahoot, ClassDojo, Canvas, IXL, Seesaw — you need to have documented accessibility compliance for each one. The deadline is not a suggestion. It carries real enforcement risk, including DOJ complaints and private lawsuits under Section 504 of the Rehabilitation Act.

What Does ADA Title II Actually Require?

ADA Title II has always required public school districts to provide equal access for students and community members with disabilities. What changed in 2024 is that the DOJ issued a final rule specifying how that requirement applies to digital content — and it named a specific technical standard: WCAG 2.1 Level AA.

That means every web-based tool your district uses in an educational or administrative capacity needs to either:

1. Conform to WCAG 2.1 AA — verified through a current Voluntary Product Accessibility Template (VPAT), or
2. Have a documented accessible alternative that provides equivalent access for students or staff who need it.

The rule applies to content your district controls and content delivered through third-party vendors. You cannot simply point to your SIS provider and say "that's their problem." If a student is using a tool your district purchased, deployed, and requires for class participation, the district has an obligation to verify it's accessible — or document what it's doing to address the gap.

Which Edtech Tools Are Covered?

The short answer: nearly everything. Any web-based tool that students, parents, or staff use as part of your district's educational program or communications falls within scope. That includes:

• Learning management systems like Canvas, Schoology, and Google Classroom
• Assessment tools like Formative, Edulastic, and Kahoot
• Communication platforms like ParentSquare, Remind, and Seesaw
• Instructional tools like Nearpod, Pear Deck, Padlet, and CommonLit
• Math and reading platforms like IXL, Prodigy, Khan Academy, and ReadWorks

The rule does carve out some exceptions — most notably for social media content posted by third parties, and for archived content that is not actively used. But for tools actively deployed in classrooms, those exceptions don't apply.

The Current Compliance Landscape: Most Tools Are Not Ready

Here's the uncomfortable reality: a significant portion of the edtech stack used by the average K-12 district does not have current accessibility documentation. Our review of 47 commonly deployed tools found:

Risk Level	What It Means	Example Tools
Critical	No VPAT, no WCAG claim, student-facing	ClassDojo, Formative, Edulastic
High	No VPAT or vague/aspirational WCAG claim	Kahoot, IXL, Nearpod, Remind, Quizlet
Medium	VPAT exists but dated or partially conformant	Seesaw, BrainPOP, Pear Deck, Newsela
Low	Current VPAT with specific WCAG 2.1 AA claim	Google Classroom, Canvas, Khan Academy, Microsoft Teams

A VPAT (Voluntary Product Accessibility Template) is the standard document vendors use to report how their product conforms — or doesn't conform — to accessibility standards. A missing VPAT doesn't necessarily mean the tool is inaccessible, but it means you have no documented basis for claiming compliance. For a federal accessibility mandate, that documentation gap is itself the liability.

What Districts Must Do Right Now

Step 1: Inventory your tools

Build a complete list of every web-based tool your district uses — not just the big contracts, but the teacher-adopted tools, the free platforms, the ones that "kind of just happened." If students or staff are logging into it, it's in scope. Your IT department's SSO logs are a good starting point.

Step 2: Check the compliance status of each tool

For each tool, you need to know: Does a current VPAT exist? What WCAG conformance level does the vendor claim? Are those claims specific or aspirational? Tools like DistrictCheck let you look up this information instantly for the most common edtech platforms — no vendor outreach required for your initial assessment.

Step 3: Prioritize your outreach

Focus first on student-facing tools with no documentation, particularly those used for graded activities or required participation. Send written vendor outreach requesting a current VPAT and a written WCAG 2.1 AA conformance statement. The date you send that outreach becomes your good-faith compliance record.

Step 4: Document accessible alternatives for high-risk tools

If a tool is high-risk and you can't get adequate documentation before the deadline, document an accessible alternative pathway for students who need it. A student with a visual impairment who relies on a screen reader and cannot use a tool without keyboard accessibility needs a documented accommodation — before they ask for one.

Step 5: Build it into procurement

Going forward, accessibility compliance needs to be a procurement criterion, not an afterthought. Include VPAT requirements in RFPs. Add WCAG conformance verification to renewal checklists. If a vendor can't produce a VPAT, that should affect your purchasing decision.

The LTI Loophole Districts Often Miss

One frequently overlooked issue: if your district uses Canvas or another LMS, the Canvas VPAT covers Canvas — not the third-party tools embedded within it via LTI integrations. If a teacher has connected a Kahoot quiz or a Nearpod lesson inside Canvas, the LTI-embedded tool carries its own accessibility requirements. Canvas's low-risk status doesn't transfer to what's running inside it.

This means districts need to audit not just their primary contracts, but the LTI integrations and embedded tools their teachers have connected — often without IT's direct oversight.

What Happens If You Miss the Deadline?

The DOJ enforces ADA Title II primarily through complaint investigations and litigation. A parent or student with a disability (or their advocate) can file a complaint with the DOJ's Civil Rights Division or sue directly under Section 504. Districts found in violation may face:

• Mandatory corrective action plans
• Court-supervised remediation
• Reputational and community trust damage
• Potential financial costs from litigation and settlement

The districts most at risk are those with documented special education populations where specific students' needs were known but tools were deployed without accessibility review. If a student has an IEP, is using a tool that's a compliance risk, and has reported difficulty accessing it — that's a high-exposure scenario.

Start With a Free Compliance Check

DistrictCheck has catalogued the ADA compliance status of the most commonly deployed edtech tools in K-12 districts — including VPAT availability, WCAG claim specificity, and recommended next steps for each tool. It's free and requires no signup.