Is My Website Legally Required to Be Accessible? A 2026 Guide for Canadian and Alberta Businesses

Probably not, and almost every page telling you otherwise is wrong. The Accessible Canada Act binds federally regulated organizations only: banks, telecoms, broadcasters, airlines, railways and the federal public service. If you run an Alberta contracting firm, a dental clinic, a Calgary short term rental or a marketing agency, no Canadian statute currently requires your website to meet WCAG. Your real exposure is human rights law, provincial rules if you operate in Ontario or Manitoba, and a federal deadline landing in 2027.

By Cody Wise, Founder, Wise Media. Published 24 September 2026. This article is general information, not legal advice. Accessibility obligations turn on facts specific to your business. Verify your position with counsel before relying on any of it.

Summary

• The Accessible Canada Act does not apply to provincially regulated businesses. That is the large majority of Canadian companies.
• Ontario and Manitoba are the two provinces with enforceable private sector web accessibility duties. Ontario binds WCAG 2.0 Level AA at 50 or more employees. Manitoba binds WCAG 2.1 Level AA at one or more employees.
• Alberta has no accessibility statute. Bill 206, the Accessible Alberta Act, was defeated on division at second reading on 23 March 2026.
• A new federal regulation changes the federal picture in 2027 and 2028. SOR/2025-255 adds digital accessibility duties and binds CAN/ASC-EN 301 549, not a WCAG version number.
• Human rights law applies everywhere, including Alberta, where no accessibility statute exists.
• 27% of Canadians aged 15 and over report a disability. That is 8.0 million people, and it is the commercial argument that survives the legal one.

Table of contents

1. Does Canadian accessibility law bind your website?
2. What the Accessible Canada Act actually requires
3. The federal rule change landing in 2027 and 2028
4. Which WCAG version applies to you?
5. Alberta: no statute, real exposure
6. What an accessibility audit actually involves
7. The accessibility and SEO overlap
8. Common mistakes
9. FAQ

Does Canadian accessibility law bind your website?

Accessibility in Canada is split across federal and provincial jurisdictions, and the split is the entire answer. There is no single Canadian web accessibility law. There are several, each binding a different set of organizations, each pointing at a different technical standard.

Find your row.

Your situation	Bound?	Standard
Federally regulated (bank, telecom, broadcaster, airline, railway, interprovincial trucking, federal public service, Crown corporation)	Yes	Accessibility plans and reports now. CAN/ASC-EN 301 549 for web from 2027 or 2028 depending on sector and size
Ontario business or non profit, 50 or more employees	Yes	WCAG 2.0 Level AA, since 1 January 2021
Ontario business, fewer than 50 employees	No web duty	Other AODA duties still apply
Manitoba organization with one or more employees	Yes	WCAG 2.1 Level AA, since 1 May 2025
British Columbia private business	No	Accessible BC binds roughly 750 public sector organizations only
Quebec private business	No	SGQRI 008 3.0 binds public bodies only
Nova Scotia private business	Not yet	Information and communication standard still in development
Alberta private business	No statute	Human rights duty to accommodate applies

Two things follow from that table that most Canadian agency pages get wrong.

First, Manitoba is stricter than Ontario, not looser. Ontario sets a 50 employee threshold. Manitoba sets none. A two person Winnipeg shop has a web accessibility duty that a 40 person Toronto shop does not.

Second, British Columbia and Quebec are public sector only. The Accessible British Columbia Act and Quebec standard SGQRI 008 3.0 get cited constantly in listicles as though they bind private business. They do not.

What the Accessible Canada Act actually requires

The Accessible Canada Act came into force in 2019 with the stated purpose of a barrier free Canada on or before 1 January 2040. Section 7(1) sets out who it binds, and the wording matters more than the summaries of it.

The Act reaches entities in Schedules I to V of the Financial Administration Act, Crown corporations, designated portions of the federal public administration, the Canadian Forces, and, in the language of paragraph 7(1)(e), any person or organization that “operates a work or carries on an undertaking or business that is within the legislative authority of Parliament.”

