With the April 24, 2026 ADA Title II deadline upon us, most district technology and compliance teams are doing some version of the same math: too many tools, not enough time, and highly uneven accessibility documentation across the edtech stack. The question isn't how to achieve perfect compliance overnight — it's how to prioritize.
This post focuses on the tools that represent the highest combination of risk factors: no VPAT, weak or absent WCAG claims, widespread district adoption, and student-facing use cases that directly implicate the rights of students with disabilities. These are the tools your compliance team should be working on right now.
Risk ratings reflect: absence of a current VPAT, quality of WCAG conformance claims, presence of PII handling, and deployment prevalence in K-12 districts. All information is based on publicly available vendor documentation reviewed in early 2026.
ClassDojo is used by millions of students and parents for classroom communication, behavior tracking, and family engagement — making it one of the most widely deployed edtech platforms in the country. Despite this scale, ClassDojo has no publicly available VPAT and makes no specific WCAG conformance claim on its accessibility page. Its core features — the notification feed, student point system, messaging interface — have no documented accessibility testing record.
The combination of high adoption, no documentation, and PII processing creates a compliance exposure that's difficult to mitigate without direct vendor engagement. ClassDojo is also typically used by younger students (K-5), where disability accommodations are particularly common.
Formative is a live assessment platform used extensively for formative checks and graded activities. The absence of any VPAT or WCAG claim is particularly significant here because assessments are high-stakes: if a student with a visual impairment, motor disability, or cognitive difference cannot access an assessment on Formative, the issue isn't just a technical inconvenience — it's a civil rights concern.
Assessment tools require careful accessibility review of keyboard navigation, screen reader compatibility, timed interactions, and input methods. Without any public documentation, districts have no basis to claim these have been evaluated.
Kahoot rates as high rather than critical primarily because it doesn't process student PII in the same way as many other tools. But its WCAG claim status is a significant red flag: Kahoot explicitly states it is "working toward WCAG 2.1 AA compliance." That wording is not a conformance claim — it's an admission that the tool currently does not meet the standard.
Kahoot's core game format — timed, competitive, rapid-response — creates structural accessibility barriers for students with motor impairments, processing differences, or visual disabilities that go beyond what a WCAG patch can address. If Kahoot is used for any graded or credit-bearing activity, the district needs a documented alternative for students who cannot participate equitably.
IXL is one of the most widely purchased math and ELA practice platforms in K-12 districts — frequently used in both classroom and at-home contexts. Despite its market prevalence, IXL has no publicly available VPAT, and its accessibility statements are vague and non-specific. The math input interface in particular has well-documented barriers: keyboard navigation is inconsistent, and screen reader behavior in the expression editor is unreliable.
Timed practice questions in IXL also present structural concerns for students with processing differences. These are not hypothetical edge cases — they're features at the core of the product used by millions of students daily.
Edulastic is a popular standards-aligned assessment platform used for district benchmark testing, formative checks, and state test preparation. Like Formative, the high-stakes nature of assessments amplifies the accessibility risk: a student who cannot access a benchmark assessment tool has a measurable, documented harm. Edulastic has no VPAT and no WCAG conformance claim.
The exposure is compounded by the IEP/504 dimension: if a student has a documented disability that affects their ability to use a standard digital interface, and they're placed in a district benchmark environment without accessible alternatives, the district has a clear compliance failure — regardless of whether anyone has filed a complaint yet.
The Contrast: What Low-Risk Looks Like
To understand why the tools above represent such significant exposure, it helps to see what adequate documentation actually looks like. Tools like Google Classroom, Canvas, and Khan Academy share a common profile:
Current VPAT (2023–2024), specific WCAG 2.1 AA conformance claim, detailed "Partially Supports" disclosures, regular update cycle tied to product releases, accessible accessibility documentation page.
No VPAT or VPAT not publicly available, no WCAG claim or only aspirational/vague language, no dedicated accessibility documentation page, no response to accessibility inquiries.
The gap isn't subtle. It represents years of investment (or disinvestment) in accessibility engineering, and it's visible in the documentation before you even open the tool.
One More to Watch: Schoology
Schoology deserves a special mention outside the top five. After its acquisition by PowerSchool, Schoology's VPAT status became unclear — the pre-acquisition documentation references a version of the product that may no longer reflect the current codebase. Districts using Schoology need to contact PowerSchool directly (not submit a web form — call) and ask specifically for a current VPAT for the Schoology parent portal and student-facing interface.
PowerSchool's main product suite has accessibility documentation, but it doesn't automatically cover Schoology's inherited codebase post-acquisition. This is a nuanced but important distinction.
The Systemic Issue: Teacher-Adopted Tools
The tools above are all widely known products with formal district contracts. But many districts have a deeper problem: teacher-adopted tools that live outside the procurement process entirely. A teacher who discovered Padlet, Quizlet, or Book Creator on a blog post and started using it for class may never have triggered an IT review or a contract review.
These tools often handle student data, require student accounts, and are used for graded work — all of which put them squarely within ADA Title II scope. Districts need a process for surfacing these tools, not just auditing the formal contract list.
Compare the individual database entries for ClassDojo, Formative, Kahoot, IXL, and Edulastic for their current VPAT status, WCAG claim type, and recommended district action.
Pull your SSO or identity provider logs to see every web application your students and staff have authenticated into in the past 6 months. That list is your actual edtech stack — often 40-60% larger than what the technology department thinks it is.
Start With the Highest-Risk Tools First
Perfect compliance across every tool by April 24 isn't realistic for most districts. What is realistic — and what matters most for your legal posture — is demonstrating that you identified the highest-risk tools, took documented action on them, and built a plan for the rest. That's the definition of good-faith compliance, and it's defensible.
Check Every Tool in Your District's Stack
DistrictCheck covers 47 common edtech platforms with instant VPAT status, WCAG claim type, and recommended next steps. Free, no signup.
Run a Free Compliance Check →Need a full district audit? Enter your work email and district name, then continue to the live intake form.