Canadian website accessibility checklist.

Who this checklist is for

This checklist is for Canadian web teams, agencies, nonprofits, small businesses, municipalities, and suppliers that need a practical review path. It does not determine legal obligations. Depending on organization type and context, get qualified advice for formal requirements.

What a first-pass checker can help with

Use automated triage to find obvious machine-detectable issues quickly: missing alt attributes, empty headings, skipped heading levels, unlabeled forms, vague links, empty buttons, missing page language, duplicate IDs, iframe title problems, and some contrast failures.

Use the accessibility issue library to understand common findings and fixes as you work through reports. Download printable checklists and handoff templates for offline use and client communication.

Start with structure

• Every page has a unique, useful title.
• The html element declares the page language, such as en-CA or fr-CA.
• There is one clear main heading.
• Headings follow a logical outline.
• The main content is inside a main landmark.
• Keyboard users can skip repeated navigation.

Check images and media

• Important images have meaningful alt text.
• Decorative images use empty alt text.
• Linked images describe the link purpose.
• Charts, infographics, videos, and audio have text alternatives where needed.

Check forms and interactions

• Every form field has a persistent label.
• Error messages explain what went wrong and how to fix it.
• Buttons have clear accessible names.
• All interactive elements can be reached and used by keyboard.

Check content and readability

• Link text makes sense out of context.
• Text has enough contrast.
• Information is not conveyed by colour alone.
• Instructions avoid vague location-only language like "click the red box on the right".

Check what automation cannot prove

• Screen reader flow makes sense.
• Focus order is logical.
• Alt text is actually useful in context.
• PDFs and documents are accessible.
• Captions and transcripts are accurate.

What still needs qualified review

Qualified review matters when you need a WCAG conformance claim, a formal audit, a procurement response, legal advice, or testing of complex flows such as checkout, applications, bookings, dashboards, maps, and authenticated tools.

Suggested workflow for web teams and agencies

1. Inventory key templates and high-value user journeys.
2. Run a first-pass scan on representative pages.
3. Fix critical and major issues before manual review.
4. Use focused tools for alt text, headings, and colour contrast.
5. Test keyboard navigation and screen reader flow.
6. Review documents, video, third-party widgets, and forms.
7. Document known limitations and next fixes in an accessibility statement if appropriate.

Common mistakes

• Reviewing only pages that are easy to test.
• Leaving old PDFs and embedded forms outside the review scope.
• Using generic alt text that technically passes a missing-alt check but does not help users.
• Assuming a clean automated report means the site conforms to WCAG.

Practical next steps

Run a first-pass scan on important pages, fix critical and major issues first, then use this checklist for keyboard, screen reader, document, and content review.

Recommended next steps

Run the checker Start with one important page or template. How to use your accessibility report Turn findings into tickets, client summaries, and manual review checklists. Use the issue library Connect report findings to practical fix guidance. Check alt text Review missing, generic, repeated, and filename-like image text. Check heading structure Confirm the page outline is usable. Generate a statement draft Document current status and known limitations. Accessibility checks by page type Learn how review priorities differ for homepages, contact pages, and more. Small business guide Triage what matters on a limited budget. Agency checklist Build a repeatable QA process for client projects.