A district rolls out a shiny new learning management system across every school building. Teachers love it. Parents love the portal. Then, three months into the semester, someone discovers a blind student can't complete a single assignment in it — because the vendor's platform was never built to work with a screen reader.
That's not a hypothetical edge case. It's the predictable result of treating accessibility as a homepage problem when the real obligation is much bigger.
The Legal Floor: Section 504, Title II, and WCAG 2.1 AA
If your institution receives federal funding — and virtually every public K-12 school and public college or university does — you're covered by Section 504 of the Rehabilitation Act, which prohibits disability discrimination by recipients of federal financial assistance. Public institutions are also covered by Title II of the ADA.
Both point toward the same technical target: WCAG 2.1 Level AA. This aligns with the DOJ's Title II web accessibility rule, which set WCAG 2.1 AA as the operative standard for state and local government entities — including public schools and universities.
That's the legal floor. Two federal statutes, one shared benchmark, and no ambiguity about what "accessible enough" means anymore.
It's Not Just the Homepage — It's the Whole Educational Program
Here's where most districts and institutions get it wrong: they audit the public-facing website, fix a few contrast issues, and consider themselves done.
But Section 504 and Title II scope isn't limited to what your web team built in-house. It extends to learning management systems, student information portals, gradebooks, and third-party curriculum tools — any digital property that's part of the institution's educational program.
A district doesn't get a pass on a vendor's LMS just because it's licensed software instead of something built internally. If students are required to use it to complete coursework, it's in scope. Full stop.
Think about everything a student touches in a single semester:
- The LMS where assignments are posted and submitted
- The student portal for grades, schedules, and announcements
- Third-party homework and quiz platforms
- Video lecture recordings
- PDFs, slide decks, and scanned readings
- Discussion boards and messaging tools
Every one of those is a potential point of failure — and a potential point of legal exposure.
Course Materials: The Overlooked Surface
Everyone thinks about the website. Almost nobody thinks hard enough about the documents.
PDFs, slide decks, and scanned readings distributed to students need the same real remediation as any other content on your site — tagged headings, proper reading order, alt text on images, none of the "looks fine visually, invisible to a screen reader" shortcuts. (Our accessible PDFs article covers what actual remediation looks like versus a cosmetic pass.)
Video lectures need captions too. That's Guideline 1.2 territory — the WCAG success criteria governing time-based media, which exist specifically so deaf and hard-of-hearing students aren't locked out of lecture content. A video without accurate captions isn't a minor gap; it's a student who can watch the video but can't understand a word of it.
Timed Assessments: A Specific and Easy-to-Miss Trap
Quiz platforms, timed tests, and assessment tools deserve their own callout, because the failure mode here is subtle.
2.2.1 Timing Adjustable (Level A) exists because a strict, non-adjustable time limit on an assessment can directly disadvantage a student who needs more time due to a disability — independent of whether they actually know the material. A student who understands the content perfectly can still fail an exam purely because the platform enforces a rigid countdown with no accommodation path.
This is one of the clearest examples of how a "neutral" platform design decision — the same timer for everyone — becomes a discrimination issue the moment it's applied to students with different needs.
The Stat: WebAIM's annual "WebAIM Million" evaluation of the top 1,000,000 home pages has repeatedly found that around 95-96% have detectable WCAG 2 failures in recent years, with low-contrast text and missing alt text among the most common. If nearly every public-facing site has issues, assume your LMS and vendor tools do too until proven otherwise. (WebAIM: The WebAIM Million)
Higher Ed's Procurement Blind Spot
Colleges and universities have a specific version of this problem: procurement.
When a college licenses a new courseware platform or LMS, that vendor's VPAT (Voluntary Product Accessibility Template) becomes directly relevant to the institution's own Section 504 and Title II obligations — not just a line item buried in a vendor-management file. (See our VPAT article for what a real VPAT should actually tell you.)
Too often, the VPAT gets collected during procurement, filed away, and never revisited. If a vendor's own documentation shows significant accessibility gaps, and the institution licenses the product anyway without a remediation plan, that decision — made months or years before any student ever complains — is exactly the kind of paper trail that turns into a real problem.
Where to Actually Start
You can't fix everything on day one, and trying to boil the ocean is how these projects stall out. Here's the practical order of operations:
Audit the platforms students are contractually required to use to complete coursework first — the LMS, the gradebook, the assessment tools. These carry the highest consequence, because a student who genuinely cannot use them cannot complete required work. That's a fundamentally different risk profile than a formatting issue on the district's public events calendar.
School Website Accessibility: Before vs. After
| Area | Before (Typical State) | After (WCAG 2.1 AA Aligned) |
|---|---|---|
| Public website | Homepage looks fine; internal pages untested | Full site audited, keyboard and screen-reader tested |
| LMS / portal | Assumed "the vendor handles it" | VPAT reviewed, gaps documented, remediation plan in place |
| Course PDFs/slides | Scanned images, no tags, no alt text | Properly tagged, logical reading order, real alt text |
| Video lectures | Auto-captions only, unreviewed | Accurate, human-reviewed captions (Guideline 1.2) |
| Timed assessments | Fixed countdown, no accommodation path | Adjustable timing per 2.2.1, documented process |
| Vendor procurement | VPAT collected, filed, never revisited | VPAT reviewed pre-purchase, tied to contract terms |
Get Ahead of This Instead of Reacting to It
The pattern across K-12 and higher ed is the same one we see everywhere: institutions discover an accessibility gap only after a student, parent, or advocacy group hits a wall and has nowhere else to go but a complaint. CDC data shows roughly 1 in 4 U.S. adults live with some type of disability — meaning your student population, staff, and parent community almost certainly include people directly affected by every gap on this list right now, not hypothetically. (CDC)
You don't need to remediate every PDF in your archive by Friday. You need a clear-eyed audit of the platforms that matter most — the LMS, the portal, the assessment tools — mapped against real WCAG 2.1 AA success criteria, with a prioritized plan instead of a vague sense of dread.
That's exactly what we do. Get your school or district digital properties audited against WCAG 2.1 AA — starting with the platforms your students can't opt out of using. Start the conversation and find out where you actually stand before a student, a parent, or a demand letter finds out for you.