The quick version
Start with page structure, headings, alt text, forms, links, buttons, contrast, keyboard navigation, documents, and media. Then add a feedback path so users can report barriers and your team can track fixes.
Why Canada context matters
Canada does not have one simple universal website rule for every organization. Ontario, federal accessibility expectations, procurement contexts, and Quebec/French-language realities all shape what teams worry about. A practical checklist helps you avoid pretending one scan answers everything.
Who this page is for
This guide is for teams that need a practical first pass before a formal audit, procurement response, client launch, redesign, or content cleanup. Depending on organization type and context, you may need qualified advice for formal obligations.
New to accessibility review? Start with the small business guide or the nonprofit checklist for audience-specific guidance.
What a first-pass checker can help with
Automated triage can quickly catch missing alt attributes, heading issues, unlabeled form controls, link and button naming problems, iframe title issues, duplicate IDs, page language problems, and some simple contrast failures. Use the accessibility issue library to understand common findings and fixes.
What still needs qualified review
Manual testing is still needed for keyboard order, screen reader experience, content clarity, documents, captions, transcripts, dynamic widgets, and any formal conformance or legal claim.
Recommended workflow
- Run the website accessibility checker on important templates.
- Use focused checks for alt text, heading structure, and colour contrast.
- Export a developer-friendly report.
- Fix critical and major issues first.
- Perform keyboard and screen reader review.
- Update or publish an accessibility statement with the accessibility statement generator.
- Repeat after redesigns, new templates, and major content changes.
Common mistakes
- Checking only the homepage and ignoring forms, search results, checkout flows, or service pages.
- Fixing colour contrast while leaving missing labels or broken keyboard access.
- Publishing a statement that says more than the review evidence supports.
- Forgetting PDFs, videos, third-party widgets, and embedded forms.
Next step
Open the detailed checklist, then use the limitations guide to plan the human review.