WCAG & Accessibility·4 min read

AODA Web Accessibility Explained for Ontario Sites

Ontario put web accessibility into provincial law years before most jurisdictions, and it backed the requirement with per-day fines. In working terms: since January 1, 2021, covered organizations must hold their public websites and web content to WCAG 2.0 Level AA under the Integrated Accessibility Standards Regulation, alongside duties around policy, training, feedback, and periodic compliance reports. Which of those obligations land on your organization depends on headcount and sector, so that's where to start.

Open the free AODA Compliance Checklist All insights

AODA web accessibility explained: what the IASR requires

The technical core.

Section 14 of the IASR is the web provision. It requires covered websites and the content on them, web apps included, to conform to WCAG 2.0 Level AA, with two exceptions: live captions (criterion 1.2.4) and prerecorded audio description (1.2.5). Everything else at Levels A and AA applies in full, from alt text and contrast to keyboard access and page language.

Legacy content gets a limited pass: content first published before January 1, 2012 doesn't have to meet the WCAG requirement, but if someone asks for it in an accessible format, you must provide one. Update or republish a page, though, and it is treated as new content with full obligations.

Who must comply with AODA, by headcount and sector

Count your employees first.

The answer runs along two axes. The website rule binds businesses and non-profits with 50 or more employees in Ontario, and every public sector organization regardless of size. Below 50 employees, the website rule doesn't apply, but duties like customer service policies, staff training, accessible feedback, accessible formats on request and telling job applicants about accommodation still do.

The AODA Compliance Checklist handles this for you. Pick 1 to 19 employees, 20 to 49, 50 or more, or public sector, and the list hides the duties that don't apply; Show everything brings back the full set. Headcount is also worth watching over time. A 45-person company that crosses 50 acquires the web obligations, and growth is exactly when websites sprawl and accessibility debt accumulates fastest.

AODA reporting deadlines and the records behind them

The recurring part people miss.

AODA compliance isn't a one-time renovation; it's a filing cycle. Businesses and non-profits with 20 or more employees file an accessibility compliance report every three years, and the current cycle is due by December 31, 2026. Public sector organizations report on their own cycle. Confirm your date on Ontario's accessibility compliance reporting page before you file, since missing or misreporting is its own problem.

Behind the report sits paperwork the checklist tracks group by group: written accessibility policies and a multi-year plan for larger and public sector organizations, training records covering staff and volunteers, and an accessible feedback process. On conviction, the Act allows fines of up to $100,000 per day for corporations and up to $50,000 per day for individuals and unincorporated organizations, and directors and officers who knowingly allow a violation can also be fined.

A worked AODA example: captions on a product video

Two videos, two outcomes.

Say a 60-employee Ontario retailer posts a 90-second product demo on its site with no caption track. Under WCAG 2.0 AA that fails criterion 1.2.2 Captions (Prerecorded), and the IASR gives no exception for it. Attach a synchronized captions file, which most platforms accept as a simple .vtt upload, and the criterion passes.

Now the retailer live-streams a launch event. Live captions fall under criterion 1.2.4, one of the two AODA exceptions, so the stream itself doesn't breach the IASR. Post the recording afterwards, however, and it becomes prerecorded content that needs captions like any other video. The line between the two trips people up constantly.

AODA mistakes Ontario organizations keep repeating

The recurring failures are less about bad intent than about misreading scope:

Assuming AODA is a physical-premises law and web accessibility is optional. Section 14 has been fully in force since 2021.
Stretching the legacy exemption over refreshed pages. Updating or republishing a page resets the clock; only untouched pre-2012 content qualifies.
Treating the two media exceptions as covering all captions. Prerecorded video still requires them at Level A.
Passing the website audit while the compliance report goes unfiled. The reporting duty starts at 20 employees.
Keeping no training records. Training happened, but without records it can't be demonstrated to an auditor.

Staying ahead of AODA obligations with less effort

Three shortcuts that are actually sound.

Scan against WCAG 2.1 AA rather than 2.0: the newer set contains every 2.0 AA criterion plus a few more, so passing 2.1 satisfies the IASR requirement with margin to spare. Put the reporting cycle in the same calendar as your fiscal deadlines so it's owned, not remembered. And save a dated copy of the checklist after each review session. The PDF export is dated and names the organization type you selected, which helps when you prepare your compliance report; Markdown and CSV copies work too. Exports include only the items shown for your selected type.

Pairing the AODA checklist with the WCAG toolset

Ontario rules, shared tooling.

The website items on this checklist run on the Website Accessibility Scanner, which tests WCAG 2.1 AA across your site and exports the evidence. Spot fixes verify quickly in the WCAG Accessibility Checker, and the manual criteria live in the WCAG Compliance Checklist. For a public accessibility page with a feedback route, the Accessibility Statement Generator produces the public-facing piece. Organizations also operating in the US should compare notes with the ADA Website Compliance Checklist, since the two regimes reward the same underlying fixes.

Try it now

Open AODA Compliance Checklist

The tool is one click away. No sign up, no upload, no payment.

Open AODA Compliance Checklist

Write a review