That last clause is what catches banks, telecoms, broadcasters, air and rail and marine transport, interprovincial trucking and First Nations band councils. They are not named in the statute. They fall inside it because they are federal works and undertakings. A provincially incorporated Alberta company selling to Albertans is not.

The reporting deadlines have already passed

If you are federally regulated, your accessibility plan deadline is behind you, not ahead of you. The Accessible Canada Regulations (SOR/2021-241) set these publication dates:

Entity	Initial plan due
Federal government entities	31 December 2022
Federally regulated private sector, 100 or more employees	1 June 2023
Federally regulated private sector, 10 to 99 employees	1 June 2024
Fewer than 10 employees	Exempt

Progress reports are due on the anniversary in each year without a plan, and an updated plan is due every 36 months. Note the private sector dates are all 1 June, deliberately aligned with Employment Equity Act reporting.

There is no 31 December 2026 ACA deadline. That date circulates widely on agency blogs. It was the end of the First Nations band council exemption, and it has since been extended to 31 December 2033.

About that $250,000 penalty

The figure is real and it is almost always quoted without the context that makes it meaningful. Section 91(2) of the Act reads: “The maximum penalty in respect of a violation that may be fixed under regulations made under paragraph (1)(b) is $250,000.” All figures in this article are CAD.

That ceiling is reachable only under Schedule 2 of the regulations, for a very serious, fourth or subsequent violation by a regulated entity that is not a small business. Here is the actual grid:

Category	Minor, first violation	Very serious, fourth or later
Person other than a regulated entity	$250 to $2,500	$37,500 to $62,500
Small business (under 100 employees)	$500 to $5,000	$75,000 to $125,000
Regulated entity, not a small business	$1,000 to $10,000	$150,000 to $250,000

Failing to publish a plan, a progress report or a feedback process is classified as a minor violation. “Very serious” is reserved for obstructing the Accessibility Commissioner or knowingly making false statements. A first missed accessibility plan by a federally regulated employer sits in the $1,000 to $10,000 band, not at $250,000.

One provision that does bite: section 88 states that a violation continued on more than one day constitutes a separate violation for each day.

The federal rule change landing in 2027 and 2028

This is the part almost nobody has written about, and it is the most consequential development in Canadian digital accessibility in years.

SOR/2025-255, registered 5 December 2025, amends the Accessible Canada Regulations to add Part 1.1, Information and Communication Technologies. It covers web pages, mobile applications and non web documents.

The binding standard is not WCAG. New section 19.1 defines the ICT Standard as “CAN/ASC-EN 301 549, Accessibility requirements for ICT products and services, published by Accessibility Standards Canada.” Web pages must conform, to the extent feasible, to clauses 4 to 7 and 9 of that standard.

WCAG appears only in the non binding regulatory impact statement, which says the ICT Standard “fully incorporates all requirements for Level AA conformance with the WCAG” without naming a version. So if a vendor tells you the new federal regulations require WCAG 2.1 AA, they are paraphrasing a preamble, not quoting the rule.

The dates

• 5 December 2027: federal public sector web pages, accessibility statements for web pages, and training for the public sector plus federally regulated private sector employers with 100 or more employees.
• 5 December 2028: federally regulated private sector with 100 or more employees, web pages. Private sector with 500 or more employees adds mobile apps, digital documents, accessibility statements and procurement conformity assessments. Public sector adds mobile apps and documents.
• Exempt: federally regulated private sector entities with 99 or fewer employees on a three year average are outside Part 1.1 entirely.

If you are a provincially regulated Canadian business, none of this touches you. If you supply federally regulated clients, it will reach you through their procurement conformity assessments well before 2028.

Which WCAG version applies to you?

Short answer: build to WCAG 2.2 Level AA and you satisfy every Canadian requirement currently in force, because no Canadian law mandates 2.2 yet.

The W3C published WCAG 2.0 in December 2008, WCAG 2.1 in June 2018, and WCAG 2.2 on 5 October 2023 with an update in December 2024. WCAG 2.2 is the current Recommendation. Critically, W3C states that the versions coexist: “WCAG 2.2 does not deprecate or supersede WCAG 2.1, and WCAG 2.1 does not deprecate or supersede WCAG 2.0.”

