The DOJ's 2024 ADA Title II final rule named WCAG 2.1 AA as the technical standard for web accessibility, set hard compliance deadlines (April 24, 2026 for large districts, April 26, 2027 for smaller ones), and created real enforcement exposure for districts deploying inaccessible edtech tools. The question isn't whether this applies to your district — it does. The question is how to build a defensible compliance record in the shortest time possible. This 30-day roadmap gives you the specific, week-by-week actions that matter most.
Week 1: Inventory and Assessment (Days 1–7)
You can't fix what you don't know exists. The first week is entirely about inventory — building a complete, documented list of every web-based tool your district uses, and getting an initial read on each tool's compliance status.
Day 1–2: Build your tool inventory
- Pull your SSO/identity provider login list — every tool students or staff authenticate to is in scope
- Check your SIS integrations, LMS plugins, and any district-approved app lists
- Ask teachers to self-report any tools they use with students that may not be in your system
- Goal: a spreadsheet with every tool name, vendor, how it's used (student-facing / staff-only / parent-facing), and whether use is required or optional
Day 3–4: Initial compliance screening with DistrictCheck
- For every tool in your inventory, search DistrictCheck for its compliance status
- Record: risk tier, VPAT status, WCAG claim, recommended action
- Flag all Critical and High risk tools — these become your priority list
Day 5–7: Triage and prioritize
- Sort your tool list by risk tier × usage type: Critical + student-facing required = immediate action
- Identify the top 5–10 tools that represent your highest combined risk
- Note any tools where students with IEPs or 504 plans are specifically required to use the tool
Common mistake in Week 1: Under-counting your tools. Teacher-adopted free tools — things that were never formally approved but are actively used in classrooms — are in scope. Don't stop at your IT-sanctioned list.
Week 2: Vendor Outreach (Days 8–14)
With your inventory prioritized, Week 2 is about creating a documented paper trail with vendors. The date you send your first VPAT request is the date your good-faith compliance record begins — even if the vendor is slow to respond.
Day 8–9: Check for publicly available VPATs
- For each Critical and High risk tool, search "
[tool name] VPAT" and "[tool name] accessibility conformance report" - Check vendor websites under Legal, Accessibility, and Trust pages
- Download and date-stamp every VPAT you find
- Note: a 2019 VPAT for a product that has had major releases since then may not reflect current conformance
Day 10–14: Send VPAT requests to vendors with no documentation
- Use the DistrictCheck Vendor VPAT Request Email Template (initial request)
- Send from your district email — not a personal account
- CC your IT director or Section 504 coordinator
- Log every email sent with the date — this becomes your compliance documentation
- For Critical-risk student-facing tools: consider immediately sending the formal escalation version (Template 3) rather than starting with Template 1
Keep a vendor outreach log: A simple spreadsheet with Tool Name, Contact Email, Date Template 1 Sent, Date Template 2 Sent, Response Received (Y/N), Date, VPAT Received (Y/N). This is your primary compliance evidence document.
Week 3: Documentation and Accessible Alternatives (Days 15–21)
While vendor responses come in, Week 3 focuses on building the compliance documentation record that protects your district even while remediation is underway — and on ensuring no student is currently being denied access without a documented alternative.
Day 15–17: Build your accessible alternatives documentation
- For every Critical and High risk tool currently required for student use, document:
- Which students might be affected (students with IEPs, 504 plans, or known AT use)
- What accessible alternative exists (a different tool, a modified task format, a teacher-mediated accommodation)
- Who is responsible for implementing the alternative if requested
- This document doesn't have to be elaborate — a spreadsheet or notes document is sufficient
Day 18–19: Review vendor VPAT responses received
- For VPATs received from vendors, review the WCAG 2.1 AA section specifically
- Flag any "Partially Supports" or "Does Not Support" entries in student-facing criteria
- Use the DistrictCheck WCAG 2.1 AA Edtech Checklist to assess which criteria have known gaps
- Note any criteria where partial support affects your specific use case
Day 20–21: IEP and 504 cross-check
- Review active IEPs and 504 plans for students who use assistive technology
- Cross-reference with your tool inventory — any tool required for a student with AT needs and rated Critical or High is highest-priority for immediate accessible alternative documentation
- Notify teachers of any specific accommodations needed for high-risk tool use
Finding a gap isn't failure: It's the start of a documented remediation record. The goal isn't perfect compliance on day one; it's demonstrating that you identified the gaps, are actively pursuing vendor documentation, and have a plan for affected students.
Week 4: Process and Procurement Updates (Days 22–30)
The final week is about converting this one-time exercise into a sustainable compliance program — so you're not starting from scratch every year, and so every tool you purchase going forward arrives with accessibility requirements already built in.
Day 22–24: Update your procurement process
- Add VPAT requirement to your standard vendor questionnaire and RFP template
- Include contract language requiring vendors to provide a current VPAT or ACR addressing WCAG 2.1 AA
- Add an accessibility verification checkpoint to your contract renewal process
- Consider adding a VPAT score to your edtech evaluation rubric
Day 25–27: Build an ongoing monitoring system
- Schedule calendar reminders to re-verify VPAT status for your top 10 tools annually
- Create a shared folder or drive location where all VPATs are stored and dated
- Designate a staff member responsible for maintaining the accessibility documentation file
- Set a reminder to send follow-up VPAT requests to vendors who haven't responded by Week 4
Day 28–30: Brief leadership and document your effort
- Prepare a brief summary for your superintendent and/or school board: what tools were reviewed, what actions were taken, what the current status is
- Confirm that your accessible alternatives documentation is filed with your Section 504 coordinator
- Review your vendor outreach log — send Template 2 (follow-up) to any vendor that hasn't responded
- File your 30-day compliance summary in your district's official compliance records
Don't skip the leadership briefing: A district that can show its leadership was informed and took action has a qualitatively different compliance posture than one where accessibility was handled quietly by IT. If a complaint is ever filed, documented institutional awareness is a significant factor.
After the 30 Days: Ongoing Compliance
Three actions to maintain momentum:
- Monthly: Check DistrictCheck for any status changes on your top 20 tools (vendors do update VPATs)
- Quarterly: Review any new tools adopted by teachers or approved by IT — screen them before they enter the classroom
- Annually: Full re-inventory, VPAT renewal verification, and update of accessible alternatives documentation
Links to Additional Resources
Ready to get started?
Begin your compliance check today by searching your tools in DistrictCheck.
Start Your Compliance CheckNeed a full district audit? Enter your work email and district name, then continue to the live intake form.