WCAG & Accessibility·4 min read

AODA Web Accessibility Explained for Ontario Sites

Ontario put web accessibility into provincial law years before most jurisdictions worked up the nerve, and it backed the requirement with per-day fines. Here's aoda web accessibility explained 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 tool 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 exactly two carve-outs: 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: material published before 2012 is exempt until someone requests it in an accessible format. Redesign or republish a page, though, and it counts as current content with full obligations.

Who must comply with AODA, by headcount and sector

Count your employees first.

The who must comply with aoda question resolves along two axes. The web content rules bind private and non-profit organizations with 50 or more employees in Ontario, and every public sector organization regardless of size. Below 50 employees, the website rules don't apply, but AODA's customer service, feedback, and training duties still do, and any organization with employees in Ontario is inside the Act's general scope.

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 must submit accessibility compliance reports on Ontario's schedule, every three years, while public sector organizations file every two. The aoda reporting deadlines are the mechanism that turns quiet neglect into a formal problem, since filing falsely or not at all is its own violation.

Behind the report sits paperwork the checklist tracks group by group: a written accessibility policy for organizations with 50 or more employees, a multi-year accessibility plan reviewed at least every five years, training records covering staff and volunteers, and an accessible feedback process. The enforcement ceiling is serious: up to $100,000 per day for corporations and $50,000 per day for directors and officers.

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. Input: the video with no caption track. Under WCAG 2.0 AA that fails criterion 1.2.2 Captions (Prerecorded), and the IASR gives no exemption for it. Output: the same video with a synchronized captions file attached, 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 exemptions, 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. A redesign resets the clock; only untouched pre-2012 content qualifies.
Treating the two media exemptions 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 just 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 the older one, so passing 2.1 satisfies the IASR requirement with margin to spare, and it future-proofs you against standard updates. Put the reporting cycle in the same calendar as your fiscal deadlines so it's owned, not remembered. And export the checklist after each review session; dated Markdown or CSV snapshots double as the supporting documentation an Ontario compliance audit will ask about.

Pairing the AODA checklist with the WCAG toolset

Ontario rules, shared tooling.

The technical group of this checklist runs on the WCAG Accessibility Scanner, which tests 2.1 AA across your site and exports the evidence. Spot fixes verify quickly in the Instant Accessibility Checker, and the manual criteria live in the WCAG Compliance Checklist. Since AODA expects published policies and an accessible feedback route, the Accessibility Statement Generator produces the public-facing piece. Organizations also operating in the US should compare notes with the ADA 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