Summary: Most Toronto business owners have heard that websites have to be accessible by law, and most of them have been told something that is not quite true. The AODA web rules apply to Ontario organisations with fifty or more employees, not to every business with a website. But a separate rule catches everyone with twenty or more, and its next deadline is 31 December 2026. This guide sorts out which rules apply to a business your size, what WCAG 2.0 Level AA actually asks for in plain English, what to fix first, and why most of it is worth doing even where the law does not require it.
Somebody has probably told you that your website has to be accessible by law. They may have been selling you something at the time. The truth is more useful than either the scare story or the shrug — and for a lot of Toronto businesses it is genuinely good news.
The short answer
- The AODA web standard applies to Ontario organisations with 50 or more employees. Under 50, it does not apply to your website at all.
- For those it covers, the requirement is WCAG 2.0 Level AA, and the deadline was 1 January 2021. It is not coming — it has been and gone.
- A separate rule catches far more businesses: 20 or more employees must file an accessibility compliance report, and the next one is due 31 December 2026.
- Those two are different things. A 25-person Toronto firm must file but is not required to meet WCAG on its website.
- Accessibility overlay widgets do not make you compliant. Fix the site, not the symptom.
- Most of the work overlaps with good SEO and with a better phone experience, which is why it is worth doing anyway.
Who the rules actually cover
The Accessibility for Ontarians with Disabilities Act does not treat every organisation the same way. It scales with headcount, and the website part sits quite high up that scale.
| Your organisation | Website must meet WCAG 2.0 AA | Must file a compliance report |
|---|---|---|
| 1–19 employees | No | No |
| 20–49 employees | No | Yes — next due 31 Dec 2026 |
| 50+ employees | Yes — since 1 Jan 2021 | Yes — next due 31 Dec 2026 |
| Public sector | Yes | Yes, on its own schedule |
Read the middle row twice, because it is the one that catches people. A Toronto company with twenty-five staff has a filing obligation and no website obligation. Being told “you must make your site WCAG compliant or you will be fined” is, for that company, simply not true.
Two other things worth knowing. The web standard covers content published or significantly refreshed after 1 January 2012, not your entire archive. And the AODA version of WCAG 2.0 AA excludes two items — live captions and pre-recorded audio description — so you are not required to caption a live stream.
None of that means a small business has no AODA duties at all. Other standards — accessible customer service, accessible formats on request, employment practices — reach much further down. It is specifically the website technical standard that stops at fifty.
Most of what Toronto business owners get told about website accessibility law is sold by people who profit from the fear. The rule is narrower than the sales pitch, and the reason to do the work is better than the rule.
The 31 December 2026 deadline
This is the live one, and it is close.
Every business and non-profit in Ontario with twenty or more employees files an accessibility compliance report with the province every three years. The last cycle closed on 31 December 2023, which puts the next one on 31 December 2026. Filing is a legal obligation in its own right, independent of whether the web standard applies to you.
It is a form, not an inspection. You are confirming you have met the obligations that apply to your organisation — training, customer service, accessible formats on request, and the web standard if you are over fifty. The filing itself is free and takes a short while if the underlying work is done.
If you are between 20 and 49 employees, this is the one to diarise. It is also the one most often missed, precisely because the owner has been told the rules are about websites — and having checked that their website is fine, assumes they are done.
What WCAG 2.0 AA asks for, plainly
The standard is long and written for specialists. Nearly all of the real-world failures we see on Toronto sites come down to the same handful of things.
Images need text alternatives
Every meaningful image needs alt text describing what it shows. Decorative images get an empty alt so a screen reader skips them rather than reading out a filename.
Text needs contrast
Normal text needs a contrast ratio of at least 4.5:1 against its background. Pale grey on white is the single most common failure, and designers love it.
Everything works by keyboard
Menus, forms, sliders and popups all have to be reachable and operable with Tab and Enter, and you must be able to see where you are.
Forms have real labels
A placeholder is not a label. Each field needs a label a screen reader can announce, and errors have to say what went wrong in words.
Text can be enlarged
Zoom to 200 per cent and the layout has to hold together without content disappearing or overlapping.
Video has captions
Pre-recorded video needs captions. Under the AODA you are not required to caption live video or add audio description to recordings.
Notice how much of that is just competent build work. A site where the headings are real headings, the buttons are real buttons and the images are described is most of the way there before anyone mentions compliance.
Checking your own site in ten minutes
You do not need a consultant to find out whether you have a problem. Four checks, no tools to install, and between them they catch most of what an audit would flag.
- Unplug the mouse. Press Tab through your home page. Can you reach the menu, open the dropdowns, fill the contact form and press send? Can you always see which thing is selected? If the focus outline is invisible or the trail disappears into a popup you cannot escape, that is a real failure and a common one.
- Zoom to 200 per cent. Ctrl and plus, five times. Does text overlap, vanish, or force you to scroll sideways to read a sentence?
- Run Lighthouse. In Chrome, right-click the page, Inspect, Lighthouse tab, tick Accessibility, run it. It is free, it is built in, and it catches contrast, missing alt text and unlabelled form fields in seconds. It does not catch everything — automated tools find roughly a third of real issues — but a low score is a reliable sign.
- Read your images with the pictures off. If your hero says nothing but “hero-banner-final-v3.jpg”, that is what a blind visitor hears.
The keyboard test is the one worth doing first. It takes two minutes, it needs nothing installed, and in our experience it finds more genuine problems than any scanner — particularly on sites built with sliders and pop-ups, which is most of them. If the slider itself is broken rather than merely inaccessible, that is a repair job instead.
Why the overlay widgets do not work
You have seen the pitch: one line of JavaScript, a little accessibility icon floats in the corner, and the site is compliant. It is sold hard, often with a monthly fee and a certificate.
It does not do what it claims. An overlay sits on top of your website; it cannot repair the markup underneath, which is the thing screen readers actually read. The disability community has been consistently critical of these tools, people who rely on assistive technology frequently report that overlays interfere with the software they already use, and in the United States overlays have shown up in accessibility lawsuits rather than preventing them.
If someone is selling you compliance as a subscription with no changes to your site, that is the thing to be sceptical about.
- An overlay cannot add alt text that describes your photographs.
- It cannot turn a
<div>that behaves like a button into a real button. - It cannot fix a form field with no label.
- It cannot make a keyboard trap escapable.
Why to bother when the law does not make you
Here is the honest case for a business under fifty employees, where none of this is required.
About one in five people has a disability. Not all of those affect web use, but plenty do, and the group is larger than most owners picture: it includes anyone with low vision, anyone with a tremor, anyone using a phone in bright sunlight, and anyone who is simply getting older. An inaccessible site is not failing a rare edge case. Across the projects in our portfolio the pattern is consistent: the builds that were done carefully need the least retrofitting.
Most of the fixes help everyone. Better contrast is easier to read on a phone outdoors. Proper labels mean autofill works. A site that works by keyboard tends to work properly on a touchscreen too.
A good share of it is the same work as SEO. Alt text, a real heading structure, descriptive link text instead of “click here”, captions, clean semantic markup — Google reads all of those. Accessibility is not a ranking factor, but the work produces exactly the kind of page a crawler understands. We cover the rest of that in our complete guide to website design in Toronto.
And you may grow into the rule. Fifty employees is not far away for a business that is doing well, and retrofitting an old site is dearer than building the next one properly.
The compliance argument persuades nobody under fifty staff, because it does not apply to them. The argument that works is simpler: a fifth of your visitors have an easier time, and so does everyone on a phone.
What it costs to fix
It depends almost entirely on how the site was built, which is why an audit comes first.
| Scope | Typical Toronto cost | Time |
|---|---|---|
| Audit and report What fails, how badly, and what it would take. |
$500–$1,500 | About a week |
| The common fixes Contrast, alt text, labels, headings, keyboard and focus. |
$1,000–$3,000 | 1–3 weeks |
| Structural work Rebuilding components that were never accessible — custom menus, sliders, modals. |
$3,000–$8,000 | 3–6 weeks |
| Build it in from the start On a new site, as part of the build. |
Little or nothing extra | — |
That last row is the real point. Accessibility costs almost nothing when it is part of how a site is built and a great deal when it is bolted on two years later. It is one of the few things in web work where doing it properly the first time is also the cheap option. The same is true of most of what we are asked about on our frequently asked questions page.
If your site is old enough that these are structural problems, the honest conversation is whether to repair or replace. Our fixed-price packages cover new builds, and if the site is simply neglected rather than badly built, monthly maintenance keeps it from drifting further.
Common questions
Does my Toronto website legally have to be accessible?
It depends on your headcount. Under the AODA, Ontario private-sector organisations with fifty or more employees must make public-facing web content meet WCAG 2.0 Level AA, and that deadline passed on 1 January 2021. If you have fewer than fifty employees, the web content standard does not apply to you, so there is no legal requirement for your website to meet WCAG. Other parts of the AODA, including accessible customer service, still apply to much smaller organisations.
What is the 31 December 2026 accessibility deadline?
It is the next accessibility compliance report. Businesses and non-profits in Ontario with twenty or more employees have to file a report with the provincial government every three years confirming they have met their AODA obligations. The last one was due 31 December 2023, which makes the next one 31 December 2026. It is a filing obligation and it is separate from the website standard, so a business with twenty-five employees has to file even though the WCAG web rules do not apply to it.
What is WCAG 2.0 Level AA in plain English?
It is a checklist for making web content usable by people with disabilities. In practice the items that matter most are: every image has a text description, video has captions, text has enough contrast against its background, the whole site can be operated with a keyboard alone, text can be enlarged to 200 per cent without breaking the layout, and form fields have labels a screen reader can announce. The AODA version excludes live captioning and pre-recorded audio description.
How much does it cost to make a website AODA compliant?
On a reasonably modern site, fixing the common issues — contrast, alt text, form labels, keyboard navigation, heading structure — is usually one to three thousand dollars in Toronto. On an old site built with a page builder that generates poor markup, it can cost more than rebuilding, because the problems are structural rather than cosmetic. An audit first is the honest way to find out which of those you have.
Do accessibility overlay widgets make a site compliant?
No, and it is worth being blunt about it. The one-line scripts that add a floating accessibility button do not fix the underlying markup, they are widely criticised by the disability community, and in the United States they have featured in lawsuits rather than preventing them. They can also interfere with the screen readers people already use. Fix the site itself.
Does accessibility help SEO?
A good part of it overlaps. Alt text, a sensible heading structure, descriptive link text, captions and clean semantic markup are all things Google reads and all things an accessibility audit asks for. Accessibility is not a ranking factor in itself, but the work produces a page that is easier for a crawler to understand, and the same fixes usually improve the experience for everyone on a phone.
Not sure where your Toronto website stands?
Tell us your headcount and your domain and we will tell you which rules actually apply to you, and whether your site has a real problem or an imaginary one. No charge for the answer.
