Canvas Accessibility Checker: What It Misses (And How to Fill the Gaps)

If you're using Canvas LMS, you've probably noticed the accessibility indicator—that little icon that turns green, yellow, or red based on your content's accessibility status.

It's a useful starting point. But if you're relying on it for WCAG 2.1 compliance, you're missing about 60% of issues.

Here's what Canvas catches, what it misses, and how to build a complete accessibility workflow.

What Canvas Accessibility Checker Does Well

Built-in Checks (The Green Light)

Canvas's Rich Content Editor checks for:

Images:

• Missing alt text (flags images without alt attributes)
• Decorative image marking (allows marking as decorative)

Text:

• Heading structure (flags skipped heading levels)
• Large blocks of text without headings

Tables:

• Missing table headers
• Missing table captions

Links:

• Empty links (no text content)
• Links that only say "click here" (basic check)

Multimedia:

• Missing captions indicator (for Canvas-hosted video)
• Missing audio descriptions indicator

The Accessibility Indicator

The colored indicator shows:

• Green: No issues detected
• Yellow: Minor issues
• Red: Critical issues

This is genuinely helpful for catching obvious problems during content creation.

What Canvas Misses (The 60%)

1. Poor-Quality Alt Text

Canvas checks: Does alt text exist?

Canvas doesn't check: Is the alt text actually useful?

Example:

• Alt text: "image" ✅ Canvas says OK
• Alt text: "photo.jpg" ✅ Canvas says OK
• Alt text: "chart" ✅ Canvas says OK

All of these fail WCAG because they don't convey meaningful information.

What good alt text looks like:

• "Bar chart showing enrollment increased 15% from 2023 to 2024"
• "Diagram of photosynthesis: sunlight + water + CO2 → glucose + oxygen"

2. Color Contrast Issues

Canvas checks: Nothing about color contrast.

WCAG requires:

• 4.5:1 contrast for normal text
• 3:1 contrast for large text (18pt+ or 14pt bold)
• 3:1 contrast for graphical elements

Common violations Canvas misses:

• Light gray text on white backgrounds
• Colored text on colored backgrounds
• Low-contrast links
• Images with text overlaid on busy backgrounds

3. Color-Only Meaning

Canvas checks: Nothing.

WCAG requires: Don't convey information through color alone.

Common violations:

• "Correct answers in green, incorrect in red" (no icons or text labels)
• Charts with legend colors but no patterns or direct labels
• "Required fields marked in red" (no asterisk or text)

4. Uploaded File Accessibility

Canvas checks: Almost nothing for uploaded files.

What Canvas doesn't scan:

• PDFs: Structure tags, reading order, alt text, OCR status
• PowerPoints: Slide accessibility, contrast, alt text
• Word documents: Heading structure, alt text, reading order
• Excel files: Table headers, sheet organization

This is a massive gap. Most course content is in uploaded files, not Canvas pages.

5. Embedded Content

Canvas checks: Limited checks on embeds.

What falls through:

• YouTube videos without proper captions
• Third-party widget accessibility
• Embedded forms (Google Forms, Microsoft Forms)
• Interactive simulations (H5P, external tools)

6. Navigation and Structure

Canvas checks: Basic heading structure in pages.

What it misses:

• Module organization accessibility
• Consistent navigation patterns
• Breadcrumb and wayfinding
• Focus order in complex pages

7. Auto-Caption Quality

Canvas checks: Whether captions exist for Canvas Studio videos.

What it doesn't check:

• Caption accuracy (auto-captions can be 70-80% accurate)
• Speaker identification
• Sound effect descriptions
• Timing and synchronization

Remember: Auto-captions don't meet WCAG requirements.

8. Mathematical Content

Canvas checks: Nothing about math accessibility.

What it misses:

• LaTeX equations rendered as images (inaccessible)
• MathML missing or malformed
• Natural language alternatives for equations
• Chemical formulas and notation

9. Reading Level and Cognitive Load

Canvas checks: Nothing.

WCAG 2.1 AAA (and best practice for AA):

• Content should be understandable at lower secondary education level
• Complex terms should be defined
• Abbreviations should be expanded on first use

10. Form and Quiz Accessibility

Canvas checks: Basic form structure.

What it misses:

• Error message clarity and association
• Field grouping (fieldsets/legends)
• Input purpose identification
• Time limit adjustments

The Real-World Impact

Scenario: "My Canvas Pages Are All Green"

Professor Smith's course:

• All Canvas pages show green accessibility indicator
• 50 PDFs uploaded (none scanned by Canvas)
• 20 hours of video (auto-captions only)
• 100 images (alt text exists, but says "image" or "diagram")

Canvas compliance score: 100% ✅

