In 2026, WCAG 2.2 AA is the practical accessibility bar for Canadian business websites — required by AODA in Ontario, by AccessibleBC for BC public-sector and large private-sector organizations, and by the Accessible Canada Act for federally-regulated entities. Even where it isn't legally required, WCAG 2.2 AA is increasingly demanded by enterprise procurement and tested for in vendor RFPs. This guide covers what changed in WCAG 2.2, the specific success criteria most Canadian sites fail, and a practical compliance timeline that doesn't blow the budget.
Who legally needs WCAG 2.2 AA in Canada in 2026
- AODA (Ontario). Public-sector organizations and Ontario businesses with 50+ employees must have accessible websites. The standard is WCAG 2.0 Level AA on paper, but enforcement and audit practices have aligned on WCAG 2.1/2.2 AA in recent years.
- AccessibleBC (British Columbia). All BC public-sector organizations covered by the Accessible British Columbia Act are required to meet accessibility standards (WCAG-aligned) through phased compliance ramping through 2026–2028.
- Accessible Canada Act (federal). Federally-regulated entities — banks, telecoms, federal agencies — must publish accessibility plans and progress reports, with WCAG 2.1+ AA as the digital benchmark.
- Quebec. Quebec's Standard SGQRI 008 covers government websites at WCAG 2.0 AA; private-sector requirements are weaker but accessibility-by-default is becoming the procurement norm.
- Procurement. Even where it's not statutorily required, most enterprise and public-sector RFPs in 2026 require WCAG 2.2 AA conformance as a vendor selection criterion.
What changed in WCAG 2.2 vs 2.1
WCAG 2.2 (W3C Recommendation, October 2023) added 9 new success criteria, 6 of which apply at Level AA. The ones that affect most Canadian business sites:
- 2.4.11 Focus Not Obscured (Minimum) — AA. When a UI element receives focus, it must not be entirely hidden behind another element (sticky headers, cookie banners). Catches a lot of sticky-nav patterns shipped in 2020–2024.
- 2.4.12 Focus Not Obscured (Enhanced) — AAA. Goes further: no part of the focused element can be obscured.
- 2.5.7 Dragging Movements — AA. Any drag-only interaction must have a single-pointer alternative. Affects sliders, file uploaders, kanban boards.
- 2.5.8 Target Size (Minimum) — AA. Click targets must be at least 24×24 CSS pixels (with exceptions). Catches tightly-packed nav links and tiny social icons.
- 3.2.6 Consistent Help — A. If you offer help (chat, contact link), it must appear in the same place across pages.
- 3.3.7 Redundant Entry — A. Don't make users re-enter information you already have within the same flow.
- 3.3.8 Accessible Authentication (Minimum) — AA. No cognitive function tests for login (no "remember and re-enter this code from memory"). Must allow paste, browser autofill, or biometric.
The success criteria most Canadian sites fail
In our 2026 audits across BC and Canadian client sites, the same 10 issues account for ~80% of WCAG failures:
| Issue | SC | Quick fix? |
|---|---|---|
| Insufficient colour contrast (4.5:1 text) | 1.4.3 | Yes — design tokens |
| Missing or unhelpful alt text | 1.1.1 | Yes — content audit |
| Form inputs without labels | 3.3.2 / 4.1.2 | Yes — markup fix |
| Focus indicator missing or hidden | 2.4.7 | Yes — CSS |
| Sticky nav obscures focus | 2.4.11 (new) | Medium — scroll-margin / nav restructure |
| Click targets < 24×24 px | 2.5.8 (new) | Medium — design adjustment |
| Modal/dialog focus not trapped | 2.4.3 / 2.1.2 | Medium — JS |
| Heading hierarchy broken (h1 → h3) | 1.3.1 | Easy — content fix |
| No skip-to-content link | 2.4.1 | Easy — markup |
| Carousel/slider auto-advance not pausable | 2.2.2 | Medium — controls |
A pragmatic compliance approach for 2026 SMBs
Hitting WCAG 2.2 AA on a typical SMB marketing site is a 2–4 week project, not a 6-month enterprise initiative. The phased approach we ship:
Phase 1: automated audit (1–2 days)
Run axe DevTools, WAVE, and Pa11y across every templated page type. These catch ~30–40% of WCAG issues automatically — the easy ones. Generate a backlog of the must-fix items.
Phase 2: manual audit (3–5 days)
The remaining 60–70% of WCAG issues require human judgment: keyboard navigation flows, screen-reader testing, focus-management on modals, semantic structure, content quality (alt text, link text, headings). A WCAG-trained auditor working with VoiceOver/NVDA + keyboard-only navigation finds these in 3–5 days for a typical SMB site.
Phase 3: remediation (1–3 weeks)
Fix in priority order: blockers (keyboard traps, missing form labels) first, then high-frequency visual issues (contrast, focus indicators), then specific WCAG 2.2 additions (target size, focus obscured), then content cleanups (alt text, headings). Most sites ship fixes in 1–3 weeks of focused work.
Phase 4: documentation and process (ongoing)
Publish an accessibility statement on the site, document your conformance level, list known issues with remediation timelines, and provide a contact method. Set up automated linting (ESLint a11y rules) and CI checks (axe-core in your test runner) so regressions don't reintroduce issues.
Cost of WCAG 2.2 AA conformance for a Canadian SMB site
| Site type | Cost (CAD) | Timeline |
|---|---|---|
| Brochure site (10–25 pages) | $3,500 – $8,500 | 2–3 weeks |
| Marketing site + blog | $6,000 – $14,000 | 3–4 weeks |
| SaaS marketing + product app | $15,000 – $40,000 | 5–10 weeks |
| E-commerce | $8,000 – $25,000 | 4–8 weeks |
| Multi-language enterprise | $30,000 – $80,000+ | 10–16 weeks |
Building accessibility in from the start of a new project adds 8–15% to a fixed-price build. Bolting it on after launch costs 2–4× as much because design and code decisions have to be reversed. For broader 2026 build pricing, see our Canadian web design cost guide.
Why accessibility overlays don't work
"One-line script makes your site WCAG compliant" is one of the most common claims in 2026 SaaS, and one of the most reliably wrong. Overlay tools (accessiBe, EqualWeb, UserWay) often fail accessibility testing on the very sites that install them, and have been the subject of multiple US accessibility lawsuits. They also can't fix structural issues — heading hierarchy, semantic markup, focus management — which are exactly the issues most sites fail. Overlays don't produce WCAG-conforming sites. Real remediation does.
Maintaining WCAG conformance over time
- Automated checks in CI. Run axe-core (or Playwright with axe) in your test pipeline. Block PRs that introduce regressions.
- Component-library compliance. Build accessibility into the component library once; every page using those components inherits it. Audit each component manually once.
- Editor guardrails. If non-developers edit content, give them guardrails: alt-text required on image upload, heading order validated, contrast checked on colour pickers. Educated editors create fewer issues than permissive ones.
- Annual third-party audit. One outside audit a year keeps the team honest and produces the kind of documentation procurement teams ask for.
Need a WCAG 2.2 AA audit or remediation?
Tell us your domain and the kind of site (brochure, SaaS, e-commerce). We'll send a one-page audit summary, an issue-priority list, and a fixed price for remediation — within three working days.
Book a consultation →Frequently asked questions
Is WCAG 2.2 AA legally required in Canada?
Yes for many organizations. AODA covers Ontario public-sector organizations and businesses with 50+ employees. AccessibleBC covers BC public-sector organizations through 2026–2028 phased compliance. The Accessible Canada Act covers federally-regulated entities — banks, telecoms, federal agencies. Even where it's not statutorily required, most enterprise and public-sector RFPs in 2026 list WCAG 2.2 AA as a vendor selection criterion.
What changed in WCAG 2.2 vs 2.1?
WCAG 2.2 added 9 new success criteria, 6 at Level AA. The most relevant for most sites: Focus Not Obscured (sticky nav can't hide focused elements), Dragging Movements (drag interactions need pointer alternatives), Target Size (24×24 px minimum click targets), Consistent Help (help in the same place across pages), Redundant Entry (don't re-ask for info you have), and Accessible Authentication (no memory-based login challenges).
How much does WCAG 2.2 AA compliance cost for a Canadian SMB site?
A brochure site costs CA$3,500–CA$8,500 to audit and remediate; a marketing site with blog runs CA$6,000–CA$14,000; SaaS marketing-plus-app runs CA$15,000–CA$40,000; e-commerce CA$8,000–CA$25,000. Building accessibility in from the start of a new project adds 8–15% to a fixed-price build. Bolting it on after launch costs 2–4× as much.
Do accessibility overlay tools like accessiBe make my site WCAG compliant?
No. Overlay tools (accessiBe, EqualWeb, UserWay) often fail accessibility testing on the very sites that install them and have been subjects of multiple US accessibility lawsuits. They can't fix structural issues like heading hierarchy, semantic markup, or focus management — exactly the issues most sites fail. Real remediation, not overlays, produces conforming sites.
How long does WCAG 2.2 AA remediation take?
For a typical Canadian SMB marketing site, plan on 2–4 weeks: 1–2 days automated audit, 3–5 days manual audit, 1–3 weeks remediation work, then ongoing process changes. SaaS apps with complex UI take 5–10 weeks. The single biggest factor in timeline is whether issues live in the component library (fixable once) or scattered across hand-written pages (fixable many times).
What's the difference between WCAG A, AA, and AAA?
Level A is the minimum baseline (visible content can be read by assistive tech). Level AA — the practical legal standard in Canada and the EU — covers most real accessibility needs (contrast, captions, keyboard navigation, error identification). Level AAA is aspirational and rarely required (sign-language interpretation for video, 7:1 colour contrast, no flashing content). Target Level AA; achieve specific AAA criteria where they matter for your audience.
