What Is This Rule?
Everything your district needs to know about the DOJ's April 2024 Title II web accessibility mandate.
In April 2024, the U.S. Department of Justice published a final rule under Title II of the ADA requiring all state and local governments — including public school districts — to ensure their websites and mobile apps are accessible to people with disabilities. The required technical standard is WCAG 2.1 Level AA. This is the legal standard, not optional.
Deadlines extended — April 2026 update: The DOJ issued an Interim Final Rule on April 17, 2026 extending all compliance deadlines by one year. Districts with 50,000+ persons now have until April 26, 2027. Districts under 50,000 now have until April 26, 2028. The new timeline is expected to take effect immediately upon Federal Register publication. Read the GovTech article →
Determining your deadline: School districts use 2022 SAIPE data from the U.S. Census Bureau to determine their compliance deadline — not enrollment numbers, not employee counts, and not the number of students served. Check your district's population at census.gov/programs-surveys/saipe.html. Even with the extension, compliance planning should continue — waiting is strongly inadvisable.
Master Timeline
All 11 action steps mapped across your compliance planning horizon. Adjust dates to align with your district's specific compliance deadline — April 26, 2027 (50,000+) or April 26, 2028 (under 50,000).
Step 1: Learn the web accessibility rule requirements
Owner: ADA Coordinator — Review DOJ guidance at ada.gov before taking any action or remediation steps.
Step 2: Determine your compliance deadline
Owner: Superintendent or designee — Look up your district population in 2022 SAIPE data.
Step 3: Identify compliance team members
Owner: Superintendent or designee — Engage stakeholders across ADA coordination, IT, curriculum, communications, procurement, legal, and special ed.
Step 4: Train staff (all roles)
Owner: HR / ADA Coord / IT Staff — Role-specific training is a prerequisite for lasting compliance.
Step 5: Inventory all web content & apps
Owner: IT Director — Catalog every site, page, PDF, video, LMS, student portal, mobile app, and vendor platform.
Step 6: Review all rule exceptions
Owner: ADA Coord. / Legal — Identify what's exempt vs. what must comply.
Step 7: Classify content: exempt vs. required
Owner: ADA Coord. / IT — Apply the exception framework to your full inventory.
Step 8: Determine what accessibility fixes are needed
Owner: IT / Tech / Curriculum — Conduct a formal accessibility audit using automated tools and manual review.
Step 9: Prioritize & begin remediation
Owner: IT / Curriculum — Fix highest-impact content first: enrollment forms, parent portal, LMS, emergency notifications.
Step 10: Review & update vendor contracts
Owner: Procurement / Legal — Require WCAG 2.1 Level AA warranties; request VPATs; evaluate non-compliant vendors.
Step 11: Create accessibility policies
Owner: ADA Coord. / Legal — Draft written policy, assign ADA Coordinator, establish feedback mechanism, set ongoing testing schedule.
11 Action Steps
A step-by-step framework based directly on DOJ guidance at ada.gov, tailored for school districts.
Learn the web accessibility rule requirements
The district must understand the legal requirements before taking any action or remediation steps. Key resources from the DOJ include:
Determine your compliance deadline
School districts use a specific method to determine their compliance deadline:
- Look up the district's population in the 2022 SAIPE data at the U.S. Census Bureau website.
- If the district population is 50,000 or more: deadline is April 26, 2027.
- If the district population is 0–49,999: deadline is April 26, 2028.
The DOJ issued an Interim Final Rule on April 17, 2026 extending all deadlines by one year. Even with the extension, compliance planning should not slow down. Waiting is strongly inadvisable.
Identify who will have a role in compliance
Accessibility is not solely an IT function. The district must identify and engage stakeholders across multiple departments:
- ADA Coordinator — Lead compliance planning; primary contact for DOJ; manage internal coordination. This is a required role, often delegated within special education or student services.
- IT / Web Team — Technical remediation of websites, apps, and LMS platforms
- Curriculum Staff — Ensure course content (PDFs, videos, documents) meets WCAG 2.1
- Communications — Ensure social media posts and public communications are accessible
- Procurement — Require accessibility warranties in all new vendor contracts
- Legal Counsel — Advise on ADA compliance obligations and risk management
- Special Ed Dept. — Provide disability perspective and user testing feedback
Even if the district outsources web work to a vendor, the district remains legally responsible for the accessibility of its web content. Assign an internal liaison to oversee all vendor accessibility work.
Train your staff
Training is a prerequisite for lasting compliance. Training should be tiered by role:
- All Staff: What is web accessibility? Why does it matter? What is WCAG 2.1?
- Web Developers & IT: Accessible coding, ARIA roles, keyboard navigation, automated testing tools
- Content Authors & Teachers: Writing accessible content; using accessible templates; adding alt text to images
- Designers & Marketing: Color contrast requirements; accessible layout and typography
- Procurement Staff: How to evaluate vendors for accessibility compliance; contract language
Inventory all web content & mobile apps
The district must conduct a full inventory of all digital assets before accessibility testing can begin. Consider:
- District website(s): How many sites? How many pages? What content types? (HTML, PDFs, Word docs, Excel files, videos, images)
- Learning Management System (LMS): Canvas, Schoology, Google Classroom, or similar. All course content must comply — there is NO exception in the law for educational content.
- Student/parent portals: Password-protected portals (registration, grades, lunch accounts, etc.) must comply.
- Mobile apps: Any third-party app the district provides to users must comply with WCAG 2.1.
- Social media: All posts made after the compliance deadline must be accessible. Pre-deadline posts are exempt.
- Vendor-hosted platforms: Platforms accessed via district contractual arrangements must be evaluated and, if necessary, replaced.
Critical LMS Alert: There is NO exception for course content. If a teacher posts a PDF syllabus, a recorded lecture, or a linked article as required reading, it must meet WCAG 2.1 Level AA.
Review all rule exceptions
Not all content must be remediated. The web rule includes five exceptions — review each carefully. See the Exceptions tab for full details.
Classify content: exempt vs. required
Using the exception analysis from Step 6, classify all inventoried content. Flag all content that must comply with WCAG 2.1 Level AA and document your reasoning for anything classified as exempt.
Determine what accessibility fixes are needed
Conduct a formal accessibility audit of all content that must comply. Use a combination of automated tools and manual review — automated tools alone cannot test all accessibility requirements.
- Start with W3C preliminary checks
- Use automated scanning tools (e.g., axe, WAVE, Siteimprove, Deque) to identify obvious failures
- Conduct manual keyboard navigation testing (can users navigate without a mouse?)
- Test with screen readers (NVDA, JAWS, VoiceOver)
- Involve users with disabilities in usability testing where possible
Testing Timeline Warning: Comprehensive accessibility testing across a full district website, LMS, and all document types is time-intensive. Begin no later than 6–9 months before your compliance deadline, or as soon as possible.
Prioritize which content to fix first
Given resource constraints, the district cannot fix everything at once. Use the following prioritization framework to sequence remediation work:
Priority 1 — Highest: Key task-enabling content; frequently accessed; barriers flagged by users with disabilities. Examples: enrollment forms, parent portal, LMS navigation, school lunch payments, emergency notifications.
Priority 2 — High: Site-wide shared components; template-based content. Examples: navigation menus, search, header/footer templates, district-wide PDF templates.
Priority 3 — Medium: New content in development (accessibility-by-design). Examples: new course materials, new policy documents, new website sections.
Priority 4 — Lower: Archivable historical content with low access demand. Examples: old board meeting minutes (consider archiving), historical newsletters.
Review & update vendor contracts
While a district can contract out for WCAG compliance support, the district cannot contract away its ADA responsibilities. Any web content or mobile app provided to students, parents, or staff through a vendor arrangement must meet WCAG 2.1 Level AA. See the Vendors tab for full contract guidance and plug-and-play clause language.
Create accessibility policies
Lasting compliance requires institutional policy — not just one-time fixes. Policies create accountability, set expectations, and demonstrate good-faith compliance efforts. Recommended policy elements include:
- A written Web and Mobile App Accessibility Policy stating the district's commitment to WCAG 2.1 Level AA
- Designation of an ADA Coordinator responsible for web accessibility compliance
- Clear staff responsibilities for creating, reviewing, and posting accessible content
- A process for users to report accessibility barriers and request accessible formats
- A feedback and grievance mechanism with a defined response timeline
- Procurement standards requiring accessibility compliance for all new vendor contracts
- An ongoing accessibility testing and monitoring schedule (at least annual)
- A policy governing new content creation — all new content must meet WCAG 2.1 from the point of creation
Sample Accessibility Statement
Customize this template for your district's homepage. Click the highlighted fields to edit.
Website Accessibility Statement
[District Name] prohibits discrimination based on disability, and no student, employee, applicant for employment, or member of the public may be excluded from participation in, be denied the benefits of, or be subjected to unlawful discrimination under any district program or activity on the basis of disability.
Accordingly, [District Name] is committed to equitable website access, providing persons with disabilities the opportunity to acquire the same information and engage in the same interactions as a person without a disability with respect to its programs, services, and activities communicated or facilitated online.
[District Name] currently strives to comply with the standards of the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG) 2.1.
[District Name] wants to hear from you. If you are unable to access content on any [District Name] websites, have questions about the accessibility of content, and/or would like to report barriers to accessing our websites, need information in another format, or have any suggestions, please email [AccessibilityCoordinator@district.edu] or call [Phone Number]. Staff strives to respond within five working days.
Rule Exceptions
Not all content must be remediated. The rule includes five exceptions — but each has strict conditions.
Critical: Even when an exception applies, the district still has ADA obligations to provide effective communication, reasonable modifications, and equal access for individuals with disabilities upon request.
| Exception | Key Conditions | School District Notes |
|---|---|---|
| Archived Web Content | Must be clearly labeled as an archive; retained only for reference; not updated; must have existed before the compliance deadline. | Old board minutes may qualify if properly archived and labeled. |
| Preexisting Conventional Documents (PDFs, Word, PPT, Excel) | Must have been posted before the compliance deadline. | Does NOT apply to documents used to access current services — enrollment forms and current course materials always must comply. |
| Content Posted by Truly Unaffiliated Third Parties | Applies only to genuinely independent public posts (e.g., a public comment board). | Does NOT apply to vendor content posted on behalf of the district. |
| Individualized Password-Protected Documents | Must be about a specific person, property, or account. | An IEP or individual billing statement may qualify. A general notice to all parents does not qualify. |
| Preexisting Social Media Posts | Posts made before the compliance deadline are exempt. | All new posts after the deadline must comply — add alt text to images, captions to videos. |
Content Classification Guide
Use this reference to classify your inventoried content.
| Content Type | Must Comply? | Notes |
|---|---|---|
| District website HTML pages | ✓ YES | All pages, all forms. |
| Current enrollment/registration forms (PDF) | ✓ YES | No exception applies — currently used for services. |
| LMS course content (all formats) | ✓ YES | No exception for educational content. |
| New social media posts (after compliance deadline) | ✓ YES | Add alt text to images; captions on videos. |
| Old board meeting minutes (pre-deadline PDF, in labeled archive) | ⚠ Possibly Exempt | Archive or preexisting doc exception may apply. |
| Student IEPs / individualized billing statements (password-protected) | ⚠ Likely Exempt | Individualized password-protected doc exception. |
| Pre-deadline social media posts | ✓ Exempt | No action required for pre-deadline posts. |
Vendor Management
While a district can contract out for WCAG compliance support, the district cannot contract away its ADA responsibilities. All vendor-provided web tools must meet WCAG 2.1 Level AA.
Key principle: Even if a vendor built or hosts your website or app, the district remains legally responsible for its accessibility. Assign an internal liaison to oversee all vendor accessibility work. Make sure your procurement and IT staff manage vendor responsibilities.
Top 10 Applications to Audit
1. Public-facing webpage
Your district's main website — highest visibility, highest priority.
2. Student Information System
Grade portals, attendance records, parent access.
3. Learning Management System
Canvas, Schoology, Google Classroom — all course content must comply. No exceptions.
4. Job Board
Employment applications and public-facing job postings.
5. Board Management Portal
Agenda, minutes, and meeting video systems used by the public.
6. Student Registration System
Online enrollment forms — no exception applies to these.
7. Emergency Notifications
Apps and systems used for safety alerts to families and staff.
8. IEP Platforms
Systems used to create and share Individualized Education Programs.
9. Food Services
Lunch account payment platforms and menus.
10. Transportation Services
Bus tracking apps, route information portals.
Contract Best Practices
Steps to take when auditing existing contracts and establishing standards for new ones.
Audit existing contracts
Review all contracts with vendors who provide web-based services (LMS, student information systems, apps, third-party payment processors, communication platforms, etc.).
Request a VPAT
Determine whether current vendor products are WCAG 2.1 compliant — request a Voluntary Product Accessibility Template (VPAT) or Accessibility Conformance Report (ACR).
Evaluate non-compliant vendors
If current vendors are non-compliant, determine the timeline for remediation or begin evaluating alternatives.
Test independently
Don't rely solely on vendor attestations. Test vendor products for accessibility independently and publish results where appropriate.
Plug-and-Play Contract Clauses
These aren't aspirational — they are specific clauses to include in your next vendor contract template. View full procurement guide →
Required contract language — use these clauses in every vendor agreement
Examples of covered vendors: LMS providers (Canvas, Schoology, Blackboard), student information systems, lunch payment platforms, translation services, emergency notification apps, third-party tutoring or assessment platforms, and any mobile app promoted or distributed by the district.
Teacher Accessibility Checklist
Use this checklist to review your digital content before posting. Check each item as you verify it. Resources open in a new tab.
🎨 Color & Visual Design
0/6🖼️ Images & Alt Text
0/5📄 Documents (PDF, Word, PowerPoint)
0/5🎬 Video & Audio
0/5🔗 Links & Navigation
0/5🔊 Screen Reader & Semantic Structure
0/4Key Resources
Official DOJ guidance, W3C standards, and tools for accessibility testing and training.
Featured Resource
Web Accessibility Compliance
Action Plan for School Districts
The complete, editable action plan this site is based on — prepared by EdTech Leaders Alliance pursuant to the DOJ ADA Title II Web Rule (April 2024).
DOJ Official Guidance
Title II Web Rule: First Steps DOJ Fact Sheet (April 2024) Small Entity Compliance Guide Full Rule Text (PDF)WCAG 2.1 Standards
WCAG 2.1 Level AA Guidelines WebAIM WCAG 2.1 Checklist W3C: Introduction to Web Accessibility W3C: How People with Disabilities Use the WebTesting Tools
WebAIM Contrast Checker WAVE Accessibility Evaluator W3C: Full Evaluation Tools List W3C: Preliminary Accessibility ChecksStaff Training
W3C Web Accessibility Tutorials W3C Curricula on Web Accessibility WCAG Teacher Training for K–12 WebAIM Articles & GuidesScreen Reader Resources
Using NVDA (Windows — free) Using VoiceOver (Mac/iOS — built in) Using JAWS (Windows) WebAIM Keyboard ShortcutsThis action plan was prepared based on official DOJ guidance published at ada.gov by the EdTech Leaders Alliance. It does not constitute legal advice. Consult qualified legal counsel for district-specific guidance.