Why K-12 Accessibility Is More Complex Than a City Website
A city hall website either works with a screen reader or it doesn't. If it doesn't, a resident with a disability is inconvenienced and you may receive a complaint. That's serious — but it's bounded. A school district website is different in kind, not just degree.
Your website touches students who have IEPs and 504 plans, parents who depend on screen readers or switch access to navigate parent portals, teachers who upload inaccessible PDFs because nobody told them not to, and community members who want to watch the board meeting that determined whether your special education budget got cut. The stakes are educational equity for children with disabilities, and that is categorically different from a parking permit page that's missing an alt attribute.
No other class of public entity faces the simultaneous overlay of ADA Title II, Section 504, IDEA, and Section 508. Each law has its own enforcement agency, its own complaint process, and its own remediation timeline. A single inaccessible IEP document can trigger complaints under three of those laws at once.
Most city IT directors have one compliance reference point: the DOJ's 2024 final rule under ADA Title II. A district web manager needs four. And unlike a city, you also have a multi-site problem — the district site, plus a website for every school, plus the parent portal, plus the student information system — often maintained by entirely different people with entirely different levels of accessibility knowledge.
The Four Laws That Apply to School District Websites
Understanding which law applies to which content type is the foundation of any district accessibility program. Here is the honest breakdown that most compliance guides skip.
Applies to all programs, services, and activities of state and local government — which now explicitly includes web content and mobile apps under the 2024 DOJ final rule.
Prohibits discrimination against individuals with disabilities in programs receiving federal financial assistance. Every district that receives federal funding is covered — which is essentially all of them.
Requires accessible communication specifically with parents of students with disabilities. This includes IEP notices, evaluation reports, progress reports, and prior written notice. If a parent who uses a screen reader cannot read their child's IEP, this is an IDEA violation.
Applies to districts that receive federal e-rate funding, Title I technology funds, or other federal ICT grants. It governs what you procure — not just what you build. If you buy a student information system that is inaccessible, you are non-compliant.
Which Law Covers Which Content Type
The Highest-Risk Content Areas for School Districts
When OCR opens an investigation against a district, these are the content categories that appear in the complaint 90% of the time. If you do nothing else this year, audit these eight areas.
If a parent who uses a screen reader cannot access their child's IEP, you have simultaneously violated ADA Title II, Section 504, and IDEA. IEPs exported from special education management systems are frequently untagged PDFs with no reading order. This is the highest-risk document category in your entire digital inventory.
Inaccessible enrollment forms prevent equal access from day one of a student's educational journey. A parent with a visual disability who cannot complete your online enrollment form has been told, effectively, that their child may not belong here. These are frequently PDF forms that cannot be completed with a keyboard, or web forms missing labels.
This is, without exaggeration, the most commonly cited document in K-12 accessibility complaints. Lunch menus are almost always posted as scanned JPEGs, image-only PDFs, or non-tagged documents. They're updated weekly. Nobody thinks to remediate them. And parents with visual disabilities need them just as much as anyone.
Emergency alerts posted on the district website, sent via email, or pushed through a mass notification system must be accessible to parents with visual or hearing disabilities. A parent who can't read a shelter-in-place notice because it was posted as an image is facing a serious safety issue, not just a compliance gap.
Every board meeting video posted to the district website requires accurate captions. Every board agenda posted as a PDF must be a tagged, accessible document. If your board discusses special education funding and a parent with a hearing disability cannot follow the meeting, you have a Section 504 problem and a community trust problem.
PowerSchool, Skyward, Infinite Campus — these are third-party systems, but you own the compliance responsibility. Procuring a platform with an outdated VPAT (or no VPAT at all) is a Section 504 and Section 508 exposure. Parents with disabilities who can't navigate the parent portal to check their child's grades are being denied equal access to a core district service.
Teacher pages are frequently maintained by individual teachers who have no accessibility training. They upload PDF syllabi, embed contact forms from third-party services, and add images without alt text. These pages have high parent traffic and are among the most consistently inaccessible pages on school sites.
Dynamically generated calendar widgets — embedded Google Calendars, third-party event plugins — are almost universally inaccessible to keyboard and screen reader users. They use color alone to communicate event types, have no focus management, and frequently have no accessible alternative.
OCR Complaints Against School Districts: What the Data Shows
The Office for Civil Rights receives more website accessibility complaints against K-12 school districts than against any other category of public entity. The patterns in those complaints are remarkably consistent.
A typical OCR resolution agreement for a district website accessibility complaint includes: a third-party WCAG audit of all web properties within 90 days; a remediation plan with quarterly milestones; designation of a district-level accessibility coordinator; mandatory accessibility training for all staff who publish web content; and annual status reports to OCR for two to three years. The district pays for all of it. The average cost, including audit, remediation, and ongoing reporting, runs $150,000–$400,000 depending on district size.
The three most predictive risk factors — legacy website, no designated coordinator, inaccessible third-party portal — are all preventable. OCR does not open investigations against districts that are demonstrably working toward compliance in good faith. The districts that end up in multi-year resolution agreements are the ones that had no program at all.
The IEP Document Accessibility Deep Dive
Most school districts generate IEP documents through a special education management system — Frontline IEP, Illuminate Education, SpEd Forms, Goalbook, or a state-provided platform. The majority of these systems export PDFs that are inaccessible to screen readers.
This is not a hypothetical problem. A parent who is blind and uses JAWS or NVDA should be able to open their child's IEP, navigate by heading to the goals section, read the present levels, and complete any required signature fields — all without sighted assistance. If your SEMS exports a flat, untagged PDF, none of that is possible.
What Makes an IEP PDF Accessible
What to Ask Your SEMS Vendor — Right Now
- Can you provide a current VPAT (Voluntary Product Accessibility Template) for all parent-facing outputs?
- Are exported IEP PDFs tagged for accessibility, and can you demonstrate this in Adobe Acrobat Pro's accessibility checker?
- Do your signature fields meet WCAG 2.1 Level AA requirements and work with JAWS and NVDA?
- If current exports are not accessible, what is your remediation roadmap and timeline?
- Does your contract include accessibility warranties? If not, will you add them?
If your vendor's PDFs are inaccessible and the vendor is unresponsive to remediation requests, document every request in writing. This documentation is your good-faith evidence if OCR comes calling. In the meantime, you are obligated to provide the IEP in an accessible alternative format upon request — whether that means an accessible HTML version, a Word document with proper heading styles, or a verbal walkthrough with a qualified staff member. The format is flexible; the obligation is not.
Video and Multimedia: The Caption Requirement
The rule is simple. The execution is where districts fail.
All prerecorded video posted to or linked from a district or school website must have accurate closed captions. All live video — board meetings, virtual town halls, graduation ceremonies streamed on the district website — must have real-time captions. "Real-time" means human-quality captions, not auto-generated text with a 40% error rate.
YouTube's automatic captions are not a compliant captioning solution under WCAG 2.1 Success Criterion 1.2.2. They typically have 70–85% accuracy, which means every board meeting transcript has 15–30% of its content wrong. Under WCAG, captions must be accurate, synchronized, and complete — including non-speech sounds relevant to meaning. Auto-captions fail on all three criteria without human review and correction.
The Cost-Effective Captioning Workflow for Districts
YouTube generates auto-captions within minutes. This is your starting draft, not your final product.
Export the auto-generated caption file. Open it in YouTube's caption editor or a free tool like Kapwing.
A staff member reviews the transcript, corrects errors (especially proper nouns, student names, policy terminology), and adjusts timing.
Replace the auto-captions with your corrected SRT file. The video is now compliant.
Rev.com charges $1.50/min with 99% accuracy. Verbit and Scribie offer bulk district pricing. For board meetings over 3 hours, outsourcing is usually faster than in-house correction.
Multi-Site Complexity: Managing Accessibility Across Every School
A district with 12 schools may have 12 separate school websites, each maintained by a different office manager, tech-savvy teacher, or PTA volunteer. The district site is managed by IT. The parent portal is managed by a vendor. The student information system is managed by a different vendor. The district YouTube channel is managed by the communications department. No single person has visibility across all of it.
This is the governance failure that produces OCR complaints. It is not malice. It is the absence of a system.
A Governance Model That Actually Works at District Scale
The single highest-leverage action a district can take is designating a Web Accessibility Coordinator before receiving an OCR complaint, not after. This person does not need to be a full-time role — in smaller districts, it can be added to an existing IT or communications position. But the designation needs to be formal, documented, and cross-departmental. Special education, IT, communications, and purchasing all need to route accessibility decisions through this person.
Staff Training That Actually Works for K-12
The classic K-12 accessibility training program is a four-hour session on a PD day in October, delivered by someone from the district's legal department, in a room full of teachers who are simultaneously grading papers on their laptops. Nobody retains anything. Nothing changes. A year later, the district does it again.
Effective accessibility training in schools works completely differently.
Annual Training Cadence
The Technology Audit Every District Should Run This Year
This is not a theoretical audit checklist. This is the exact sequence of steps your district should run before the end of the current fiscal year. Each item is scoped to be completable by a district IT team with no external consultants — though external auditors should be brought in for the full annual review.
Why K-12 Districts Need a Modern Accessible CMS
The current state of K-12 district web infrastructure is not a technology problem. It is a governance problem that technology makes worse. A 2015 WordPress installation maintained by whoever in the office "knows computers" is not a platform — it's a liability. Add seventeen school sites with different themes, a parent portal procured in 2019 that has never been audited, and a YouTube channel that auto-publishes board meeting recordings, and you have a compliance posture that will not survive a single motivated OCR complaint.
An accessible-by-design CMS built for government doesn't just give you better technology. It changes the compliance economics entirely.
Every school site uses the same WCAG-compliant templates. A teacher at School 9 cannot accidentally create an inaccessible hero section because that option doesn't exist in the template. Accessibility is enforced at the design system level, not the training level.
Before a content editor can publish, the CMS checks: does this image have alt text? Is this PDF tagged? Does this video have a caption track? These are not warnings — they are gates. Content that fails the check cannot go live without a documented exception.
Every PDF uploaded to the system is automatically scanned and given a risk score. High-risk PDFs (enrollment forms, IEP notices, handbooks) are flagged for mandatory remediation before linking. The district's highest-traffic inaccessible PDFs are surfaced in the accessibility dashboard.
A school-level teacher can draft content but cannot publish without IT review. Special education documents route through the district accessibility coordinator before going live. The compliance burden shifts from "everyone needs to know everything" to "the right person reviews the right content."
The superintendent and board can see, in a single dashboard, the accessibility posture of every site in the district. When OCR asks for documentation of your compliance program, you have a year's worth of audit history, remediation records, and training completion rates.
VPAT tracking, contract renewal alerts, and third-party integration accessibility reviews are part of the platform — not a separate spreadsheet maintained by someone who might leave. When a vendor's VPAT expires, the system flags it.
The question is not whether your district will eventually address accessibility — the DOJ rule has made that a legal certainty by April 2028 for most districts. The question is whether you address it proactively, with a governance program and a modern CMS that makes compliance sustainable, or reactively, after an OCR complaint that will cost more in legal fees, consultant fees, and staff time than a compliant system ever would have. Districts that are already in OCR resolution agreements will tell you the same thing: they wish they had started two years earlier.