ADA Title II for K-12 Districts: Frequently Asked Questions

Title II of the Americans with Disabilities Act prohibits state and local government entities from discriminating against people with disabilities. Public school districts are state and local government entities, which means they have been subject to ADA Title II since the law was enacted in 1990.

What changed in 2024 is that the Department of Justice issued a final rule specifying exactly how Title II applies to digital content. For the first time, there is a named technical standard — WCAG 2.1 Level AA — that districts must meet for their websites, web applications, and web-based tools used in educational programs.

In practical terms: the edtech tools your district deploys in classrooms, the parent communication platforms you use, your student information system portal, your district website — all of these need to be accessible to students, staff, and community members with disabilities.

Yes and no. Districts have had general accessibility obligations under ADA Title II since 1990, and under Section 504 of the Rehabilitation Act since 1973. What's new is the specificity.

Before 2024, there was no federal rule naming a specific technical standard for web content. Districts had general obligations to provide equal access, but no clear benchmark for what "accessible" meant digitally. The 2024 DOJ final rule eliminates that ambiguity by naming WCAG 2.1 AA as the standard and setting compliance deadlines.

This means complaints and enforcement that were previously harder to bring — because there was no bright-line standard — are now more straightforward. The practical enforcement risk increased significantly with the 2024 rule.

Charter schools: Generally yes, if they are publicly funded and operate as a government entity or under a government-issued charter. Most charter schools in the U.S. receive public funding and are subject to ADA Title II. Consult legal counsel for your state's specific charter school classification.

Private schools: Private schools are not subject to ADA Title II, which covers government entities. However, private schools that receive federal funding are subject to Section 504 of the Rehabilitation Act, which has similar — though not identical — accessibility requirements. Private schools with 15 or more employees are also covered by ADA Title III (places of public accommodation), which has different requirements than Title II.

The deadline is based on the population of the jurisdiction your district serves — not the number of students enrolled. The DOJ rule uses census population counts:

• Jurisdictions with 50,000 or more residents: April 24, 2026
• Jurisdictions with fewer than 50,000 residents: April 26, 2027

Note that this is the population of the geographic area the government entity serves, not enrollment. A suburban district in a large metro area may fall under the earlier deadline even if it has a relatively small student population.

Regardless of which deadline applies, districts can be subject to individual complaints at any time. The deadline governs when the DOJ can initiate its own compliance reviews, but it does not prevent parents or advocacy organizations from filing complaints before that date.

The rule requires conformance with WCAG 2.1 AA by the deadline — it does not have an explicit "good faith effort" exemption that allows non-compliant tools to remain in use. However, in practice, enforcement is complaint-driven, and documented good-faith efforts significantly affect how the DOJ and courts assess a district's situation.

Districts that have:

• Inventoried their deployed tools
• Requested VPATs from vendors in writing
• Documented accessible alternatives for high-risk tools
• Built accessibility requirements into procurement

…are in a materially better position than districts that took no action. If a complaint is filed, documented outreach and ongoing remediation efforts are relevant to the outcome.

Any web-based tool that students, staff, or community members use as part of your district's educational program or official communications falls within scope. This includes:

• Learning management systems — Canvas, Schoology, Google Classroom
• Assessment platforms — Edulastic, Formative, Kahoot, Quizlet
• Communication tools — ClassDojo, Remind, ParentSquare, Seesaw
• Instructional platforms — Nearpod, Pear Deck, Padlet
• Reading and math tools — IXL, Khan Academy, Newsela, CommonLit

It also includes your district's main website, parent portal, enrollment systems, and any other digital interface the public uses to interact with the district.

Yes. The rule does not distinguish between tools a district pays for and tools it uses for free. If your district deploys a tool — meaning students or staff are required or expected to use it as part of the educational program — the district has an obligation to ensure that tool is accessible.

You cannot disclaim responsibility by pointing to a vendor. If a student with a visual impairment cannot use a required classroom tool because it doesn't support screen readers, that student has been denied equal access by the district — regardless of who built the software.

