An accessible website is one that people can use whether they see, hear, move or process information differently: someone using a screen reader, someone who navigates with a keyboard instead of a mouse, someone with low vision who zooms the page, or someone reading captions in a noisy place. For a business, accessibility is partly about doing right by customers, partly about legal obligations that are growing in Canada, and partly about plain usability. Most accessibility fixes make a site easier for everyone.
This guide explains what the standard is, what the law broadly expects in Canada, the problems we see most often and how to check your own site.
What WCAG is
The Web Content Accessibility Guidelines, or WCAG, are the international standard for web accessibility, published by the W3C. They are organized around four principles: content must be perceivable, operable, understandable and robust. Each guideline has success criteria at three levels, A, AA and AAA. Level AA is the level most laws and organizations point to, and the practical target for a business website.
WCAG 2.2, published in 2023, is the current version. It builds on WCAG 2.1 and adds a few criteria, mostly about people who use a keyboard, have limited dexterity or find complex steps hard:
- Focus not obscured: when a visitor tabs to a link or button, sticky headers or banners must not hide it.
- Target size: buttons and links need to be large enough, or spaced far enough apart, to tap reliably.
- Dragging movements: anything that requires dragging, such as a slider, needs a simpler alternative.
- Consistent help: contact details or help links should appear in the same place across pages.
- Redundant entry: people should not have to type the same information twice in one process.
- Accessible authentication: logging in should not depend on memorizing or transcribing codes without help, such as allowing password managers and paste.
A site that meets WCAG 2.1 AA is most of the way to 2.2 AA; the new criteria are worth checking on their own.
What the law broadly expects in Canada
Accessibility law in Canada depends on who you are and where you operate. The federal Accessible Canada Act applies to federally regulated organizations, such as banks, telecommunications companies and interprovincial transportation. Ontario's accessibility legislation, the AODA, sets specific website requirements, including for many private organizations. Other provinces, including British Columbia and Manitoba, have their own accessibility laws, which differ in who they cover and what they require. Separately, human rights legislation across Canada prohibits discrimination in providing services, and that can extend to services offered online.
This is a general overview, not legal advice. Whether specific requirements apply to your business depends on your sector, size and where you operate, so confirm the details with qualified counsel or the relevant government body.
Whatever applies to you formally, WCAG 2.1 or 2.2 Level AA is the sensible benchmark to build to.
The most common problems
When we review business websites, the same issues come up again and again:
- Low colour contrast. Light grey text on white, or text over busy photos. WCAG AA asks for a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text.
- Missing or useless alt text. Images that carry meaning need a short text alternative. "Image1.jpg" or "photo" does not help anyone; purely decorative images should be marked so screen readers skip them.
- Unlabelled form fields. Placeholder text that disappears when you start typing is not a label. Every field needs a proper label, and error messages need to say what went wrong.
- Links and buttons with no clear name. Icon-only buttons and "click here" links tell a screen reader user nothing.
- Keyboard traps and invisible focus. If you cannot reach every menu, form and button with the Tab key, or cannot see where you are on the page, keyboard users are stuck.
- Skipped or decorative headings. Headings chosen for their size rather than their structure make pages hard to navigate with a screen reader.
- Video without captions and audio without transcripts.
- Content that moves or plays on its own, such as carousels and auto-playing video without a way to pause them.
- Text that breaks when zoomed. Pages should still work when text is enlarged or the browser is zoomed.
- Missing page language, which affects how screen readers pronounce the content.
How to check your own site
You do not need special training to find the most obvious problems:
- Use the keyboard only. Put the mouse aside and press Tab through your homepage and contact form. Can you reach everything, see where you are, and submit the form?
- Zoom to 200%. Does the page still work, or does text overlap and disappear?
- Run an automated checker. Tools such as WAVE, axe or the accessibility audit in Chrome's Lighthouse flag issues like contrast, missing labels and alt text. They catch only part of the problems, so treat a clean result as a starting point, not proof.
- Try a screen reader. VoiceOver is built into Apple devices and NVDA is free on Windows. Even ten minutes listening to your own site is revealing.
- Check your PDFs and videos, not just your pages.
A word on accessibility overlays
Some products promise to make a website accessible with a single line of code, by adding a widget with contrast toggles and text resizing. These overlays do not fix the underlying code, such as missing labels, broken keyboard navigation or poor heading structure, and many people who rely on assistive technology find them get in the way. They are not a substitute for building the site accessibly.
Building it in from the start
Accessibility is far cheaper to build in than to retrofit. It starts with design choices, such as colour palettes with enough contrast, visible focus styles and readable type sizes, and continues into code: semantic HTML, proper labels, one clear heading structure per page and components that work with a keyboard. Content matters too, because alt text, captions and plain language are written, not coded.
Our builds follow WCAG 2.1 AA guidelines from the design stage onward. If you would like your current site reviewed for accessibility, or want accessibility planned into a new build, get in touch and we will tell you what we find and what it would take to fix.