Website accessibility (WCAG): a practical guide for Canadian businesses

Website accessibility means building a site that everyone can use, including people who have visual, hearing, motor or cognitive differences. In Canada the practical benchmark is WCAG 2.1 Level AA, which Ontario's AODA law references for many organisations. Meeting it widens your audience, lowers legal risk and tends to improve SEO at the same time.

Key takeaways

• WCAG 2.1 Level AA is the standard most Canadian businesses should aim for; it is the level AODA points to for public-facing websites.
• Accessibility is not just compliance — roughly one in five people lives with a disability, so an inaccessible site quietly turns away real customers.
• The most common failures are low colour contrast, missing alt text, unlabelled forms, mouse-only interactions and uncaptioned video. Most are cheap to fix when built in early.
• Many accessibility practices (clean headings, descriptive alt text, semantic markup) overlap with SEO basics, so the same work helps you rank.
• Accessibility is ongoing: audit, fix, then re-test after every redesign or major content change.

What is website accessibility?

Accessibility is the practice of designing and building a website so that people can perceive, understand, navigate and interact with it regardless of how they access the web. That includes someone using a screen reader because they are blind, a person who navigates by keyboard because they cannot use a mouse, a customer with low vision who zooms to 200%, and an older user who simply finds small, low-contrast text hard to read.

It is easy to assume this is a niche concern, but it is not. A large share of the population has a disability of some kind, and many more experience temporary or situational limitations — a broken arm, bright sunlight on a phone screen, a noisy room where audio is useless. Designing for the edges almost always produces a clearer, calmer experience for everyone in the middle.

Crucially, accessibility is a property of the whole experience, not a plugin you bolt on. An "accessibility widget" that adds a floating toolbar does not make an inaccessible site compliant; the underlying HTML, contrast, structure and interactions are what matter.

WCAG and AODA in plain terms

Two acronyms come up constantly, and they are easy to mix up.

WCAG: the international standard

WCAG (Web Content Accessibility Guidelines) is the globally recognised technical standard, published by the W3C. It is organised around four principles — content must be Perceivable, Operable, Understandable and Robust (POUR) — and it defines three conformance levels: A (minimum), AA (the common target) and AAA (strictest). Most laws and contracts reference WCAG 2.1 or 2.2 at Level AA, which is the realistic, achievable bar for a small-business website.

AODA: Ontario's law

AODA (the Accessibility for Ontarians with Disabilities Act) is provincial legislation that requires many organisations operating in Ontario to make their public websites accessible to WCAG 2.0 Level AA (with limited exceptions). Federally regulated organisations also have obligations under the Accessible Canada Act, and human-rights law across Canada increasingly treats inaccessible digital services as a form of discrimination. If you do business in Ontario or serve a national audience, designing to WCAG AA is the safe, defensible choice.

The short version: WCAG is the "how," AODA and similar laws are the "you must." Build to WCAG AA and you satisfy the spirit of the legislation while making your site better for everyone.

Why accessibility is good business

Compliance is the floor, not the reason. Accessible sites perform better commercially in several measurable ways.

• You reach more customers. An inaccessible checkout, form or menu silently excludes a meaningful slice of buyers — and they rarely complain, they just leave.
• You reduce legal and reputational risk. Complaints, demand letters and human-rights claims over inaccessible websites are a real and growing cost.
• You often rank better. Semantic headings, alt text, clear link labels and fast, well-structured pages help search engines understand your content. This is why accessibility work pairs naturally with our SEO basics guidance and with strong Core Web Vitals.
• You improve conversions for everyone. Clear labels, visible focus and readable text reduce friction across the board, which is exactly what we focus on when shaping a high-converting homepage.

It is rare for the ethical choice and the profitable choice to be the same choice. Accessibility is one of those rare cases, which is why we build to best practice by default rather than treating it as an upsell.

The four WCAG principles, made practical

WCAG can read like a wall of technical criteria, so here is what each principle actually asks of a small-business website.

Perceivable

Users must be able to perceive your content with the senses available to them. In practice: provide text alternatives (alt text) for meaningful images, captions and transcripts for video and audio, and enough colour contrast between text and background. Never rely on colour alone to convey meaning — pair it with a label or icon.

Operable

Everything must work without a mouse. Every link, button, menu and form control should be reachable and usable with a keyboard, with a clearly visible focus indicator. Avoid time limits that cannot be extended, and steer clear of content that flashes rapidly.

Understandable

Text should be readable and the interface predictable. Use plain language, consistent navigation, clear instructions and helpful error messages. When a form field is wrong, say what is wrong and how to fix it — this connects directly to good website copy.

Robust

The code should work reliably with current and future assistive technologies. That means valid, semantic HTML, correct use of ARIA only where native HTML falls short, and components that announce their state (expanded, selected, disabled) to screen readers.

Common accessibility issues — and how to fix them

In audits of small-business sites, the same handful of problems appear again and again. The good news is that most are inexpensive to correct, especially during a build or redesign.

