Website accessibility compliance in Canada means your public website meets WCAG 2.0 Level AA. In Ontario, the AODA requires it for private organizations with 50 or more employees and for all public sector organizations. Federally regulated businesses fall under the Accessible Canada Act instead. The next Ontario accessibility compliance report is due December 31, 2026, and penalties reach six figures per day.
Summary
- The standard is WCAG 2.0 Level AA, not 2.1 and not 2.2, though Ontario has signalled a move to WCAG 2.2 around 2027.
- Ontario’s next compliance report deadline is December 31, 2026 for organizations with 20 or more employees and for all public sector organizations. Filing happens through the Accessibility Compliance Reporting portal on ontario.ca.
- Maximum penalties are steep. Published provincial figures reach up to $100,000 per day for corporations and up to $50,000 per day for directors and officers. Enforcement in practice is complaint driven and audit driven, not automatic.
- Most Canadian small business sites fail on four things: colour contrast, missing alt text, keyboard traps, and unlabelled forms. Those four account for the bulk of automated-scan errors on a typical WordPress site.
- Budget realistically. An audit plus remediation on a standard 15 to 30 page brochure site is usually a low four-figure project. A large ecommerce or booking site is a different order of magnitude.
- Overlay widgets do not make you compliant. They are a supplement at best and have been the subject of litigation in the United States. Fix the code.
Table of Contents
- What does website accessibility compliance actually require in Canada?
- Who has to file by December 31, 2026?
- What does WCAG 2.0 Level AA mean on a real website?
- How do you audit your own site in an afternoon?
- What does it cost to fix a website in Canada?
- Do accessibility overlay widgets work?
- Common mistakes
- Frequently asked questions
- The bottom line
What does website accessibility compliance actually require in Canada?
It requires your website and web content to conform to WCAG 2.0 Level AA. Which law makes that a legal obligation depends on where you operate and how you are regulated. Canada does not have one single national website accessibility law. It has a federal statute for federally regulated entities and a patchwork of provincial statutes on top.
AODA (Ontario)
The Accessibility for Ontarians with Disabilities Act is the one most Canadian businesses run into first, because Ontario is the largest market and the AODA has been enforced the longest. Its Information and Communications Standard is the part that touches your website.
The requirement: private and non-profit organizations with 50 or more employees, and all public sector organizations, must make their internet websites and web content conform to WCAG 2.0 Level AA. Live captions and pre-recorded audio descriptions are carved out of the requirement. Organizations under 50 employees have lighter obligations under the standard but are not exempt from the rest of the AODA, including accessible formats on request.
One detail that trips people up: the obligation attaches to new content and to significant refreshes. If you rebuilt your site last year, that build was in scope. A website redesign is the cheapest possible moment to become compliant, which is why we fold accessibility into every website redesign and migration rather than treating it as a separate line item afterward.
The Accessible Canada Act
The Accessible Canada Act, in force since 2019, applies to federally regulated entities: banks, telecoms, broadcasters, airlines, interprovincial rail and trucking, Crown corporations, and the federal public service. If that is you, the ACA is your governing statute and it comes with its own accessibility plan, feedback process, and progress report obligations on a published schedule.
If you are a Calgary contractor, an Ontario clinic, or a BC agency, the ACA almost certainly does not apply to you. Provincial law does.
The rest of the provinces
| Jurisdiction | Statute | Where website obligations stand |
|---|---|---|
| Ontario | AODA (2005) | Mature. WCAG 2.0 AA required, reporting portal active, next report due Dec 31, 2026. |
| Federal | Accessible Canada Act (2019) | Applies to federally regulated entities. Plans and progress reports required. |
| Manitoba | Accessibility for Manitobans Act (2013) | Information and Communications Standard phased in, with website obligations following. |
| Nova Scotia | Accessibility Act (2017) | Standards being developed toward a stated goal of an accessible province by 2030. |
| British Columbia | Accessible British Columbia Act (2021) | Public sector first. Private sector standards still developing. |
| Saskatchewan | Accessible Saskatchewan Act (2023) | Early stage. Standards under development. |
| Alberta | No dedicated provincial accessibility statute | Human rights law and federal rules still apply. Many Alberta businesses meet WCAG because clients demand it. |
The practical read for a business operating in more than one province: build to WCAG 2.0 Level AA once and you satisfy the strictest current Canadian requirement everywhere. Building to a lower standard and then patching province by province costs more.
Who has to file by December 31, 2026?
In Ontario, businesses and non-profits with 20 or more employees and all public sector organizations must file an accessibility compliance report by December 31, 2026. The report is filed online through the Accessibility Compliance Reporting portal linked from ontario.ca. It is a self-declaration: you are confirming that you meet the applicable standards.
That self-declaration is the part worth pausing on. If you have 50 or more employees, the form asks you to confirm that your website conforms to WCAG 2.0 Level AA and that you have a documented multi-year accessibility plan. Ticking that box on a site that fails an automated scan on the homepage is a knowingly false declaration, which is a materially worse position than simply being behind.
- Under 20 employees in Ontario: no report required, but the underlying accessibility obligations still apply.
- 20 to 49 employees: report required. Full WCAG conformance for the website is not the trigger at this size, but accessible formats on request and other obligations are.
- 50 or more employees: report required, and the website must conform to WCAG 2.0 Level AA, and a multi-year accessibility plan must be published and reviewed.
On penalties: Ontario’s published maximums run up to $100,000 per day for a corporation and up to $50,000 per day for a director or officer. Those are ceilings under the administrative penalty framework, not typical outcomes. Real world enforcement has been driven by complaints, targeted audits, and non-filing. The more common commercial consequence in 2026 is losing an RFP, because public sector and enterprise procurement in Canada now routinely asks for an accessibility conformance statement.
What does WCAG 2.0 Level AA mean on a real website?
Stripped of the specification language, Level AA on a typical business site comes down to roughly a dozen things a developer has to get right. Here is the working checklist we run on client sites.
- Colour contrast. Normal text needs a contrast ratio of at least 4.5:1 against its background. Large text, meaning 18.66px bold or 24px regular and above, needs 3:1. Light grey body copy on white is the single most common failure in premium-looking design.
- Text alternatives. Every meaningful image needs alt text that conveys its purpose. Decorative images need an empty alt attribute so screen readers skip them, not a filename.
- Keyboard operability. Every interactive element must be reachable and usable with Tab, Enter, and Space, with no keyboard trap. Custom dropdowns, sliders, and modals are where this breaks.
- Visible focus indicator. The user must be able to see where they are. Removing the focus outline in CSS without replacing it is an instant failure and it is extremely common on designer-built themes.
- Form labels. Every input needs a programmatically associated label. Placeholder text is not a label.
- Error identification. Form errors must be described in text, not signalled only by turning a border red.
- Heading structure. One H1, then a logical H2 and H3 hierarchy with no skipped levels. This overlaps directly with SEO structure, which is why an accessibility pass and a technical SEO audit are efficient to run together.
- Link purpose. Link text must make sense out of context. “Read more” repeated fourteen times fails.
- Page language. The html element needs a lang attribute, and a French page needs lang=”fr”.
- Resize and reflow. Content must remain usable at 200% zoom without horizontal scrolling.
- Video captions. Pre-recorded video needs captions. Under the AODA carve-out, live captions and pre-recorded audio description are not required.
- No mouse-only interactions. Anything you can do with a hover, you must be able to do another way.
How do you audit your own site in an afternoon?
You can find the majority of your problems yourself in about three hours, with free tools, before you pay anyone. Automated scanning catches roughly a third of WCAG issues, so this is triage rather than certification, but it tells you the size of the problem.
- Run an automated scan on five representative pages. Homepage, a service page, a blog post, your contact form, and your checkout or booking flow. Use WAVE from WebAIM, or the axe DevTools browser extension, or Lighthouse in Chrome DevTools. Do not scan only the homepage. The homepage is usually the best page on the site.
- Log every error and its count. Errors, not warnings, first. You are looking for patterns, because on a templated site one error usually repeats across a hundred pages and has one fix.
- Do the keyboard test. Put the mouse down. Tab from the top of the page to the bottom. Can you reach the navigation, open the menu on mobile width, fill the form, and submit it? Can you always see where you are? Can you get out of the cookie banner and the popup?
- Check contrast on your brand colours. Run your actual hex values through a contrast checker. Most brand palettes have one accent colour that fails on white. Fix it at the design token level, not page by page.
- Test one page with a screen reader. VoiceOver is built into macOS with Cmd + F5. NVDA is free on Windows. Listen to your homepage for two minutes. It is uncomfortable and it is the single most informative thing on this list.
- Turn off images and check the alt text. The page should still communicate what it is about.
- Write it down. A one-page findings list with counts and page examples is what turns a vague worry into a scoped quote.
What this process cannot tell you: whether your reading order makes sense, whether your alt text is actually useful, or whether a custom component is announced correctly. That is manual expert testing and it is the part you pay for.
What does it cost to fix a website in Canada?
Cost tracks two things: how many unique templates your site has, and how much custom JavaScript is in the interactive parts. Page count matters far less than people expect, because a fix to a header template propagates everywhere.
| Scope | Typical Canadian planning range (CAD) | What it covers |
|---|---|---|
| Automated scan and findings summary | $500 to $1,500 | Tool-based scan across key templates, prioritized issue list, no code changes. |
| Manual WCAG 2.0 AA audit, brochure site | $2,500 to $6,000 | Expert review, screen reader testing, keyboard testing, remediation roadmap. |
| Remediation, standard WordPress brochure site | $2,000 to $6,000 | Contrast, alt text, focus states, form labels, heading structure, menu and modal fixes. |
| Remediation, ecommerce or booking flow | $6,000 to $20,000+ | Cart, checkout, filters, date pickers, and third-party widgets. The date picker is usually the worst offender. |
| Accessible rebuild instead of remediation | Cost of a new site build | Often cheaper than remediating a page builder site loaded with nested divs and inline styles. |
| Ongoing monitoring and content QA | $150 to $600 per month | Scheduled scans, new-content checks, plugin and theme update regression testing. |
The uncomfortable finding on older sites: remediation sometimes costs more than replacement. If your site is a heavily nested page builder layout with inline styles on every element and a theme that has not been updated in three years, you are paying a developer to fight the tool. At that point the honest recommendation is a rebuild, which is how we scope most of our website packages: accessible markup, semantic structure, and real focus states from the first commit rather than bolted on at the end. For context on what a full build costs in this market, see our 2026 website cost guide for Canada.
There is also a performance overlap worth naming. Semantic HTML with fewer wrapper elements is both more accessible and faster, which is why accessibility work usually improves the numbers discussed in our guide to website speed optimization. You are not buying two things.
Do accessibility overlay widgets work?
Short answer: not as a compliance strategy. An overlay is a JavaScript snippet that injects a floating accessibility toolbar and attempts to patch problems at runtime. Vendors market them as one-line compliance. The disability advocacy community has been near-unanimous in rejecting them, thousands of accessibility practitioners have signed public statements against them, and in the United States overlay-equipped sites have still been the subject of accessibility lawsuits.
The reasons are mechanical rather than ideological. An overlay cannot know that your image of a chart shows quarterly revenue. It cannot restructure your headings meaningfully. It sometimes interferes with the assistive technology the user already has configured, which makes the experience worse for the exact person it claims to help. And it does nothing for a compliance report, because the underlying code still fails.
Where they have a narrow legitimate use: as a temporary stopgap while real remediation is in progress, or as a preferences panel offering font size and contrast toggles on a site that is already conformant. Buying one instead of fixing your code is buying a receipt, not a solution.
Common mistakes
- Treating it as a one-time project. Every blog post published without alt text reopens the gap. Accessibility is a content workflow issue as much as a code issue.
- Auditing the homepage only. The homepage is hand-built and polished. Your conversion pages, forms, and booking flow are where the failures live and where the legal exposure is highest.
- Removing focus outlines for aesthetics. Designers do this constantly. If you dislike the default outline, design a better one. Do not delete it.
- Assuming your page builder handles it. Elementor, Divi, and Webflow can all produce conformant output and all readily produce non-conformant output. The tool does not decide, the build does.
- Using colour as the only signal. Red borders for errors, green for success, coloured-only chart legends. Add text or icons.
- Auto-playing video or carousels with no pause control. Moving content that runs longer than five seconds needs a way to stop it.
- Filing the compliance report without checking the site. A false self-declaration is worse than a late one.
- Buying an overlay and ticking the box. Covered above. It does not hold up.
Frequently asked questions
Does the AODA apply to my business if I am based in Alberta but sell to Ontario?
The AODA applies to organizations that provide goods, services, or facilities in Ontario and have at least one employee in Ontario. Selling to Ontario customers from an Alberta base without any Ontario presence generally puts you outside the AODA’s scope, but this is a legal question with real nuance and it is worth a short conversation with a lawyer rather than a blog post. Regardless of the answer, WCAG 2.0 AA is what enterprise and public sector buyers in Ontario will ask you to attest to, so the commercial pressure often arrives before the legal one.
Is WCAG 2.1 or 2.2 required in Canada yet?
Not for AODA compliance today. The Ontario requirement is WCAG 2.0 Level AA, and Ontario has signalled an intended move toward WCAG 2.2 around 2027. Building to 2.1 AA now is the sensible hedge: it is a superset of 2.0 AA, it adds mobile and low-vision criteria that matter in practice, and it means the next standards change is a small delta instead of another project.
How long does remediation take on a typical small business site?
For a 15 to 30 page WordPress site with no ecommerce, expect two to four weeks from audit to retest. Roughly one week for the audit and findings, one to two weeks of development, and a few days for verification. Sites with custom booking flows, filtered listings, or third-party embedded widgets take longer because the third-party components often have to be replaced rather than fixed.
Can I be held personally liable over an inaccessible website in Canada?
Ontario’s administrative penalty framework contemplates penalties against directors and officers, with published maximums up to $50,000 per day, separate from corporate penalties. There is also human rights complaint exposure at both the provincial and federal level, which is a distinct process from AODA enforcement. None of this is legal advice, and Wise Media is not a law firm. If you are weighing real exposure, talk to counsel.
Does accessibility actually help SEO?
Indirectly and meaningfully. Proper heading hierarchy, descriptive link text, image alt attributes, language attributes, and semantic landmarks are all things crawlers and AI answer engines parse. Accessibility work does not have a ranking factor attached to it, but it produces cleaner, more machine-readable markup, and that is exactly what gets extracted into featured snippets and AI answers. The overlap with a technical SEO checklist is substantial.
The bottom line
If you have 50 or more employees in Ontario, WCAG 2.0 Level AA is a legal requirement and you are attesting to it in December. If you are smaller or in another province, it is a commercial requirement that arrives the first time you bid on public sector work or a serious enterprise contract. Either way the work is the same, the cost is knowable, and it gets cheaper the earlier in a build it happens.
The move is not to panic-buy an overlay in November. It is to run the three-hour self-audit this week, find out whether you have a fifteen-hour problem or a fifty-hour problem, and scope it properly.
Get your site audited and fixed properly
Wise Media builds accessible, fast, semantic websites from the first line of code, and we remediate existing ones. If you want a WCAG 2.0 AA audit with a prioritized fix list, or a rebuild that clears the bar without a retrofit, look at our website packages and our website growth packages, then tell us about your site through the intake form and we will come back with a scoped quote.