That is why Canadian law can still point at 2.0 in 2026 without being out of date in a technical sense. What each jurisdiction binds:

Jurisdiction	Standard bound	Notes
Ontario (AODA, O. Reg. 191/11)	WCAG 2.0 Level AA	Excludes 1.2.4 Captions (Live) and 1.2.5 Audio Descriptions. Applies to content published after 1 January 2012
Manitoba (M.R. 47/2022)	WCAG 2.1 Level AA	No employee threshold for the web duty
Quebec (SGQRI 008 3.0)	WCAG 2.1 AA plus 7 named WCAG 2.2 criteria	Public bodies only. In force 29 April 2024
Federal (SOR/2025-255)	CAN/ASC-EN 301 549	Not a WCAG version number. From 2027 and 2028

On WCAG 3.0: it is an incomplete working draft, not a standard, and W3C says so plainly. Updated drafts landed in September 2026 with a revised tiered conformance model. W3C’s own advice is that the best way to prepare for WCAG 3 is to meet WCAG 2.2 now. Ignore anyone selling WCAG 3 readiness.

One practical note for Manitoba: section 7(1) of M.R. 47/2022 binds web content that is “published on or after the day this regulation applies to the organization” or that “is required to access the organization’s goods and services.” Your 2019 blog archive is not in scope. Your booking page is.

Alberta: no statute, real exposure

Alberta has no enacted accessibility legislation binding private business, and the most recent attempt to create one failed six months ago.

Bill 206, the Accessible Alberta Act, was a private member’s public bill in the 31st Legislature. It passed first reading on 12 March 2026, was adjourned at second reading on 16 March, and was defeated on division on 23 March 2026. Alberta is one of the few provinces without accessibility legislation.

Be careful with the word “consultation” here. What exists is a completed report, not a live process. The Office of the Advocate for Persons with Disabilities published Accessible Alberta: Recommendations for Provincial Accessibility Legislation in 2023, recommending the government pass an Accessible Alberta Act within 18 months. The government has not introduced its own bill in response. Anyone telling you Alberta is currently consulting on accessibility legislation is repeating a three year old document.

So why does any of this matter in Alberta?

Because human rights law does not wait for accessibility statutes. The Alberta Human Rights Act prohibits discrimination in goods, services, accommodation or facilities customarily available to the public, protects mental and physical disability, and imposes a duty to accommodate to the point of undue hardship. The Alberta Human Rights Commission’s guidance treats services as including professional, medical, community and government services, and treats accommodation as including hotels, motels, bed and breakfasts, campsites and vacation property rentals. Short term rental operators should read that line twice.

Here is the honest limit of that argument, which most agency pages will not give you. We are not aware of a Canadian decision holding a private business’s website inaccessible under a provincial human rights code. The leading Canadian web accessibility case, Jodhan v. Canada (Attorney General), 2010 FC 1197, was a Charter equality challenge against the federal government’s own websites, decided 29 November 2010 and affirmed on appeal in 2012. It is not authority that a private company’s website must be accessible.

Treat human rights exposure as real but untested, and make your decision on commercial grounds instead. They are stronger anyway.

The number that actually matters

Per Statistics Canada’s 2022 Canadian Survey on Disability, 27% of Canadians aged 15 and over, or 8.0 million people, have one or more disabilities that limit them in daily activities. That is up 5 percentage points from 22% in 2017. The rate is 40% among Canadians 65 and over, and 30% among women.

In the same survey, 72% of persons with disabilities reported experiencing at least one of 27 types of accessibility barrier, and 17% reported barriers specifically related to online activities.

If you are a Calgary home services business, an inaccessible booking form is not primarily a legal problem. It is a conversion problem in a market where two in five of your senior customers report a disability. Note that many pages still quote the 2017 figures of 22% and 6.2 million. Those are nine years old.

What an accessibility audit actually involves