• Low colour contrast. Light grey text on white fails constantly. Aim for at least a 4.5:1 contrast ratio for normal text and 3:1 for large text.
• Missing or useless alt text. Meaningful images need a short, descriptive alt attribute; purely decorative images should have empty alt text so screen readers skip them.
• Forms without labels. Placeholder text is not a label. Every field needs a visible, programmatically associated label and an accessible error state.
• Mouse-only interactions. Dropdowns, sliders and modals that only respond to hover or click lock out keyboard users.
• No visible focus. Removing the focus outline for aesthetics leaves keyboard users unable to see where they are.
• Uncaptioned video. Video content needs captions; spoken-only content benefits from a transcript.
• Skipped heading levels. Headings should describe structure (one H1, then H2s and H3s in order), not be chosen for visual size.

If your current site shows several of these, it is often a signal of deeper structural age — one of the signs your website needs a redesign. When you do rebuild, do it carefully so you keep your rankings, as we cover in redesign without losing SEO.

A WCAG AA checklist you can actually use

Use this as a pre-launch and quarterly review list. It will not cover every WCAG criterion, but it catches the issues that affect the most users.

1. Contrast: all body text meets 4.5:1; large text and UI components meet 3:1.
2. Images: meaningful images have descriptive alt text; decorative images have empty alt.
3. Headings: a single H1 per page, with logical, unskipped heading levels.
4. Keyboard: you can tab through and operate the entire page — menus, forms, modals — with a visible focus ring.
5. Forms: every field has a visible label; errors are described in text and linked to the field.
6. Links and buttons: link text makes sense out of context (no bare "click here"); buttons are real buttons.
7. Media: videos have captions; audio content has a transcript.
8. Zoom and reflow: the page works at 200% zoom and on a 320px-wide screen without horizontal scrolling, which ties into mobile-first design.
9. Motion: animations respect reduced-motion settings and nothing flashes more than three times per second.
10. Language: the page declares its language; multilingual content is handled correctly, as in our multilingual websites guide.

How to test your site

Good accessibility testing combines automated tools with human judgement, because automation only catches a fraction of real-world problems.

Automated checks

Free tools such as browser-based accessibility auditors and contrast checkers will flag obvious failures — missing alt text, low contrast, missing labels and invalid markup — in minutes. Run them early and often. Treat their results as a starting point, not a pass certificate, since they cannot judge whether your alt text is actually meaningful.

Manual checks

The most valuable test costs nothing: put the mouse away and navigate the whole site with the keyboard. Then try a screen reader (VoiceOver on Mac/iOS, or NVDA on Windows) to hear how your pages are announced. Ask whether the order makes sense, whether buttons say what they do, and whether you can complete a key task such as booking or checkout. If you run a booking system or store, test those flows specifically.

Ongoing maintenance

Accessibility is not a one-time project. Every new blog post, image, form or feature can introduce a regression, so fold a quick check into your maintenance routine and re-test after any redesign.

Building accessibility in from day one

Retrofitting accessibility onto a finished site is almost always more expensive than building it in, because it can require reworking markup, components and content all at once. When accessibility is part of the brief from the start, it adds little to the timeline or cost — it simply becomes how the site is built.

That is the approach we take. Whether you are choosing between platforms (see custom-coded vs WordPress) or planning the scope of a new project, accessibility should be a baseline requirement, not an optional add-on. If you want a sense of where it fits in overall budgets, our cost of a website in Canada guide breaks down what goes into a quality build.

Frequently asked questions

Is website accessibility legally required in Canada?

For many organisations, yes. Ontario's AODA requires public-facing websites to meet WCAG 2.0 Level AA, federally regulated bodies fall under the Accessible Canada Act, and human-rights law increasingly treats inaccessible digital services as discrimination. Even where it is not strictly mandated, building to WCAG AA is the safest and most defensible choice.

What WCAG level should a small business aim for?

WCAG 2.1 (or 2.2) Level AA is the right target for almost every small business. Level A is too minimal to satisfy most laws, while Level AAA is stricter than is practical for general websites. AA is the level referenced by AODA and by most contracts, and it is genuinely achievable on a normal budget.

Does accessibility hurt design or aesthetics?

No. Accessible design is simply good design — readable type, sufficient contrast, clear structure and predictable interactions. The constraints push you toward cleaner, calmer layouts that work better for every visitor. Plenty of beautiful, award-winning sites are also fully accessible; the two goals reinforce each other.

Will accessibility help my SEO?

Yes, meaningfully. Many WCAG requirements — semantic headings, descriptive alt text, clear link labels, valid markup and fast, well-structured pages — are the same things search engines reward. Accessible sites are easier for crawlers to parse, so the work you do for users with disabilities also helps you rank for everyone else.

Can an accessibility widget make my site compliant?

No. Overlay widgets that add a floating toolbar cannot fix inaccessible underlying code, and some actively interfere with assistive technology. Real compliance comes from accessible HTML, proper contrast, keyboard support and semantic structure. There is no shortcut that replaces building the site correctly.

How much does it cost to make a site accessible?

It depends on the starting point. Building accessibility in from day one adds very little, since it is just good practice. Retrofitting an existing site costs more because it may require reworking markup, components and content. The cheapest path is always to include WCAG AA in the original brief rather than fixing it later.