I run Eskore, a web studio in Toronto that builds and fixes websites, so I sell this work. This is practical guidance from a web team, not legal advice, and a condensed version of our article; the full one is linked at the end.
If you run an Ontario business, you have probably had emails saying your website must be "AODA compliant by 31 December 2026". The date is real, but the rule behind it is often described wrongly. Here is what Ontario's rules actually ask of a website.
Two different obligations
The website rule. Section 14 of O. Reg. 191/11 (the Integrated Accessibility Standards Regulation) requires designated public sector organizations and large organizations, those with 50 or more employees in Ontario, to make their websites and web content meet WCAG 2.0 Level AA.
The 2026 report. Businesses and non-profits with 20 or more Ontario employees must file an accessibility compliance report by 31 December 2026, then every three years. The report covers all of your AODA duties, not only the website.
So a 30-person firm files a report but has no legal WCAG website duty. A 60-person firm has both.
| Ontario employees | Compliance report | Legal WCAG website duty |
|---|---|---|
| 1–19 | No | No (general AODA duties still apply) |
| 20–49 | Yes, by 31 Dec 2026 | No |
| 50+ | Yes, by 31 Dec 2026 | Yes: WCAG 2.0 AA |
| Public sector | Yes, every two years | Yes: WCAG 2.0 AA |
For 50+ organizations, the regulation excludes two success criteria: live captions (1.2.4) and pre-recorded audio descriptions (1.2.5). Level A applied to new sites from 1 January 2014 and Level AA to all sites from 1 January 2021, so both deadlines have passed. The report is where you confirm you met them.
2.0, 2.1 or 2.2?
The legal standard named for AODA is WCAG 2.0 AA, not 2.1 or 2.2, whatever some pages claim. For new builds, WCAG 2.2 AA is still the better target: it covers mobile interactions, focus hidden behind sticky headers, small tap targets and memory-based login steps. Because 2.2 builds on 2.0, the extra work is small if you plan for it from the start.
The core checklist
- Alt text on meaningful images; empty alt on decorative ones.
- Headings in a logical order, and unique page titles.
- Full keyboard navigation, no keyboard traps, visible focus.
- Contrast of 4.5:1 for normal text, 3:1 for large text.
- Form labels and error messages that say what went wrong and how to fix it.
- Captions and transcripts for video and audio.
- Text resizes to 200% without breaking the layout.
- Meaningful link text instead of "click here".
- ARIA used correctly, or not at all.
- Accessible PDFs, or HTML alternatives (a scanned menu is just an image).
Why overlays don't fix it
Accessibility widgets can change font size or contrast for a visitor. They can't fix broken heading structure, missing labels, illogical keyboard order, inaccessible menus, PDFs or checkout errors. Those live in your code, design and content. In the US, accessibility claims keep being filed against sites that already had a widget installed.
How to test
- Automated scans (Lighthouse, axe-style tools) catch missing alt text, contrast failures and unlabelled fields. They find only part of the problem.
- Manual checks: use the site with only a keyboard, submit every form with deliberate mistakes, test at 200% zoom and on mobile.
- A screen reader on your main journeys: homepage, a service page, contact, and checkout if you have one.
What proof to keep before you file
The report is certified by someone who can bind the organization, so a "yes" on the website question should have evidence behind it:
- a dated audit that names the standard tested against;
- a remediation log: each issue, its fix and the date;
- scan results and manual test notes;
- notes on third-party content you can't modify;
- a published accessibility statement with a feedback contact;
- a recurring testing schedule (quarterly suits most sites).
Fines, in proportion
Section 37 of the AODA sets maximum fines on conviction of up to $100,000 a day for a corporation. Those are prosecution ceilings, not the usual first outcome. In practice, enforcement has focused mostly on organizations that don't file their reports. Don't panic, but don't skip the report, and don't tick boxes you can't support.
Full article, with platform notes for WordPress, Shopify, Webflow and Next.js: https://eskore.ca/blog/aoda-compliant-website-toronto
Top comments (0)