An accessible website: the obligation on its way, and the quarter of the work that matters

Web accessibility usually enters an SMB conversation through the door of fear: a vendor mentions "compliance", someone brings up fines, and the owner starts wondering whether they just discovered a legal problem they didn't have yesterday. For a private Quebec SMB in 2026, the honest answer is that no obligation applies to you yet.

That is not a reason to close the file. Three distinct regimes travel under the same word, and the part of the work that actually matters is small, well known, and part of a properly built website.

This article separates the legal layers, describes the quarter of the rules that removes most of the barriers, and shows how to check it yourself in ten minutes.

The short answer, for the busy

No law today requires a private Quebec SMB to make its website conform to WCAG. The Accessible Canada Act covers only federally regulated organizations, and its first digital regulation (SOR/2025-255, registered December 5, 2025) will not require new web pages to conform for federally regulated businesses with 100 or more employees until December 5, 2028. In Quebec, the SGQRI 008 3.0 standard, in force since April 29, 2024, applies only to public bodies. Ontario, by contrast, has required private businesses with 50 or more employees to comply since January 1, 2021. Quebec's Charter of Human Rights and Freedoms already prohibits discrimination based on disability in services offered to the public, a live if untested recourse. The direction of travel is one-way, even if the obligation has not arrived. And six defect types account for 96% of all errors detected across the million home pages WebAIM analyzed in 2026: contrast, alt text, form labels, empty links, empty buttons, and page language.

Three laws, three perimeters, none of which covers you

"Accessibility law" gets used for three things that cover completely different organizations.

The Accessible Canada Act (in force July 11, 2019) aims for a barrier-free Canada by January 1, 2040. It applies to organizations under federal responsibility: departments, agencies, Crown corporations, and the slice of the private sector Ottawa regulates, meaning banks, telecommunications, broadcasting, the post, and interprovincial transportation. Your storefront or your machine shop in Laval is not on that list.

The SGQRI 008 3.0 standard of the Quebec government came into force on April 29, 2024. It requires WCAG 2.1 Level AA, plus a handful of WCAG 2.2 criteria, on all new web content. Its scope is spelled out: public bodies covered by section 2 of the Act respecting the governance and management of the information resources of public bodies. Ministries, municipalities, health, education. Not businesses.

Ontario is the one that shows what comes next. Since January 1, 2021, the AODA has required designated public sector organizations and any business or non-profit with 50 or more employees to make their public websites conform to WCAG 2.0 Level AA. A 60-person Ontario SMB has had that obligation for five years. The same SMB in Quebec has none.

What the December 2025 federal regulation actually changes

The most concrete move is recent and went unnoticed. On December 5, 2025, Ottawa registered SOR/2025-255, the regime's first digital regulation, adding a full part on information and communication technologies to the Accessible Canada Regulations. The reference standard is not WCAG but CAN/ASC-EN 301 549, published by Accessibility Standards Canada, which incorporates the WCAG criteria.

The schedule runs in two steps. On December 5, 2027, federal public sector entities must make their new web pages conform, publish an annual accessibility statement, and train the staff who touch ICT. On December 5, 2028, the same web page obligation extends to federally regulated private businesses with an average of 100 or more employees over the preceding three years. Mobile apps and downloadable documents follow, at a 500-employee threshold.

Two details are worth noting. The obligation covers only pages created or updated after the coming-into-force date: Ottawa chose to stop the bleeding rather than demand a rebuild of everything already published. And the penalties are modest, classified as "minor": $1,000 to $10,000 for a first violation within five years. What stings more is that the Accessibility Commissioner can publish the names of the organizations that violate the rules.

None of this touches you. But if you supply a bank, a telecom, or an interprovincial carrier, your client will be covered, and requirements travel down a supply chain through contracts long before they arrive through legislation.

The recourse that already exists

While everyone waits for a law, Quebec's Charter of Human Rights and Freedoms has been in force since 1975. Section 10 makes disability a prohibited ground of discrimination. Section 12 prohibits refusing, through discrimination, to enter into a juridical act respecting goods or services ordinarily offered to the public. Section 15 prohibits preventing access to public places, "such as commercial establishments".