A real audit is two passes: automated scanning, then manual testing. Automated tools reliably catch roughly a third of WCAG failures. The rest require a human.

The automated pass

• Colour contrast ratios below 4.5:1 for body text and 3:1 for large text and UI components
• Missing or empty alt attributes on informative images
• Form inputs with no associated label
• Broken heading hierarchy, such as an H2 followed by an H4
• Missing document language attribute
• Links whose only accessible name is “read more” or “click here”
• Duplicate or missing ARIA landmark roles

The manual pass

• Keyboard only navigation. Unplug the mouse. Tab through the entire site. Every interactive element must be reachable, operable and visibly focused, in a logical order, with no keyboard traps.
• Screen reader testing. NVDA or JAWS on Windows, VoiceOver on macOS and iOS. Does the page announce in an order that makes sense?
• Alt text quality. An automated tool confirms alt text exists. Only a human confirms it says something useful. “IMG_4471” passes the automated check.
• Zoom and reflow. 200% text zoom and 400% page zoom without horizontal scrolling or lost content.
• Error handling. Do form errors get announced, and do they explain how to fix the problem?
• Motion and autoplay. Can carousels, video and animation be paused?

Why overlay widgets do not fix this

You have seen the pitch: one line of JavaScript, an accessibility icon in the corner, instant compliance. It does not work, and the accessibility profession has said so in writing.

The Overlay Fact Sheet, signed by contributors to the WCAG, ARIA and HTML specifications and by people from W3C, WebAIM, Deque, TPGi, the National Federation of the Blind and the American Council of the Blind, states: “No overlay product on the market can cause a website to become fully compliant with any existing accessibility standard and therefore cannot eliminate legal risk.”

The mechanical reason is simple. WCAG conformance requires satisfying every applicable success criterion. An overlay is a script reacting to rendered output. It cannot restructure a heading hierarchy, write meaningful alt text, fix a PDF, or repair content in Canvas, SVG or embedded media. Overlays also introduce their own privacy surface, which sits awkwardly next to your Law 25 consent obligations if you have Quebec users.

To be precise about what we are and are not claiming: no Canadian regulator or court has ruled on overlays. The argument against them is technical and comes from the people who wrote the standard.

The accessibility and SEO overlap

Roughly 40% of an accessibility remediation is work you should be doing for search anyway. Both a screen reader and a crawler parse your page without seeing it.

Accessibility fix	Search benefit
Correct H1 to H6 hierarchy	Clearer topical structure, better featured snippet eligibility
Descriptive alt text	Image search visibility and added page context
Descriptive link text instead of “click here”	Stronger internal anchor signals
Video captions and transcripts	Indexable text from otherwise opaque media
Semantic HTML landmarks	Better content extraction for AI answer engines
Labelled form fields	Higher completion rates, which is a conversion gain

That overlap is the argument for treating accessibility as part of a website growth programme rather than a one off compliance purchase.

Common mistakes

1. Buying compliance you do not need. An Alberta business with 12 employees being sold AODA remediation is being sold an Ontario obligation it does not carry.
2. Assuming the ACA applies to you. It binds federally regulated organizations. Most Canadian businesses are provincially regulated.
3. Quoting the $250,000 maximum as your exposure. It is the ceiling for repeat very serious violations by large federally regulated organizations.
4. Believing an overlay resolved it. See above.
5. Testing the homepage only. Your legal and commercial exposure sits in the booking flow, the contact form and the checkout, not the hero section.
6. Ignoring PDFs. Menus, price lists, intake forms and rate cards are frequently the least accessible assets a business publishes.
7. Treating it as a project. Every new page, plugin and campaign landing page can reintroduce failures. It is a maintenance discipline.
8. Using stale statistics. If your agency is quoting 22% and 6.2 million, they have not checked a primary source since 2017.

What to actually do, in order