In practice, this means districts should: require VPATs from vendors during procurement, include accessibility conformance requirements in contracts and RFPs, and document accessible alternative pathways for tools that have known barriers while remediation is underway.

Yes. An LMS VPAT covers the LMS — it does not transfer to tools embedded within it via LTI integrations or iframes. If a teacher has embedded a Kahoot activity, a Nearpod lesson, or any other third-party tool inside your LMS, that embedded tool carries its own accessibility requirements.

This is a compliance gap that many districts miss. Even if your LMS (Canvas, Schoology, Google Classroom) has strong accessibility documentation, the tools running inside it may not. An audit of LTI integrations and embedded tools is a critical step in a thorough compliance review.

A VPAT (Voluntary Product Accessibility Template) is a standardized document — originally developed by the IT Industry Council — that software vendors use to report how their product conforms to accessibility standards. For web applications, the relevant standard is WCAG 2.1.

A VPAT is your primary documentation that a tool has been evaluated for accessibility. Without a current VPAT, you have no written basis for claiming a tool is accessible. For a federal compliance mandate, that documentation gap is itself a risk — if a complaint is filed, "we didn't check" is not a defensible position.

A VPAT does not guarantee a tool is accessible — it's a self-reported document that vendors produce, and the quality varies widely. A vague VPAT that says "supports WCAG 2.1" without specifying conformance level or noting known limitations is much less valuable than a detailed one with specific criterion-level assessments.

Many vendors post their VPATs publicly on their website (often under a "Legal," "Accessibility," or "Trust" page). Check there first. If it's not publicly available:

• Email the vendor's sales contact or customer success manager with a specific written request for their current VPAT or ACR (Accessibility Conformance Report) for WCAG 2.1 Level AA.
• Frame the request in compliance terms — "We are conducting an ADA Title II accessibility review as required under the DOJ 2024 final rule."
• Document the date you sent the request. That date becomes part of your good-faith compliance record even if the vendor is slow to respond.

We've built a set of copy-paste email templates for initial requests, follow-ups, and escalations — see our Vendor VPAT Request Email Template page.

If a vendor cannot produce a VPAT, you have a few options:

• Document your outreach. Keep records of every request you send. This is evidence of good-faith effort.
• Evaluate alternatives. If a vendor has no VPAT and makes no commitment to produce one, that is a risk factor that should affect your procurement and renewal decisions. There are often competing tools with stronger accessibility documentation.
• Document an accessible alternative. If you must continue using the tool while pursuing compliance, document what accessible pathway exists for students who need it — a different tool, a modified assignment, additional accommodations.
• Escalate in writing. For high-risk tools with significant student adoption, consider sending a formal letter from your district's legal counsel or superintendent making the request and noting the compliance deadline.

A vendor that has never been asked for a VPAT may simply not have prioritized it. A formal written request from a district sometimes prompts movement.

WCAG (Web Content Accessibility Guidelines) is a set of technical standards published by the World Wide Web Consortium (W3C). Version 2.1 Level AA is the tier required by the DOJ rule. It is organized around four core principles:

• Perceivable: Content must be presentable in ways users can perceive — including text alternatives for images, captions for video, and sufficient color contrast.
• Operable: Interface components must be usable with a keyboard alone, not just a mouse. No content should cause seizures. Users must have enough time to complete tasks.
• Understandable: Text and functionality must be readable and predictable. Error messages must be clear and helpful.
• Robust: Content must work reliably with current and future assistive technologies — including screen readers used by students with visual impairments.

Key Level AA requirements that edtech tools frequently fail: color contrast ratio of at least 4.5:1 for normal text, full keyboard navigability, no keyboard trap, captions for pre-recorded audio/video, and meaningful sequence (content order makes sense when CSS is removed).

The DOJ final rule specifies WCAG 2.1 Level AA. WCAG 2.2 was published in 2023 and adds additional criteria, but it is not currently required by the DOJ rule. WCAG 2.2 is backwards compatible with 2.1 — a product conforming to WCAG 2.2 AA also conforms to 2.1 AA.