An order form that cannot be completed with a screen reader looks a lot like a service offered to the public that someone cannot access. Let's stay careful: we found no published Quebec decision applying those sections to a private company's website. The mechanism exists, a complaint costs nothing to file, and it is not waiting for 2028.

The quarter of the work that removes most barriers

Here is the useful part. Every year, WebAIM runs an automated engine across the million most-visited home pages. In the February 2026 analysis, 95.9% of pages had at least one detectable WCAG failure, averaging 56 errors per page, a number that rose from 2025.

The finding that matters is elsewhere: six defect categories account for 96% of all errors detected, and they have been the same six for seven years.

Low contrast, on 83.9% of pages, at 34 instances per page on average. WCAG asks for 4.5:1 between text and its background, 3:1 for large text. This is the pale grey on white nobody can read outdoors.

Missing alt text, on 53.1% of pages and 16.2% of all images. An image with no alt is a hole for a screen reader, and an invisible image for Google.

Missing form labels, on 51% of pages and one third of all fields. A field with no label is announced as "edit text", with no clue what goes in it.

Empty links (46.3%) and empty buttons (30.6%). Typically an icon on its own, with no machine-readable text.

Missing document language, on 13.5% of pages. One attribute, lang="en-CA", that decides how the whole page is pronounced.

Add two rules no tool measures: every function must work with the keyboard alone (a Level A criterion, the most basic tier), and nothing should flash or animate with no way to stop it. That is the complete list. It is not a redesign project, it is a week of fixes.

Why this work pays twice

Accessibility and SEO describe the same structure in different vocabulary. Alt text feeds image search. A clean heading hierarchy serves the screen reader and the crawler, both of which read the page without seeing it. The language attribute drives pronunciation and language targeting, the subject of our piece on the bilingual site and Bill 96. Animations you cannot stop degrade Core Web Vitals. And a properly labelled form gets completed more often, which is exactly the subject of a homepage that converts.

That is the argument for the owner with no legal obligation at all: you fix these six things for the same reason you fix a typo on the pricing page.

Testing in ten minutes, and what the tool cannot see

Three checks, no budget.

Put the mouse away. From the top of your home page, use Tab, Enter, and the arrow keys. Can you reach the menu, open a submenu, fill the form, submit it? Can you always see where you are? A focus outline removed in CSS "because it looked ugly" is the most common sin.

Pick up your phone. VoiceOver on iPhone, TalkBack on Android, both already installed. Listen to your page for two minutes. Silent images and buttons announced as "link" are obvious within seconds.

Run an automated checker, then know what it is worth. In 2017, the UK's Government Digital Service built a page stuffed with 143 known barriers and ran ten tools at it. All ten combined found 71%: 42 barriers, or 29%, escaped every one of them. The best single tool found 37%, or 41% counting its prompts to check manually. WebAIM says the same thing in its own words: the absence of detected errors does not mean a page is accessible. A green score is a floor, never a proof.

The same goes for overlay widgets sold as "compliance in one line of code". They add a layer on top of the code; they do not repair the contrast chosen in your brand palette or the label missing from your form.

What we do, and what we don't promise

On new sites, we aim for WCAG 2.2 Level AA, the current version the W3C recommends, published December 12, 2024. "Aim" is the right verb: a living site takes on content, images, and documents after launch, and nobody honest guarantees permanent conformance on content they do not write. What we do guarantee is that the foundation is not working against you: validated contrast, full keyboard navigation, labelled forms, declared language.

If you just want to know where you stand, those six categories can be measured on an existing site in about an hour, and the result fits on one page.

→ Request an audit of your site

This article explains a moving legal framework to help an SMB ask the right questions; it is not legal advice. The texts of the Accessible Canada Act, the Accessible Canada Regulations, the Charter of Human Rights and Freedoms, and the SGQRI 008 standard prevail: validate your situation with legal counsel before any decision.