1. Determine your jurisdiction. Federally regulated, Ontario at 50 or more employees, Manitoba at any size, or none of the above.
2. If none of the above applies, decide commercially. Run the numbers on 27% of your addressable market.
3. Run an automated scan across templates, not just pages. One theme fix usually resolves failures site wide.
4. Do the keyboard only pass yourself. It takes 20 minutes and it is the single most revealing test available to a non specialist.
5. Fix the conversion path first. Contact, booking, checkout, then everything else.
6. Write an accessibility statement covering your conformance target, known limitations and a contact route for barrier reports. It will be mandatory for federally regulated web pages from 2027.
7. Add it to your maintenance scope so it does not regress. Our WordPress maintenance guide covers where this fits.

Frequently asked questions

Is my website legally required to be accessible in Canada?

Only if you are federally regulated, an Ontario organization with 50 or more employees, or a Manitoba organization with at least one employee. Most Canadian businesses fall outside all three and have no statutory web accessibility duty, though human rights law still applies to how services are delivered.

Does Alberta have a web accessibility law?

No. Bill 206, the Accessible Alberta Act, was defeated on division at second reading on 23 March 2026. Alberta businesses have no statutory web accessibility standard. The Alberta Human Rights Act duty to accommodate in the provision of goods and services still applies.

Which WCAG version do I need to meet?

Ontario binds WCAG 2.0 Level AA, Manitoba binds WCAG 2.1 Level AA, and the federal ICT regulations bind CAN/ASC-EN 301 549 from 2027 and 2028. No Canadian law currently mandates WCAG 2.2. Building to 2.2 Level AA satisfies all of them, because W3C treats the versions as coexisting rather than superseding one another.

Is there a 31 December 2026 accessibility deadline in Canada?

Not for accessibility plans or web accessibility. That date was the end of the First Nations band council exemption under the Accessible Canada Regulations, and it has been extended to 31 December 2033. Federally regulated private sector plan deadlines were 1 June 2023 and 1 June 2024 depending on employee count.

Can I be fined $250,000 for an inaccessible website?

Realistically, no. The $250,000 ceiling in section 91(2) of the Accessible Canada Act applies to fourth or subsequent very serious violations by federally regulated entities that are not small businesses. Failing to publish an accessibility plan is a minor violation carrying $1,000 to $10,000 for a large regulated entity. Provincially regulated businesses are outside the Act entirely.

Do accessibility overlay widgets make my site compliant?

No. The Overlay Fact Sheet, signed by WCAG and ARIA specification contributors, states that no overlay product can make a website fully compliant with any existing accessibility standard. Overlays cannot restructure headings, write meaningful alt text or fix embedded media, and conformance requires satisfying every applicable success criterion.

How many Canadians have a disability?

27% of Canadians aged 15 and over, or 8.0 million people, per Statistics Canada’s 2022 Canadian Survey on Disability. The rate rises to 40% among Canadians 65 and over. Of those with disabilities, 17% reported barriers related to online activities.

Does accessibility help SEO?

Yes, substantially. Heading hierarchy, descriptive alt text, meaningful link text, captions and semantic landmarks all improve how crawlers and AI answer engines extract your content. Labelled form fields also raise completion rates, which is a direct conversion gain.

The bottom line

Most Canadian businesses are not legally required to meet WCAG today. That will not be true forever, the federal direction is set for 2027 and 2028, and Alberta’s legislative gap is a policy choice rather than a permanent condition.

The stronger case is the one that does not depend on a statute. More than a quarter of your Canadian market reports a disability, the fixes overlap heavily with search and conversion work you are already paying for, and the cost of building it in is a fraction of retrofitting it later. Compliance is the floor. The reason to do it is that an accessible site is a better built site.

If you are unsure which row of the table above you sit in, that is the question to resolve first. Everything else follows from it.

Get your site assessed

Wise Media builds and remediates Canadian business websites with accessibility, search and conversion treated as one workstream rather than three invoices. If you want to know where your site actually stands, and which obligations genuinely apply to your jurisdiction and size, start with our project intake form. We will tell you plainly if the answer is that you have no obligation at all.

Related reading: privacy policy requirements for Canadian websites, CASL compliance for forms and tracking, and Quebec French language rules. If you are planning a rebuild, our website packages include accessibility as standard scope.