Evaluating Canvas Accessibility Checks and Course Content
Check the tools enabled in your Canvas deployment, then evaluate pages, documents, media and student tasks beyond the scanner’s tested scope.
Canvas accessibility checks can support course authors, but their result needs a declared scope. Determine which editor, course-level and licensed services are enabled in the institution's actual deployment. Features and coverage change; use current Instructure documentation and representative test content.
Check the course rather than one indicator
Review authored pages for meaningful headings, links, image descriptions, contrast and keyboard access. Assess uploaded documents separately for structure, reading order, tables and preserved content. Review media for synchronized captions and essential visual information. Test assessments and external links using the intended roles and assistive technologies.
There is no verified universal percentage of issues caught by Canvas or by every automated checker. A green indicator can reflect the rules that ran while other conditions remain untested. Do not translate it into a WCAG conformance percentage.
Use existing tools for demonstrated work
An editor checker, a course checker, an uploaded-file service and alternative formats may cover different content. Test known issues to discover actual coverage. Inspect whether a feature changes the original file or provides a separate representation, and evaluate the resulting student task.
Aelira's integration boundary
Canvas integration has release-specific verification evidence, including supported stored-content workflows. That evidence does not establish every course, role, file format or full student journey. Inspect the current Core release documentation and evaluate authorized representative files in a bounded test course.
Core is beta. Supported workflows can apply partial fixes; some material remains manual or cannot deliver a downloadable candidate. Review the actual saved file and unresolved work. Automated scores describe implemented checks rather than conformance.
Build the remaining review plan
Assign owners for generated descriptions, ambiguous structures, caption corrections and unsupported material. Retain the original and saved identities, validation results and review decisions. Measure total accepted-output effort and failures before publishing any efficiency claim.
Aelira Team
•Accessibility EngineersThe Aelira team is building beta accessibility tools for higher education. Institutions can evaluate selected checks and partial fixes on their own files, with human review required before publication.
Related Articles
A PowerPoint Accessibility Review Checklist for Faculty
Review slide structure, alternatives, contrast, tables, links, media and exported files. This checklist guides evaluation without certifying every applicable WCAG condition.
Aelira Core v0.9.12: publishing the security record with the release
Aelira Core v0.9.12 fixes a LaTeX file-access vulnerability, publishes three security advisories, discloses every unfixed image advisory and adds reviewed PDF working files.
I applied for GitHub's security fund. Then CodeQL found 42 alerts.
We applied for GitHub's security fund, then CodeQL raised 42 alerts. Here's what we changed, deployed and still need to review.