Actual WCAG compliance: ~25% ❌

Scenario: "I Uploaded Accessible Files"

Professor Jones created accessible PowerPoints:

• Proper alt text, good contrast, correct reading order

But then:

• Uploaded to Canvas
• Canvas doesn't verify the accessibility
• Files could be corrupted, converted, or modified
• No ongoing monitoring

Initial accessibility: Good

Verified accessibility: Unknown

Building a Complete Workflow

Layer 1: Canvas Built-in Checks (Keep Using)

Canvas's checker is still valuable for:

• Real-time feedback during page creation
• Catching obvious issues immediately
• Training faculty on basic accessibility concepts

Action: Keep the accessibility indicator visible. Fix red and yellow issues.

Layer 2: Document Scanning (Add This)

For uploaded files, you need external scanning:

Option A: Manual checking

• Download each file
• Open in native application
• Run built-in accessibility checker (Adobe Acrobat, PowerPoint, Word)
• Fix issues, re-upload

Time: 15-30 minutes per file

Scalability: Poor (works for 10 files, not 1,000)

Option B: Automated scanning (Aelira)

• Bulk scan all uploaded files
• Identify issues across entire course
• AI-generated fix suggestions
• One-click remediation for common issues

Time: Minutes for entire course

Scalability: Handles thousands of files

Layer 3: Color and Contrast Auditing (Add This)

Canvas doesn't check contrast. You need:

Option A: Spot-check manually

• Use browser extensions (WAVE, axe DevTools)
• Check key pages periodically
• Document findings

Option B: Automated page scanning

• Crawl all Canvas pages
• Check contrast programmatically
• Flag violations for review

Layer 4: Caption Quality Review (Add This)

Don't trust auto-captions. For every video:

1. Generate auto-captions as starting point
2. Review and edit for accuracy
3. Add speaker identification
4. Add sound effect descriptions
5. Verify timing

Or: Use Aelira's caption enhancement to automate 80% of cleanup.

Layer 5: Ongoing Monitoring (Add This)

Accessibility isn't one-time. New content is added constantly.

Set up:

• Weekly scans of new/modified content
• Alerts for high-severity issues
• Trend reporting (are we improving?)
• Faculty accountability (who's creating inaccessible content?)

Canvas + Aelira Integration

How It Works

1. LTI Integration: Aelira connects to Canvas via LTI 1.3
2. Automatic Scanning: New uploads trigger accessibility scan
3. Dashboard View: See compliance by course, module, or file type
4. In-Context Alerts: Faculty see issues while in Canvas
5. One-Click Fixes: Common issues fixed without leaving Canvas

What Aelira Adds to Canvas

Check	Canvas	Canvas + Aelira
Alt text exists	✅	✅
Alt text quality	❌	✅
Color contrast	❌	✅
PDF accessibility	❌	✅
PowerPoint accessibility	❌	✅
Caption quality	❌	✅
LaTeX/math accessibility	❌	✅
Reading order	❌	✅
Cognitive accessibility	❌	Partial

Quick Wins: Improving Canvas Accessibility Today

This Week

1. Enable accessibility checker visibility (if hidden)

- Admin Console → Settings → Feature Options

1. Run WAVE on 5 key pages

- Homepage, syllabus, first module page, assignment page, discussion page

- Document findings

1. Spot-check 10 uploaded PDFs

- Open in Adobe Acrobat

- Run accessibility check

- Note patterns (are all PDFs missing tags?)

This Month

1. Audit one complete course

- All pages, all files, all videos

- Document total issues and types

- Estimate remediation workload

1. Implement caption review process

- For new videos: Review captions before publishing

- For existing videos: Prioritize high-enrollment courses

1. Evaluate additional tools

- Demo Aelira or similar

- Calculate ROI vs. manual checking

This Semester

1. Deploy automated scanning

- Cover all active courses

- Set up ongoing monitoring

1. Train faculty

- What Canvas checks vs. doesn't check

- How to create accessible content

- Where to get help

1. Establish baseline metrics

- Current compliance percentage

- Improvement targets

- Reporting cadence

The Bottom Line

Canvas's accessibility checker is a starting point, not a complete solution.

What it does well:

• Real-time feedback during editing
• Basic checks (alt text exists, heading structure)
• Awareness building for faculty

What it misses:

• Uploaded file accessibility (PDFs, PPTs, docs)
• Color contrast
• Alt text quality
• Caption accuracy
• Math/LaTeX accessibility
• Embedded content

To achieve actual WCAG compliance, you need to supplement Canvas with:

• Document scanning tools
• Color contrast auditing
• Caption quality review
• Ongoing monitoring

Canvas is necessary. It's not sufficient.

See how Aelira integrates with Canvas | Request a demo