There's a government form due December 31, 2026, and most business owners we talk to have never heard of it. If your business or non-profit has 20 or more employees in Ontario, you're supposed to file an accessibility compliance report with the province. Fewer than 20, and none of that applies to you, though a different, smaller set of rules still does.
We get asked about this every time a client hears "AODA" in the news and assumes the worst. Most of the time the actual obligation is smaller than they feared, and sometimes it's bigger. Here's the honest breakdown.
Who actually has to file anything
The Accessibility for Ontarians with Disabilities Act (AODA) applies to every organization in Ontario with at least one employee, but the paperwork and the website rules scale up in two steps, at 20 employees and at 50 employees.
| Employees | Compliance report due Dec 31, 2026 | Website must meet WCAG 2.0 Level AA |
|---|---|---|
| 1 to 19 | No | No, but customer service and accessible-format rules still apply |
| 20 to 49 | Yes, every three years | Not required by the web rule, though it's good practice |
| 50 or more | Yes, every three years | Yes, for public-facing web content |
Source: Ontario's accessibility compliance reporting page. If you're under 20 staff, you can stop worrying about the December deadline specifically. You still owe your customers accessible service and accessible documents on request; that part of AODA has applied to every business since 2012, regardless of size.
What WCAG 2.0 Level AA actually requires
For organizations at 50 employees and up, the Integrated Accessibility Standards Regulation requires public-facing web content to meet WCAG 2.0 Level AA. That standard boils down to four things: your site needs to be perceivable, operable, understandable, and robust. In plain terms: images need real descriptions, every function needs to work from a keyboard, text needs to hold its contrast against the background, and forms need labels a screen reader can announce.
This part of the law isn't new. The deadline for the actual web accessibility work passed back on January 1, 2021. What's new for 2026 is the reporting requirement, the province wants organizations with 20 or more staff to formally confirm where they stand, even the ones under 50 who don't have the WCAG obligation.
Check your own site today, it takes about twenty minutes
You don't need us for this part. Install the free WAVE browser extension or the axe DevTools extension, run it on your homepage and your contact page, and look at three things:
- Every image has real alt text. Not "image1.jpg", an actual description of what's in the photo. Decorative images should have empty alt text, not none at all.
- You can tab through the whole page with just a keyboard. No mouse. If you land on a button you can't see is focused, or you get stuck in a menu, that's a real barrier for someone using a screen reader or a switch device.
- Your form fields have visible labels, not just placeholder text that disappears the moment someone starts typing.
Fix what the free scan flags, and you've closed most of the gap between "we ignored this" and "we made a genuine effort," which matters both for your customers and for how a complaint would look if one ever landed.
The three things we find broken on almost every site
Doing this work for a living, the same problems show up on nearly every audit we run: contact forms with placeholder text instead of real labels, buttons that are pale grey on white and fail contrast by a wide margin, and PDF menus or price sheets that are just a scanned photo, unreadable by any screen reader. None of those are hard to fix once you know to look. The hard part is nobody looks until a customer or an auditor points it out.
We also see businesses buy an accessibility overlay widget, the kind that adds a floating icon promising instant compliance, and stop there. We don't recommend them. Overlays sit on top of broken code instead of fixing it, several well-known overlay vendors have been sued by the same disability advocates the tools claim to serve, and a manual scan will still find the underlying problems. Fix the code. It's not more expensive in the long run, and it actually works.
When to fix it yourself and when to bring in help
If you're under 20 employees and your site is a handful of pages, alt text, contrast, and form labels are a Saturday afternoon project, not a hired job. Free tools will catch 80 percent of it.
Once you're at 50 employees, the law expects a real WCAG 2.0 AA pass, and once your site has bookings, online ordering, multi-step forms, or a lot of pages, a manual scan misses things automated tools can't catch, like whether your tab order actually makes sense to someone who can't see the screen. That's when it's worth having a developer who does accessible web design go through it properly, and where ongoing hosting and maintenance work matters, because a site that passes today can break its own accessibility with the next plugin update if nobody's watching.
This is general information, not legal advice. If you're not sure where your organization lands, or you've received a complaint, talk to an accessibility consultant or an employment lawyer.
We do this kind of cleanup for clients around London and out to St. Thomas as part of regular website work. If you want a second set of eyes on your site before the December deadline, book a call and we'll tell you honestly whether you have a problem.
Frequently asked questions
Does AODA apply if I only have five employees?
Some of it, yes. The customer service and accessible-format rules apply to every business with at least one employee. The December 2026 compliance report and the WCAG website requirement only kick in at 20 and 50 employees.
Do I need to file the compliance report with 15 employees?
No. The report is required for organizations with 20 or more employees. Under that, you have no form to file, though the general accessibility standards still apply to how you serve customers.
What happens if I ignore this?
The statutory maximum penalty under AODA reaches $100,000 a day for a corporation, with personal liability for directors and officers on top of that. In practice, enforcement has focused on organizations that ignore direct requests or complaints, not on businesses making a genuine effort. Making the effort is the part that protects you.
Will an accessibility overlay widget make my site compliant?
No, and we'd tell a client that even if it cost us the sale. Overlays mask problems in the browser without fixing the underlying code, and several vendors have faced lawsuits from the same community they claim to help. A real fix touches the actual markup.
Is the WCAG standard changing soon?
Ontario currently requires WCAG 2.0 Level AA, with a move toward the newer WCAG 2.2 standard expected in the next couple of years. Build to 2.0 AA now and most of that work carries forward.