Canvas LMS Accessibility Checklist 2026 | WCAG 2.1 AA & Title II
Last updated: 2026-07-30
Canvas is the learning management system for a large share of universities, community colleges, and K-12 districts, which means it is also where most of an institution's accessibility risk actually lives. Instructure builds the platform to standards, publishes conformance documentation, and ships an accessibility checker directly into the Rich Content Editor. None of that governs what gets published inside a course, and that is where audits and complaints land. A Canvas course is authored by an individual instructor, usually under time pressure, usually with no accessibility training, and almost never with an editorial review step. What accumulates over a few semesters is predictable: scanned chapter readings that are images of text, lecture slides exported straight to PDF, module headings faked by bolding a line, publisher content dropped in through an LTI tool nobody evaluated, and last year's lecture recordings carrying automatic captions that never got corrected. The legal exposure is unusually concrete here. Public universities, colleges, and school districts fall under the Department of Justice Title II web rule, which requires WCAG 2.1 Level AA by April 26, 2027 for entities serving 50,000 or more people and by April 26, 2028 for smaller entities and special districts. Federal grant recipients face Section 504 and Section 508 obligations, and institutions enrolling EU students face the European Accessibility Act. More practically, an inaccessible course is a barrier to a graded requirement, so a student who cannot read the assigned chapter or take the timed quiz has a direct academic injury that resolves through the disability services office, the Office for Civil Rights, or a lawsuit. This checklist targets the course content and configuration layer, because that is where nearly every Canvas failure originates and where instructors can actually fix it.
Common Accessibility Issues
The assigned reading in most Canvas courses is a PDF, and a large share of those PDFs are photocopied book chapters, scanned article reprints, or slide decks exported with print-to-PDF. An image-only scan contains no text at all, so a screen reader announces an empty page, and text-to-speech, translation, reflow on a phone, and highlighting all fail equally. Because the file is the assigned reading rather than supplementary material, a blind or dyslexic student is locked out of the course requirement itself, not merely inconvenienced.
Replace scanned chapters with publisher-supplied digital editions or library-licensed accessible copies, which most academic libraries can source on request and far faster than instructors expect. Where a scan is unavoidable, run optical character recognition and proofread the output rather than trusting it, since OCR mangles equations, tables, and multi-column layouts. Author new handouts and slide decks in Word or PowerPoint with real heading styles, alt text, marked table header rows, and a declared document language, then export using the accessibility-preserving export option instead of printing to PDF. For short text content, skip the file entirely and build a Canvas Page, which reflows, scales, and reads reliably on every device.
Course pages and announcements routinely embed images with no alternative text, and in technical courses the pattern is worse: equations, code samples, chemical structures, and data tables get pasted in as screenshots because that was faster than typing them. A screen reader user receives a filename or silence where the actual instructional content sits. Complex images such as anatomical diagrams, circuit schematics, and statistical plots are also treated as if a single short alt attribute could carry them, which it cannot.
Set meaningful alternative text on every informative image, describing what the image teaches in the context of the lesson rather than naming the object, and mark purely decorative images as decorative so screen readers skip them. Stop pasting screenshots of text: type equations using the Rich Content Editor's built-in equation editor, which produces accessible math, and paste code as real text in a code block. For complex diagrams and charts, put the full explanation in the page body or a linked accessible document and use the alt text to point to it, since the underlying data and relationships are the instructional content.
Instructors building pages in the Rich Content Editor commonly create structure visually, selecting a line and applying bold or a larger size instead of using the paragraph style menu. The page looks organized and carries no programmatic structure whatsoever, so a screen reader user cannot jump between sections of a long syllabus or module overview and must listen linearly to reach the assignment instructions. The same problem arrives wholesale when content is pasted from Word or a website, which brings inline styling rather than semantics.
Use the paragraph style menu to apply real Heading 2 and Heading 3 levels for every section title, and control appearance through the institution's theme rather than by hand-setting font sizes and colors. Keep levels in sequence without skipping, remembering the page title already sits at the top of the outline. Paste as plain text and reapply styles when importing from Word, Google Docs, or a publisher site. Run the accessibility checker built into the Rich Content Editor before saving, which flags heading order, missing alt text, contrast, and table header problems while the instructor is still on the page.
Recorded lectures, Studio videos, embedded YouTube links, and screen-capture walkthroughs are frequently published with no captions or with unreviewed automatic captions. Automatic captioning is least reliable exactly where courses need it most, garbling technical vocabulary, discipline-specific terminology, instructor and author names, and any speech over background noise or through a poor microphone. Deaf and hard of hearing students then receive a distorted version of the lecture their classmates heard clearly, and audio-only content such as podcast assignments offers no alternative at all.
Treat automatic captions as a first draft that must be reviewed and corrected for terminology, names, and acronyms before the media is published to students. Provide a transcript alongside long recordings so students can search, skim, and study rather than scrubbing through video, which benefits the whole class and is often the cheapest accommodation available. Describe essential visual information the audio never states, such as what is being pointed at on a slide or written on a board. When a recording is required coursework, treat missing captions as a publishing blocker rather than a follow-up task, because a student cannot be required to complete content they cannot perceive.
Quizzes configured with tight time limits, one-question-at-a-time locking, and lockdown or proctoring tools create a compounding barrier for students using assistive technology. A screen reader user needs substantially longer to work through a question, and lockdown browsers and proctoring extensions frequently interfere with screen readers, magnification, and speech input outright, or flag their use as suspicious behavior. Question types that depend on drag and drop or on hotspot selection are often not keyboard operable at all, so the student cannot answer regardless of how much time is allowed.
Set time limits based on the assessment's purpose rather than habit, and apply approved extended-time accommodations through Canvas moderation before the quiz opens rather than scrambling during it. Verify that any lockdown browser or proctoring tool in use documents compatibility with screen readers and magnification, and provide an alternative assessment path when it does not. Avoid drag-and-drop and hotspot question types unless you have tested them by keyboard alone, and prefer multiple choice, multiple answer, or text entry equivalents. Allow backtracking rather than locking each question, since a student using speech output often needs to re-read earlier items.
Much of the graded work in a modern Canvas course happens outside Canvas, inside LTI integrations: publisher homework platforms, adaptive learning systems, virtual labs, coding environments, video discussion tools, and plagiarism checkers. These reintroduce the failures Canvas itself avoids, including controls that cannot be reached by keyboard, custom widgets with no accessible name or state, interactive simulations with no text alternative, and dynamic feedback that is never announced. Because the tool holds the homework or the lab, a failure there blocks the grade rather than degrading the experience.
Require an accessibility conformance report before any LTI tool is enabled at the account level, and test the actual student workflow by keyboard and screen reader instead of trusting the vendor document, which often describes an older version. Make keyboard operability and a meaningful accessible name on every control the minimum gate. Where a tool is contractually locked in and inaccessible, arrange an equivalent alternative assignment in advance and state it in the syllabus so a student does not have to negotiate it mid-term. Feed findings back to procurement, since renewal is the only leverage point most institutions actually have.
Canvas LMS-Specific Tips
- Run the accessibility checker in the Rich Content Editor before saving every page, announcement, and assignment description.
- Use the equation editor for math instead of pasting screenshots, since screenshots of equations are unreadable to screen readers and unsearchable for everyone.
- Build short readings as Canvas Pages rather than PDF attachments, because pages reflow on phones and read reliably in every assistive technology.
- Ask the library for an accessible digital edition before scanning a chapter, and start that request early since sourcing can take weeks.
- Fix courses in copy-forward order: remediating the master course once stops the same broken content from propagating every term.
- Check LTI tools by keyboard before enabling them account-wide, because one inaccessible integration affects every course that adopts it.
Recommended Tools
Instructure Accessibility
Instructure's accessibility documentation for Canvas, including conformance reports and guidance on the accessibility checker built into the Rich Content Editor.
axe DevTools
A browser extension that audits a rendered Canvas page for contrast failures, missing accessible names, heading structure problems, and non-semantic interactive controls introduced by themes and LTI embeds.
NVDA
A free Windows screen reader for verifying that course images are described, that quiz question types are operable, and that LTI tool interfaces expose their controls in a usable order.
PAC (PDF Accessibility Checker)
A free checker for testing whether readings and handouts posted to Course Files are properly tagged, or whether they are untagged exports and image-only scans.
Frequently Asked Questions
Instructure publishes accessibility conformance reports for Canvas. Why did our courses still fail an audit?
Because an audit reviews the courses your institution published, not the platform's own code. Canvas gives instructors accessible building blocks and an accessibility checker in the editor, and Instructure documents the product's conformance. What the platform cannot do is stop an instructor from uploading a scanned chapter, bolding a line instead of applying a heading style, publishing a lecture recording with uncorrected automatic captions, or enabling a publisher LTI tool that is not keyboard operable. A Canvas instance reflects the authoring habits of every instructor who teaches in it, with no editorial layer in between. That is also why training, an accessible master course template, and a review gate on new LTI tools produce far more measurable improvement than any technical configuration change.
Do we have to remediate every course, or only courses with a registered disabled student?
Waiting for a registered student is the approach that generates complaints. Under the Department of Justice Title II web rule, public institutions have a proactive obligation to meet WCAG 2.1 Level AA rather than a duty to react once someone asks, and the conformance deadline is April 26, 2027 for entities serving 50,000 or more people and April 26, 2028 for smaller entities and special districts. Practically, reactive remediation also fails on timing: a student who discovers in week three that the assigned readings are image-only scans has already fallen behind while the fix is negotiated, and a scanned chapter can take weeks to replace with an accessible edition. The workable approach is to prioritize rather than boil the ocean. Fix high-enrollment courses, required core sequences, and the master templates that get copied forward each term, because remediating a master course once stops the same broken files from reappearing every semester. Handle low-enrollment electives and archived courses on request, provided that request path is genuinely fast.
Our publisher's homework platform is not accessible and we cannot change textbooks mid-term. What now?
Separate the immediate obligation from the long-term fix. Immediately, arrange an equivalent alternative for the graded work the tool holds, describe it in the syllabus so a student does not have to negotiate an accommodation mid-semester, and confirm the alternative is genuinely equivalent in weight and difficulty rather than a token substitute. Document the barrier in writing with specifics, such as which controls cannot be reached by keyboard and which feedback is never announced, and send it to both the vendor and your procurement office. Then make it a renewal condition. Institutional purchasing is the only real leverage on publisher platforms, and vendors respond to contract language and adoption decisions far more reliably than to individual bug reports. Requesting an accessibility conformance report before the next adoption cycle, and testing the actual student workflow rather than reading the document, prevents the same situation from recurring with the next edition.
Further Reading
Other CMS Checklists
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.