AODA and your website, what Ontario businesses actually need to know.

Every so often an Ontario business owner gets an email warning that their website is breaking accessibility law and that a costly fix is needed immediately. Sometimes that email is from someone genuinely helpful. Often it is a sales tactic that leans on the fact that almost nobody knows what the rules actually say. The rules are not complicated, and once you know two numbers you will know exactly where you stand.

This is a plain language walk through of the Accessibility for Ontarians with Disabilities Act as it touches websites. What it is, who it covers, what the technical standard means in normal words, what the reporting requirement is and when it falls due, and what a smaller business that sits under the threshold should sensibly do. It is written to be accurate and unexcited, because the goal here is for you to stop worrying about the wrong things and spend your money on the right ones.

What the AODA is, in plain language

The AODA is Ontario legislation aimed at removing barriers for people with disabilities across the province, in stages, over a long timeline. It covers a lot more than websites. It reaches into customer service, employment practices, public spaces, transportation and information. Most owners meet it first through something physical, a ramp, a doorway width, a service animal policy, and only later find out there is a digital piece too.

The digital piece sits inside the information and communications part of the rules. In short, it says that certain organizations must make the web content they put in front of the public usable by people with disabilities, measured against a recognised international technical standard rather than against somebody's opinion. That standard is WCAG, the Web Content Accessibility Guidelines. Using an existing global standard is deliberate, it means the target is fixed and testable instead of a matter of debate.

Exactly who it applies to

Two numbers decide this. Public sector organizations of any size, and private organizations with 50 or more employees, must make their public facing websites and web content meet WCAG 2.0 Level AA. The deadline for that was 1 January 2021, so it is not upcoming, it is already in force. The requirement applies to web content created or significantly refreshed since 1 January 2012, which is why an old page that has genuinely not been touched is treated differently from a site you rebuilt last year.

Two specific parts of the standard are excepted, so you are not expected to meet all of it. Success criterion 1.2.4, which covers captions on live video, and success criterion 1.2.5, which covers audio descriptions for pre recorded video, are both carved out. Everything else at Level AA is in scope. If you are a private business with fewer than 50 employees, and the large majority of local trades, clinics, salons, shops and studios are, the web standard is not a legal requirement for you. That is the plain truth and anyone telling you otherwise should be asked to show you where it says so.

What WCAG 2.0 Level AA means in normal words

WCAG is organised around four ideas, that content should be perceivable, operable, understandable and robust. Level AA is the middle of three levels and it is the one regulators around the world tend to point at. Stripped of the jargon, it asks for things any sensible person would recognise as fair. Text has enough contrast against its background to be readable. Every meaningful image has a written description. Every form field has a proper label. Video carries captions.

It also asks that a person can operate the whole site with a keyboard alone, that they can always see which element they are on, that they can zoom the text without the page falling apart, and that colour is never the only way meaning is carried, so a red outline on a broken form field is joined by words explaining the problem. Pages need real headings in a sensible order, links that say where they go, and a page language declared in the code so screen readers pronounce things correctly. None of that dictates how your site should look. Almost all of it is invisible to a sighted visitor with a mouse.

Two numbers settle most of the confusion. Fifty employees for the web standard, twenty for the reporting. Everything else is detail.

What "public facing web content" actually covers

The phrase means the material you publish for the general public rather than the tools your staff use internally. So your website, its pages, and the documents you offer for download from it. That last part surprises people. A price list, a form, a menu or a brochure published as a PDF is web content, and a PDF that is really just a scanned image of a page is completely unreadable to a screen reader. If you publish documents, they count.

Things you embed from elsewhere are the other grey area worth thinking about. A booking widget, a review carousel, a map, a chat bubble or a video player is part of what the public experiences on your site even though somebody else wrote the code. In practice you cannot rewrite a third party tool, so the realistic approach is to choose vendors who take accessibility seriously and to always provide a plain alternative route, a phone number and an ordinary form alongside the fancy booking widget. That is good business anyway, because embedded tools break.

The reporting requirement and the December 2026 deadline

This is separate from the web standard and it catches people out because the threshold is lower. Private sector businesses and non profit organizations with 20 or more employees are required to file an accessibility compliance report with the province, and the current filing deadline is 31 December 2026. It is a report about your organization's accessibility obligations generally, not a technical audit of your website.

The point worth holding onto is that the two obligations use different numbers. A business with 30 employees has a reporting obligation but is not caught by the web standard. A business with 60 has both. If you are near either line, or if your headcount moves with the seasons, that is exactly the situation to take to the province's own guidance or to a professional rather than to guess. Start with Ontario's accessibility information for businesses, which is the official source and is written for owners rather than lawyers.

---

Common misunderstandings

These are the ones that cost owners either money or sleep, usually needlessly:

• Believing every business in Ontario must meet the web standard. The private sector threshold is 50 or more employees.
• Assuming the deadline is still coming. For the web standard it passed on 1 January 2021.
• Mixing up the two thresholds, so a 25 person company panics about WCAG when its actual obligation is the report.
• Thinking an overlay widget or an accessibility toolbar makes a site compliant. Those tools sit on top of the problem rather than fixing it.
• Forgetting downloadable PDFs and forms, which are web content too.
• Treating it as a one time project, when every new page, photo and document you publish carries the same requirements.
• Taking a cold email's word for your legal position instead of checking the province's own guidance.

Practical next steps, whichever side of the line you are on

In rough order of value for the time it takes:

1. Count your employees honestly, including part time staff, and write the number down.
2. Check that number against the province's guidance to confirm which obligations, if any, apply to you.
3. If you are at 20 or more, put the 31 December 2026 reporting deadline in your calendar now with a reminder well ahead of it.
4. Run a free scan on your three most important pages using Lighthouse in Chrome or the WAVE extension.
5. Fix contrast, missing image descriptions and unlabelled form fields first. They are the most common failures and the cheapest to correct.
6. Tab through your homepage with the keyboard alone and fix anything you cannot reach or see.
7. Replace image only PDFs with real web pages wherever you can, since a page is easier to make accessible than a document.
8. Ask whoever maintains your site to make accessibility part of publishing, not a project you do once a year.
9. If you are close to the 50 employee line or expect to cross it, build to the standard now rather than retrofitting later.

If you are under the threshold, here is the honest advice

Do it anyway, but do it calmly and for business reasons rather than out of fear. A person who cannot read your text, cannot use your form or cannot hear your video is a customer who cannot hire you, and that arithmetic does not care about employee counts. The population is ageing, so the number of visitors who need larger text and clearer buttons rises every year. Nearly every fix also makes the site better on a phone, which is where most of your traffic already is, so you are paying once for two benefits. Our plain accessibility checklist walks through the specific items, and six ways to improve your website's user experience covers the same ground from the conversion side.

One last thing worth saying plainly. Nothing here is legal advice, and your obligations depend on facts about your own organization that a web article cannot know. Confirm them with the Government of Ontario or a qualified professional. What we can tell you is the practical part. Building a site properly the first time, with real headings, readable type, labelled forms and clean code, costs no more than building it badly, and it means this whole topic stops being a worry. If you also want to be sure the finished site is genuinely yours to control, read who owns your website before you sign anything.