AODA Website Requirements: What Applies at Your Business Size
The AODA website rule applies at 50+ employees. Dec 31, 2026 is a report deadline for 20+. A plain breakdown of what your business size needs to do.
If you run a business in Ontario, you’ve probably had an email or a sales call this year about AODA and your website, usually with December 31, 2026 in the subject line. That date is real. It’s the deadline to file your accessibility compliance report, and it only applies if you have 20 or more employees. The website rule is a separate thing. It has applied since January 1, 2021, and only to businesses and non-profits with 50 or more employees.
Most of what’s written about this mixes the two together. Here’s what actually applies at your size, taken from the regulation and Ontario’s own guidance pages as of October 2026.
What applies at your size
Count everyone who works for you in Ontario: full-time, part-time, seasonal and contract workers. Don’t count volunteers, independent contractors or staff outside Ontario.
| Employees in Ontario | Website must meet WCAG 2.0 AA | Compliance report due Dec 31, 2026 |
|---|---|---|
| 1 to 19 | No (encouraged) | No |
| 20 to 49 | No (encouraged) | Yes, on customer service only |
| 50 or more | Yes, since January 1, 2021 | Yes, including your website |
Every size still has duties under the customer service standard: training your staff, accepting feedback, and giving people information in an accessible format when they ask for it. That last one includes what’s on your website. If someone can’t read your menu or your price list online, you’re expected to get it to them in a format that works for them, at no extra cost.
What the website rule actually says
The rule is section 14 of Ontario Regulation 191/11. If you have 50 or more employees, your public website has to meet WCAG 2.0 Level AA, an international accessibility standard published in 2008. In practice that means things like:
- every image that carries meaning has text describing it
- text has enough contrast against its background to read
- the whole site works with a keyboard alone, no mouse
- form fields are labelled, so a screen reader can tell you what to type
- pre-recorded videos have captions
Two parts of the standard are carved out: live captions and audio descriptions for pre-recorded video. The rule covers content published after January 1, 2012, on sites you control directly or through a contract that lets you change them. Internal sites like an intranet aren’t covered.
There’s also an exception where meeting the rule “is not practicable.” Ontario is clear that you’d need to back that up, with real numbers if your reason is cost, and you may be asked to explain it in an audit.
What December 31, 2026 actually is
Every three years, businesses and non-profits with 20 or more employees file an accessibility compliance report through Ontario’s Accessibility Compliance Reporting Portal. The next one is due December 31, 2026.
What you’re asked depends on your size. With 20 to 49 employees, the report covers customer service only. With 50 or more, it covers more, including whether your public websites meet WCAG 2.0 AA. Someone with authority to legally bind the business has to certify it.
So if you’re at 50 or more and your site doesn’t meet the standard, the report is where that comes up. The obligation itself is five years old.
What happens if you don’t comply
Ontario’s page says not filing can lead to “enforcement measures which can include financial penalties.” The actual numbers are in the regulation. Administrative penalties for a corporation start at $500 and go up to $15,000. The $100,000 a day you’ll see in a lot of sales emails is a ceiling: it applies to court fines after a conviction, or to daily penalties when both the violation and your history of violations are rated “major.”
For a sense of how this plays out, Ontario’s 2024 annual report says 99% of its compliance audits that year were resolved as compliant. It issued 19 Director’s Orders, and one of them came with a financial penalty. The ministry’s approach is education and orders first. That’s a reason to fix things, and a reason to tune out anyone using fines to rush you into a contract.
If you’re under 50 employees
The website rule doesn’t apply to you. Ontario says smaller businesses are “encouraged” to meet it anyway.
I’d take them up on it, for a practical reason. The changes that make a site accessible are the same ones that make it easier for everyone: readable text, buttons that are easy to hit on a phone, forms that tell you what went wrong. They also help search engines understand your pages. And if you’re growing toward 50 people, building it in now is cheaper than retrofitting later.
Why an accessibility widget doesn’t fix it
You’ll get pitched overlay tools: a small button that adds a toolbar to your site for resizing text or changing colours. They don’t change the code underneath. A screen reader user still lands on the same unlabelled form and the same image with no description. If your site has problems, they get fixed in the site itself.
Which version of WCAG to build to
Ontario’s rule still names WCAG 2.0. There have been recommendations to update it, and as of October 2026 the regulation hasn’t changed. You’ll see claims online that Ontario requires 2.1 or 2.2, or will by 2027. I couldn’t find any Ontario source that says so.
I build new sites to WCAG 2.2 AA, the current version. W3C, which writes the standard, says content that meets 2.2 also meets 2.0 and 2.1. It’s a higher bar than the law sets, and it means a site doesn’t need rework if Ontario does update.
What it costs to fix
It depends on the site. Missing image descriptions and low-contrast colours are often an afternoon of work. A site built on a theme that was never accessible in the first place can cost more to patch than to rebuild. I’d want to look at yours before guessing at a number, and if a template is the right answer for your budget, I’ll say so.
How to check your own site this week
You can get a rough picture without hiring anyone:
- Keyboard test. Put your mouse away and press Tab through your homepage. Can you see where you are on the page, and can you reach and use every link, menu and button?
- Free scan. Run your homepage through WebAIM’s WAVE tool (wave.webaim.org). It flags missing image descriptions, contrast problems and unlabelled form fields.
- Zoom. Zoom your browser to 200%. Text should still be readable and nothing should be cut off.
- Your videos. Check that every pre-recorded video has captions, and that they’re accurate.
- Your PDFs. If a menu, price list or form only exists as a scanned PDF, a screen reader can’t read it.
An automated scan only catches part of the problem. If you’re at 50 or more and the scan turns up a long list, it’s worth having someone go through the site properly before you file.
I built HEET’s national tour site to meet AODA standards while running the tour’s marketing, and I build accessibility into every site from the start. If you’d like me to look at where yours stands, start with a conversation or see how I approach website design.
This is a plain-language summary, not legal advice. The regulation on Ontario’s e-Laws site is the official version, and Ontario’s AODA guidance for businesses is the best place to confirm what applies to you.

