Public colleges, universities, and community colleges are covered by Title II of the ADA. Under the 2024 Department of Justice rule, their web content and mobile apps must conform to WCAG 2.1 Level AA. That includes the learning management system, every course inside it, and the third-party tools integrated through LTI. Large public institutions face an April 24, 2026 deadline. Smaller public institutions have until April 24, 2027. The LMS sits at the center of this requirement because nearly every student interaction with the institution runs through it.
| Item | Detail |
|---|---|
| Standard | WCAG 2.1 Level AA |
| Who is covered | Public colleges, universities, community colleges, and state-run institutions |
| Deadlines | April 24, 2026 (50,000+ population); April 24, 2027 (under 50,000) |
| Scope | LMS shell, course content, third-party LTI tools, mobile apps, PDFs, videos |
| Documentation | Audit report, remediation tracking, ACRs from LMS and tool vendors |
What does ADA Title II require for an LMS?
The DOJ rule requires that web content and mobile apps provided by a public entity conform to WCAG 2.1 AA. For a higher education institution, the LMS is web content. So is every page, document, video, and quiz inside a course shell. So is the LMS mobile app students use to check grades or submit work.
The rule does not stop at the platform vendor. The institution is responsible for conformance across content it controls and content it procures. If Canvas, Blackboard, Brightspace, or Moodle is the platform, the vendor provides the application layer. The institution is responsible for everything faculty and staff create or upload inside it.
The two layers of LMS conformance
Think about the LMS in two layers. The first is the platform itself, the code and interface built by the vendor. The second is the content layer, what instructors and instructional designers put inside courses.
Platform vendors should provide an ACR documenting WCAG conformance for their product. Institutions request this during procurement and on renewal. The content layer is where institutions carry the most responsibility, because it changes every semester and is created by hundreds or thousands of people.
Course content is where most accessibility issues live
A WCAG 2.1 AA audit of an LMS platform will identify issues in the application code. But the volume of issues sits in course content. PDFs scanned from textbooks with no text layer. Videos posted without captions. Images used to convey key concepts without alt text. Color-only indicators on rubrics. Tables built with visual formatting instead of header cells.
Each of these is an issue under WCAG, and each is created by a human inside the course shell. No platform fix addresses them. Institutions need a process for evaluating course content, training faculty, and remediating what already exists.
Third-party tools and LTI integrations
Most LMS environments include dozens of integrated tools: proctoring software, video platforms, publisher courseware, plagiarism checkers, lecture capture, adaptive learning systems. Each one loads as part of the student experience. Each one must conform.
Institutions should request an ACR from every tool vendor and verify the scope of the report matches what students actually use. A vendor ACR that covers only the marketing site does not document conformance of the student-facing tool.
How should an institution start?
Begin with an inventory. List the LMS, every integrated tool, every mobile app, every public-facing site, and every category of course content. Then map each item to a responsible owner inside the institution.
From there, conduct a WCAG 2.1 AA audit of the LMS shell and the most-used templates and course types. The audit identifies the issues. Remediation addresses them. Documentation captures the work for the record.
Automated scans cannot determine conformance, and they flag approximately 25% of issues. A manual evaluation by a qualified auditor is the only way to verify WCAG 2.1 AA conformance for the LMS and the content inside it. Scans have a role in monitoring after remediation, but they are not the path to compliance.
Faculty training is part of compliance
An institution cannot remediate its way out of an ongoing content creation problem. If faculty keep posting inaccessible PDFs and uncaptioned videos, the next semester will look like the last one.
Training is the long-term fix. Instructional designers, faculty, and course developers need working knowledge of how to create accessible documents, captioned media, properly structured pages, and accessible quiz formats. Institutions that bake accessibility into course design templates and faculty onboarding see fewer issues year over year.
Documentation the institution needs
For Title II, documentation matters. An institution should keep its audit report, a remediation tracker showing progress, ACRs from the LMS vendor and tool vendors, a digital accessibility policy, faculty training records, and a process for addressing accessibility requests from students.
This is the paper trail that demonstrates good-faith conformance work. It also gives the institution a clear answer when a student, parent, faculty member, or regulator asks what is being done.
What happens if a public university misses the deadline?
The rule went into effect with hard compliance dates. Missing the deadline exposes the institution to DOJ enforcement and to student complaints filed with the Office for Civil Rights. OCR resolution agreements with universities have historically required full audits, remediation plans, training programs, and ongoing reporting. Starting late costs more than starting early.
Do open educational resources need to meet WCAG 2.1 AA?
Yes. If the institution provides the OER through its LMS or website, it is web content under the rule. The source does not change the requirement. Institutions adopting OER should evaluate accessibility before adoption, the same way they would evaluate a publisher textbook or LTI tool.
Does the rule apply to password-protected course content?
Yes. Title II does not exempt content because it sits behind a login. Course shells, gradebooks, discussion boards, and student portals are all covered.
Are archived courses covered?
The rule includes a narrow exception for certain archived web content, but it is limited. Active courses, courses available for enrollment, and content currently used by students are not archived. Institutions should not rely on the archive exception as a shortcut.
The institutions making the most progress treat the LMS as a long-term accessibility program, not a one-time project. Audit, remediate, document, train, repeat each term.
Contact me for help with ADA Title II compliance for your LMS and course content: krisrivenburgh.com/contact.