Digital accessibility in Canada.

The pieces people confuse

WCAG is the technical accessibility standard most teams hear about. AODA is Ontario's accessibility law. The Accessible Canada Act affects federally regulated contexts. Government and procurement requirements can bring additional expectations. That is why SiteCheck Canada starts with practical website checks instead of pretending every organization has the same legal situation.

Who this page is for

This guide is for Canadian businesses, nonprofits, agencies, public-sector teams, and suppliers that need a practical starting point. It is not a substitute for qualified legal or accessibility advice when formal obligations matter.

Where a first-pass checker helps

A scan can find obvious machine-detectable problems quickly: missing image alternatives, heading outline defects, unlabeled controls, vague links, empty buttons, missing page language, duplicate IDs, iframe title issues, and some contrast problems. It is especially useful before redesigns, client handoffs, content audits, and accessibility reviews. Use the accessibility issue library to understand common findings and fixes.

Where humans still matter

Real accessibility includes keyboard flow, screen reader clarity, content quality, media alternatives, documents, error recovery, plain-language task completion, and user feedback. Automated checks should support that review, not stand in for it.

Suggested workflow for web teams and agencies

1. Pick a small set of important templates and user journeys.
2. Run the website accessibility checker and fix obvious critical issues.
3. Use the focused tools for alt text, headings, and colour contrast.
4. Use the Canadian checklist for manual review.
5. Write a cautious accessibility statement only after checking it against the real site.

Common mistakes

• Assuming one Canadian rule applies to every organization in the same way.
• Treating WCAG as only a developer checklist and missing content, documents, and support paths.
• Publishing a compliance claim before manual review.
• Forgetting that procurement or client contracts may include accessibility expectations even when a public website law is unclear.

Practical next steps

Check a few important page templates, fix the obvious issues, then use the checklist and automation limitations guide to plan manual review and documentation.

Recommended next steps

Run the checker Check one important page or template first. Use the issue library Turn common report findings into practical fixes. Open the Canadian checklist Use a broader review path after the first scan. Read the AODA guide Understand Ontario-specific website accessibility context. Read what automation misses Plan keyboard, screen reader, content, and document checks.