By Cody Wise, Founder, Wise Media. Published 18 August 2026. This article is general information about Canadian accessibility law, not legal advice. Verify your own obligations with qualified counsel.
Probably not by statute, if you are an ordinary Alberta business. Canada has no single law that forces every commercial website to meet a technical accessibility standard. Federal accessibility duties under the Accessible Canada Act reach only federally regulated organizations. Ontario and Manitoba bind private employers above an employee threshold. Alberta has no enacted private-sector accessibility statute at all. Human rights law, however, reaches everyone.
Summary
- There is no universal Canadian web accessibility statute. Obligations depend on whether you are federally regulated, which province you operate in, and how many people you employ.
- The Accessible Canada Act (ACA) applies to federally regulated entities only, such as banks, airlines, railways, interprovincial trucking, telecoms and broadcasters, plus the federal public sector.
- The maximum administrative monetary penalty under the ACA is $250,000 CAD per violation, and a violation continued on more than one day counts as a separate violation for each day.
- Ontario is the strictest jurisdiction for private business. Businesses and non-profits with 50 or more employees must meet WCAG 2.0 Level AA on public websites, and those with 20 or more employees must file an accessibility compliance report by 31 December 2026.
- Alberta has no enacted accessibility legislation. Alberta and Prince Edward Island are the two remaining provinces without one. A private member’s bill, Bill 206, the Accessible Alberta Act, has been introduced but not passed.
- Alberta exposure runs through two other channels: the ACA if you happen to be federally regulated, and the human rights duty to accommodate, which has no employee threshold.
- WCAG 2.2 has been the current W3C Recommendation since October 2023. Most Canadian regulations still name WCAG 2.0 Level AA, which creates a gap between what the law cites and what the standards body advises.
- 27% of Canadians aged 15 and over, about 8.0 million people, reported a disability in 2022, up from 22% in 2017. The commercial case does not depend on the legal one.
Table of contents
- Does Canadian accessibility law bind my website?
- What the Accessible Canada Act actually requires
- Where Alberta stands in 2026
- Which WCAG version applies to you
- What a real accessibility audit involves
- Where accessibility and SEO overlap
- Common mistakes
- Frequently asked questions
- The bottom line
Does Canadian Accessibility Law Bind My Website?
Work through this table before you spend a dollar on remediation. Most Canadian businesses that panic about accessibility law are not bound by the statute they are panicking about, and most that assume they are clear have missed the human rights channel entirely.
| If you are… | Statutory web obligation | Standard named |
|---|---|---|
| A federally regulated private business (bank, airline, railway, interprovincial trucking, telecom, broadcaster) | Yes. Accessibility plan, feedback process and progress reports under the ACA and its regulations | ACA does not name a WCAG version directly; sector regulators and procurement standards commonly reference WCAG 2.0 AA or later |
| An Ontario business or non-profit with 50+ employees | Yes. Public websites and web content must conform under the AODA Information and Communications Standard | WCAG 2.0 Level AA, with limited exceptions for live captions and pre-recorded audio description |
| An Ontario business or non-profit with 20+ employees | Yes, for reporting. Accessibility compliance report due 31 December 2026, then every three years | Reporting obligation, not itself a technical standard |
| A Manitoba organization | Yes. Accessible Information and Communications Standard obligations phased in from 1 May 2025 | WCAG 2.0 Level AA as the benchmark |
| A British Columbia private business | No. The Accessible British Columbia Act currently reaches government and prescribed public sector organizations | Not applicable to private business yet |
| A Nova Scotia, Saskatchewan, New Brunswick or Newfoundland and Labrador business | Framework legislation exists. Specific web obligations depend on which standards have been enacted in your province | Check the current enacted standards, not the enabling Act |
| An Alberta or Prince Edward Island business, not federally regulated | No accessibility statute applies to your website | None. Human rights duty to accommodate still applies |
Two things this table does not let you off the hook for. First, if you sell into Ontario or Manitoba but employ people there, the provincial thresholds count your employees in that province. Second, and much more commonly missed, human rights legislation contains no employee threshold and no safe harbour. A customer who cannot use your booking form to access a service you offer the public has a potential human rights complaint regardless of which province you are in and how few people you employ.
What the Accessible Canada Act Actually Requires
The ACA received royal assent in 2019. Its stated purpose is the realization of a Canada without barriers on or before 1 January 2040. It is a planning and reporting regime, not a technical web specification: it obliges regulated entities to publish accessibility plans, run a feedback process, and report on progress, in seven priority areas including information and communication technologies.
Who counts as a regulated entity?
Section 7 of the Act sets the scope. In practice it covers Government of Canada departments and agencies, Crown corporations, the Canadian Forces, parliamentary entities, and federally regulated private sector entities. That last category is narrower than most business owners assume. It is the federal works and undertakings list: banking, interprovincial and international transportation, telecommunications, broadcasting, grain elevators, uranium mining, and a handful of others.
A Calgary roofing company, a Canmore property manager, a Saskatoon dental clinic and a Vancouver e-commerce brand are not federally regulated. A credit union, a regional airline and a rural telephone cooperative are.
The real deadlines, which are not what you have been told
A lot of agency content circulating in 2026 attaches a 31 December 2026 accessibility deadline to the ACA. That date belongs to Ontario’s AODA reporting cycle, not to the federal regime. The federal deadlines set by the Accessible Canada Regulations are staggered by function and size:
| Entity type | First accessibility plan due |
|---|---|
| Government entities, including departments, agencies, Crown corporations, the Canadian Forces and parliamentary entities | 31 December 2022 |
| Large federally regulated private sector entities, average of 100 or more employees | 1 June 2023 |
| Small federally regulated private sector entities, average of 10 to 99 employees | 1 June 2024 |
After the first plan, the cycle is continuous rather than a single cliff edge. Plans are updated every three years, and progress reports are published in the intervening years. For federally regulated private sector entities the recurring publication date is 1 June, which means the meaningful 2026 date for that group was 1 June 2026, not the end of the year. Sections 1 to 3 of the regulations set out which entities are exempt, and very small entities under the ten-employee threshold are treated differently.
What the penalties actually are
The $250,000 figure quoted everywhere is real, and it comes from subsection 91(2) of the Act: the maximum penalty that may be fixed by regulation in respect of a violation is $250,000. What almost nobody quoting it mentions is the three provisions that surround it, which matter far more to how exposure actually accumulates.
- Section 88, continuing violations. A violation committed or continued on more than one day constitutes a separate violation for each day. A structural problem left unfixed does not attract one penalty, it attracts a daily one.
- Section 85, defences unavailable. A regulated entity named in a notice of violation cannot defend itself on the basis that it exercised due diligence, or that it honestly and reasonably believed facts that would have exonerated it. Good intentions are not a defence.
- Section 86, personal liability. Officers, directors, agents and senior officials who directed, authorized, assented to, acquiesced in or participated in a violation are personally parties to it and liable, whether or not the organization itself is proceeded against.
Against that, two provisions cut the other way. Section 90 imposes a two-year limitation period on commencing proceedings in respect of a violation. And the penalty range is graduated, not fixed: the regulations classify each violation as minor, serious or very serious, and the $250,000 ceiling sits at the top of the very serious band for large entities. The realistic exposure for a first minor administrative failure by a small entity is a long way below the headline number.
Separately from penalties, Part 6 of the Act gives individuals a complaint route. Where a complaint is substantiated, the Accessibility Commissioner can order corrective measures and compensation, including an amount for pain and suffering and a further amount where the contravention resulted from a wilful or reckless practice. Each of those amounts was set at $20,000 for the year the provision came into force and is indexed annually to the Consumer Price Index, so the current figure is higher.
Where Alberta Stands in 2026
Alberta has no enacted accessibility legislation. Alberta and Prince Edward Island are the last two provinces without one, after Saskatchewan and New Brunswick both adopted accessibility statutes in 2023.
That is not the same as nothing happening. The Office of the Advocate for Persons with Disabilities published Accessible Alberta: Recommendations for Provincial Accessibility Legislation, which recommended a framework phasing obligations from the public sector into the private sector over a five to ten year period. In 2026, Bill 206, the Accessible Alberta Act, was introduced as a private member’s bill by St. Albert MLA Marie Renaud, proposing a committee to consult on and recommend standards across employment, government services, transportation, housing, health and education. The government has raised objections, with the Minister of Assisted Living and Social Services citing insufficient consultation with business and concern about concentrating accessibility policy in an unelected committee.
Private members’ bills rarely pass. Treat Bill 206 as a signal about direction, not a compliance deadline. The practical planning assumption for an Alberta business is that no provincial web accessibility standard binds you today, and that if one arrives it will phase in over years and will almost certainly land on a WCAG conformance level rather than inventing a new standard.
The exposure Alberta businesses actually have
Two channels, and only one of them is the one people worry about.
- The ACA, if you are federally regulated. Being headquartered in Alberta does not exempt a federally regulated entity. An Alberta credit union or an Alberta-based interprovincial carrier is inside the federal regime.
- Human rights duty to accommodate. This is the one that reaches ordinary Alberta businesses. Provincial human rights legislation prohibits discrimination in the provision of goods, services and facilities customarily available to the public. A website that is the only practical route to a service, and that a person using assistive technology cannot operate, is a service delivery problem with a human rights dimension. There is no employee threshold, no phase-in and no compliance report to file, which is precisely why it gets overlooked.
The practical implication is that a small Alberta business is not facing a $250,000 statutory penalty risk on its website. It is facing a complaint risk plus a commercial one, and the commercial one is larger.
Which WCAG Version Applies to You?
Short answer: build to WCAG 2.2 Level AA, and if a regulation names an older version you have satisfied it anyway. The versions are backward compatible, so meeting 2.2 means meeting 2.1 and 2.0.
This is where competitor content creates confusion it then fails to resolve. Two separate things are true at once, and conflating them is what produces the muddle:
| Version | Status | What it adds |
|---|---|---|
| WCAG 2.0 | Still a W3C Recommendation. The version most Canadian regulations name by reference, including Ontario’s AODA | The original baseline, published 2008 |
| WCAG 2.1 | Still a W3C Recommendation | 17 additional success criteria over 2.0, with an emphasis on mobile, low vision and cognitive accessibility |
| WCAG 2.2 | W3C Recommendation since October 2023. The current version, and the one W3C advises using | 9 further success criteria, six of them at Level A or AA, and removes the old 4.1.1 Parsing criterion |
So the legal floor in Ontario is 2.0 AA, while the standards body’s advice is 2.2. Building to the floor is a decision to redo the work when the reference updates. Building to 2.2 AA costs marginally more on a new build and settles the question for years, which is why it is the default we specify on every website build rather than an upsell.
What Does a Real Accessibility Audit Involve?
An automated scan plus manual testing with a keyboard and a screen reader. Automated tooling alone catches roughly a third of real conformance issues and produces false confidence on the rest, because most of what breaks accessibility is judgment: whether alt text is meaningful, whether a heading structure reflects the actual document outline, whether a focus order matches visual order, whether an error message explains how to fix the error.
The audit sequence we run
- Automated scan across templates, not pages. Scan one instance of each template, since a 400 page site usually has eight templates and the same eight defects repeated.
- Keyboard-only pass. Unplug the mouse. Tab through every interactive element on every template. You are looking for focus that disappears, focus order that jumps, dropdowns and modals that trap focus, and skip links that do not exist.
- Screen reader pass. NVDA or VoiceOver through the primary conversion path: navigation, a form, a checkout or booking step, an error state.
- Contrast and zoom. Check text contrast ratios against the 4.5:1 requirement for body copy, then reflow the page at 400% zoom and at 320 CSS pixels wide to confirm nothing is lost or requires two-dimensional scrolling.
- Forms and error handling. Every input programmatically associated with a visible label, errors identified in text rather than colour alone, and instructions available before submission.
- Media. Captions on pre-recorded video, transcripts, and no autoplaying audio.
- Document the remaining gaps. A conformance statement that honestly lists known exceptions is worth more than a claim of full conformance that a single tab press disproves.
On overlay widgets
Overlay and toolbar products, the ones that add a floating accessibility icon and a panel of contrast and font-size toggles, are not a compliance strategy on their own. They sit on top of the markup rather than fixing it, they cannot repair a broken heading structure or an unlabelled form field, and they frequently interfere with the assistive technology a user has already configured. They also do not remove human rights exposure, because the underlying barrier is still there.
They have a narrow legitimate use as a stopgap while real remediation is scheduled. Sold as a substitute for remediation, they are the accessibility equivalent of a cookie banner: visible compliance theatre that changes nothing structural.
Where Accessibility and SEO Overlap
Substantially, and this is the argument that actually gets accessibility work approved. A screen reader and a crawler both consume your page as structured text without seeing the design. Work that helps one tends to help the other.
| Accessibility requirement | Search benefit |
|---|---|
| Logical single-H1 heading hierarchy | Clearer topical structure for indexing and for passage-level extraction into AI answers |
| Descriptive alt text on meaningful images | Image search eligibility and additional relevance signal |
| Descriptive link text instead of “click here” | Anchor text that tells crawlers what the destination is about |
| Captions and transcripts on video | Indexable text where there was none, plus longer dwell time |
| Semantic HTML landmarks over generic containers | Easier main-content identification and cleaner extraction |
| Text alternatives for content locked in images | Content that can be indexed and cited at all |
| Reflow and touch target sizing | Mobile usability signals |
The overlap is not total. Contrast ratios and focus indicators do nothing for rankings, and a perfectly accessible page can still be invisible in search if nothing links to it. But the structural half of an accessibility remediation is close to identical to the structural half of a technical SEO fix, which is why we scope them together in growth engagements rather than billing them as separate projects. If you want the search side of that in more depth, our guide to schema markup for Canadian local businesses and the walkthrough on pages that are indexed but not ranking both cover ground that sits next to this.
Common Mistakes
- Assuming the ACA applies because you are Canadian. It applies because you are federally regulated. Most businesses are not.
- Attaching Ontario’s 31 December 2026 reporting deadline to the federal regime. Different statute, different regulator, different cycle.
- Reading the $250,000 ceiling as the expected penalty. It is the top of the very serious band for large entities, and the range starts several orders of magnitude lower.
- Concluding that no statute means no exposure. The human rights duty to accommodate has no employee threshold and is the live risk for most Alberta businesses.
- Installing an overlay widget and calling it compliance. It does not fix the markup, and the barrier persists.
- Auditing pages instead of templates. You will pay to rediscover the same eight defects several hundred times.
- Building to WCAG 2.0 because that is what the regulation names. 2.2 is backward compatible, so you may as well satisfy both.
- Treating accessibility as a launch task. Every subsequent content edit can reintroduce a barrier. It belongs in the publishing checklist, not the launch checklist.
- Claiming full conformance you cannot support. An honest conformance statement listing known exceptions is defensible. An unsupported claim is a liability you wrote yourself.
Frequently Asked Questions
Is my website legally required to be accessible in Canada?
It depends on three things: whether your organization is federally regulated, which province you operate in, and how many employees you have. Federally regulated entities have obligations under the Accessible Canada Act. Ontario businesses with 50 or more employees must meet WCAG 2.0 Level AA on public websites. Manitoba has phased information and communications obligations. Alberta and Prince Edward Island have no accessibility statute. Human rights law applies everywhere regardless.
Does the Accessible Canada Act apply to small businesses?
Only if the small business is federally regulated. Within the federal regime, entities with an average of 10 to 99 employees were required to publish a first accessibility plan by 1 June 2024, and entities below the ten-employee threshold are treated differently under sections 1 to 3 of the Accessible Canada Regulations. A small business that is not federally regulated is outside the Act entirely.
What is the penalty for an inaccessible website in Canada?
Under the ACA, subsection 91(2) caps administrative monetary penalties at $250,000 CAD per violation, with the actual amount set by regulation according to whether the violation is minor, serious or very serious, the size of the entity, and prior history. Section 88 treats each day a violation continues as a separate violation. Ontario’s AODA carries its own published maximum penalties, which are higher on a per-day basis for corporations, so confirm the current figures with the Ontario regulator if you operate there. There is no penalty regime at all in provinces without accessibility legislation, though human rights remedies remain available.
Which WCAG version should I build to in 2026?
WCAG 2.2 Level AA. It has been the W3C Recommendation since October 2023 and is fully backward compatible, so conforming to 2.2 also satisfies regulations that name 2.1 or 2.0. W3C explicitly advises using 2.2 to maximize the future applicability of accessibility work.
Do accessibility overlay tools make my site compliant?
No. Overlays layer controls on top of existing markup and cannot repair a broken heading structure, an unlabelled form input, a keyboard trap or a missing text alternative. They can also conflict with assistive technology the user has already configured. They are a temporary mitigation at best, not a substitute for remediating the underlying code.
Does Alberta have accessibility legislation?
Not as of August 2026. Alberta and Prince Edward Island are the two provinces without accessibility legislation. Bill 206, the Accessible Alberta Act, was introduced in 2026 as a private member’s bill and has not been passed. Alberta businesses that are not federally regulated have no statutory web accessibility standard, but remain subject to the human rights duty to accommodate.
The Bottom Line
If you are an ordinary Alberta business, no statute currently dictates a technical accessibility standard for your website, and anyone selling you remediation on the threat of a $250,000 federal penalty is describing a regime you are not in. What is true is that roughly one in four Canadians reports a disability, that the human rights duty to accommodate has no threshold, that the structural work overlaps heavily with technical SEO, and that the regulatory direction across every other province is one way.
That combination makes WCAG 2.2 AA a sensible build standard rather than a compliance scramble. It is cheapest at build time, it is defensible if the law changes, and it earns its keep in search and conversion in the meantime.
If you want to know where your current site actually stands, we run template-level audits with keyboard and screen reader passes, then scope remediation against the findings rather than against a generic checklist. Tell us about your site through the Wise Media intake form, or look at how we scope accessible builds inside our website packages.
Sources
- Accessible Canada Act, S.C. 2019, c. 10, Justice Laws Website, including sections 85 to 91
- Guidance on the Accessible Canada Regulations: progress reports, Employment and Social Development Canada
- Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation
- A demographic, employment and income profile of persons with disabilities aged 15 years and over in Canada, 2022, Statistics Canada
- Completing your accessibility compliance report, Government of Ontario
- Accessible Alberta: Recommendations for Provincial Accessibility Legislation, Office of the Advocate for Persons with Disabilities