My Tool Studio
WCAG

AODA Compliance Checklist

Ontario's accessibility law comes with concrete web obligations, and this aoda compliance checklist tracks all of them across four groups: who must comply, the technical standard, organizational duties, and reporting. The iasr web requirements have bound private and non-profit organizations with 50 or more employees, plus every public sector organization, since January 1, 2021: covered websites must meet WCAG 2.0 Level AA, with exemptions only for live captions and prerecorded audio description. Compliance officers and web leads pull up an ontario accessibility checklist like this one ahead of a filing deadline or after a redesign, because the penalties for getting it wrong can reach six figures per day.

Always freeNo sign upRuns in your browser

0 of 14 complete

0%

Progress is saved in your browser — close the tab and pick up where you left off.

1. Determine your obligations

0/3

2. Technical compliance

0/4

3. Organizational requirements

0/4

4. Reporting & maintenance

0/3

How to use

01

Confirm which obligations apply

The first group sorts you by size and sector: web content rules bind organizations with 50 or more employees and all public sector bodies, and pre-2012 legacy content is exempt unless requested.

02

Meet the technical standard

Group two covers scanning covered sites, remediating Level A and AA failures, making posted documents accessible, and captioning prerecorded video, the core of WCAG 2.0 AA under the IASR.

03

Handle policy, training, and reporting

The last two groups track your written accessibility policy, multi-year plan, staff training records, procurement duties, and Ontario's compliance report schedule. Export as Markdown or CSV.

Why AODA Compliance Checklist

Common questions

What do the aoda website requirements actually demand?
Covered public websites and web content must conform to WCAG 2.0 Level AA, a rule in force since January 1, 2021. Two success criteria are exempt: live captions (1.2.4) and prerecorded audio description (1.2.5). Everything else at A and AA applies.
Does the aoda compliance checklist cover duties beyond the website?
Yes, roughly half of it does. Beyond the technical items you'll find the written accessibility policy, the multi-year accessibility plan, an accessible feedback process, staff training on AODA and the Human Rights Code, and procurement obligations for public sector bodies.
How often are Ontario accessibility compliance reports due?
Businesses and non-profits with 20 or more employees file every three years, and public sector organizations file every two. The checklist's reporting group exists so the filing date never sneaks up on you.
Is scanning against WCAG 2.1 overkill for AODA purposes?
No, it's the practical shortcut. WCAG 2.1 AA contains everything in 2.0 AA plus additional criteria, so a site passing a 2.1 AA scan satisfies the IASR's 2.0 requirement automatically. Our scanner tests 2.1 AA for exactly this reason.
Can a 30-employee Ontario business skip the ontario accessibility checklist?
Not entirely. The web content rules in IASR section 14 apply from 50 employees up, but smaller organizations still carry customer service, feedback, and training obligations, and the reporting duty starts at 20 employees. The first checklist group sorts out which items apply to you.
What penalties back the iasr web requirements?
Corporations face fines of up to $100,000 per day of non-compliance, and directors and officers personally face up to $50,000 per day. Ontario also runs compliance audits, so the exposure isn't theoretical.
Do pre-2012 legacy pages need AODA remediation?
Legacy web content published before 2012 is exempt until someone requests it in an accessible format, at which point you must provide one. Content you redesign or republish loses the exemption, so treat any refresh as new content.

More WCAG tools

View all