Accessibility for schools, universities and EdTech — for the LMS, the lecture and the assessment.

Section 504 of the Rehabilitation Act prohibits disability discrimination by any institution that receives federal funding — which, in practice, captures nearly every K-12 district, public university, and most private colleges. The statute itself does not name WCAG, but the Office for Civil Rights (OCR) has been resolving Section 504 web-accessibility complaints against WCAG 2.0 AA and, more recently, 2.1 AA for over a decade. OCR resolution agreements routinely specify WCAG conformance as the remediation standard. Treat WCAG 2.2 AA as the operational floor for Section 504 compliance even though the statute does not say it in those words.

When a Section 504 or ADA Title II complaint is filed with the US Department of Education's Office for Civil Rights against a school or university, OCR investigates and — if it finds non-compliance — typically settles via a resolution agreement rather than litigation. These agreements are public, and a typical web-accessibility resolution specifies WCAG 2.1 AA conformance for both new and existing web content, a remediation timeline (often 18-24 months for legacy content), an annual self-audit, designated accessibility staff, and training requirements. The agreements bind the institution for several years and OCR monitors compliance with periodic reporting.

Effectively yes for anything assigned as required course content. The DOJ's 2024 Title II rule sets WCAG 2.1 AA as the standard for state and local government, which includes public K-12 districts, and WCAG 1.2.2 requires captions for prerecorded audio in synchronised media. Auto-generated captions are not, on their own, accurate enough to satisfy WCAG — they need human review or a vendor that meets a stated accuracy floor. The compliance deadline under the 2024 rule was April 24, 2026 for large entities and April 24, 2027 for small entities, with limited exceptions for archived or pre-rule content that is not currently being used.

The vendor is not directly liable under ADA Title II or Section 504 — but the institution that procures and deploys the vendor's product is. That is why procurement contracts for LMS, video conferencing, proctoring, publisher content, and ancillary EdTech increasingly require a current VPAT (or its EU equivalent, an EN 301 549 conformance statement), an accessibility roadmap, and indemnification language. If you are evaluating a new EdTech tool, ask for the VPAT, validate it against your top three workflows, and write the accessibility commitments into the contract — not the marketing.

In principle yes, but the lived experience varies sharply by version and configuration. Respondus LockDown Browser and Monitor have shipped accessibility improvements in recent releases, but the underlying model — locking the browser, watching the user, blocking unapproved processes — interacts badly with screen readers, magnifiers, and dictation software. The institution's accommodation policy should specifically address proctoring: many universities allow an alternative supervised testing arrangement (in-person or remote with a human proctor) for students who use AT, and the Disability Services Office authorises it. Do not let the procurement decision foreclose accommodations.

Increasingly yes. The European Accessibility Act binds private-sector EdTech vendors selling into the EU from June 2025, and the Web Accessibility Directive (WAD) has bound public-sector education buyers since 2020. EU procurement processes for universities, schools, and ministries now routinely require an EN 301 549 conformance statement (the EU's harmonised technical standard, which incorporates WCAG 2.1 AA plus mobile, hardware, and documentation criteria). A US VPAT is a starting point but is not sufficient on its own; EN 301 549 covers additional surfaces the VPAT does not.

Course content turns over every semester, faculty add new materials weekly, and the LMS vendor itself ships updates several times a year — so a one-time audit is obsolete by the next academic term. The pattern that works is three layers: automated scanning across the LMS and every new course shell on a continuous basis; a per-semester sampling audit of a representative slice of active courses; and a full manual audit (with testers including current or recent students with disabilities) every 12-18 months and after any major LMS upgrade or replatform.