Some vendors are moving to WCAG 2.2 voluntarily or in anticipation of future regulatory updates. For current ADA Title II compliance purposes, WCAG 2.1 AA is the standard.

ADA Title II enforcement occurs primarily through two channels:

• DOJ complaint investigations: Any individual can file a complaint with the DOJ's Civil Rights Division. The DOJ investigates and, if it finds a violation, attempts to negotiate a resolution. If negotiations fail, the DOJ can file suit.
• Private litigation: Individuals can also sue directly under Title II in federal court. Section 504 of the Rehabilitation Act provides a parallel cause of action for recipients of federal funding (which includes virtually all public school districts).

Districts found in violation typically face corrective action plans — structured remediation timelines supervised by the court or DOJ. Financial penalties are less common in school cases but remain possible through litigation costs and settlements.

The most likely complainants are parents of students with disabilities, disability rights advocacy organizations, and Section 504 coordinators who identify systemic issues.

Enforcement risk is higher when specific harm to identifiable students can be documented. The highest-risk scenarios involve:

• Students with IEPs or 504 plans who are required to use tools that lack accessibility documentation
• Students or families who have previously complained about a specific tool's accessibility and received no response
• Districts with significant special education populations where tool deployment happened without any accessibility review
• Graded assessments administered through platforms with known accessibility barriers

Large districts are more likely to face DOJ-initiated compliance reviews (the 2026 deadline tier covers jurisdictions over 50,000 residents). Smaller districts are more often subject to complaint-driven enforcement. Both are real risks.

Yes. The DOJ rule includes several exceptions, but they are narrower than many districts assume:

• Archived web content: Web content that is maintained solely for reference or as a historical record, is not currently used, and is not modified after the applicable compliance date is exempt.
• Preexisting conventional electronic documents: Word documents, PDFs, PowerPoint files, and spreadsheets that were posted before the compliance date are exempt unless they are currently used as the primary means of accessing required information, or unless they are about a current program, service, or activity.
• Third-party content posted by a non-governmental entity: Content posted by a private individual to a district platform (e.g., a community member's comment on a district social media page) is not the district's responsibility.
• Undue burden: If conformance would impose an undue financial or administrative burden, the district may qualify for an exception — but must still provide an accessible alternative that delivers the same information or service.
• Fundamental alteration: If conformance would fundamentally alter the nature of the service or program.

None of these exceptions apply to current, actively-used edtech tools deployed in classrooms. The exceptions are for legacy or passive content, not for active instructional platforms.

Accessibility should be a procurement criterion, not an afterthought. Practical steps districts are taking:

• Add VPAT requirements to RFPs and contracts. Require vendors to provide a current VPAT as a condition of the award. Include contract language requiring vendors to notify the district of material changes to their accessibility conformance.
• Set a WCAG 2.1 AA conformance requirement. Specify in RFPs that you require documented WCAG 2.1 Level AA conformance, not just "we support accessibility."
• Build renewal checkpoints. Add VPAT verification to your renewal and re-procurement process. A tool that had a VPAT two years ago may not have updated it since.
• Evaluate shadow IT. Teachers often adopt free tools without IT review. Building an approval workflow that includes accessibility screening catches these before they become embedded in classrooms.

A compliance documentation trail is the record that shows your district took good-faith steps toward ADA Title II compliance. The core elements:

• Tool inventory: A dated list of all edtech tools deployed, with notes on how each is used (student-facing, staff-only, graded, optional, etc.)
• Vendor outreach log: Dates and content of VPAT requests sent to each vendor. Keep copies of the emails.
• VPAT/ACR file: Current VPATs collected from vendors, dated. Note when VPATs were last updated.
• Risk assessment: A documented assessment of each tool's compliance risk, using criteria like VPAT recency, WCAG claim specificity, and known accessibility barriers.
• Accessible alternatives: For high-risk tools, documentation of what alternative pathway exists for students who need it.
• Procurement policy updates: Evidence that accessibility requirements have been added to your procurement process going forward.

DistrictCheck's tool pages give you the VPAT status, risk tier, and recommended next steps for 47 common tools — a starting point for your documentation.