AODA compliance for Ontario businesses: a 2026 reality check
AODA's web-content rules have been law for years, but enforcement is sharpening. What Ontario businesses with 50+ employees actually need to do — and what's being audited.
AODA — the Accessibility for Ontarians with Disabilities Act — is the longest-standing provincial accessibility law in Canada. Its Integrated Accessibility Standards Regulation (IASR) requires public-facing websites and web content from organizations with 50+ employees in Ontario to conform to WCAG 2.0 Level AA.
Two things changed recently: enforcement budgets are up, and government procurement is asking for evidence rather than self-attestation.
Who's covered
- Government of Ontario, the Legislative Assembly, and designated public-sector organizations
- Private and non-profit organizations with 50+ employees that provide goods, services, or facilities in Ontario
- Educational institutions, libraries, and producers of educational materials
What the IASR actually requires (digital)
- 01All new public websites and web content must conform to WCAG 2.0 Level AA — note: the standard is technically 2.0; we recommend targeting 2.2 AA so you're forward-compatible with ACA, ADA, and EAA.
- 02Accessible feedback processes for the public to report barriers.
- 03An accessibility plan, posted publicly and reviewed at least every 5 years.
- 04Training for employees and volunteers on accessibility law and the Human Rights Code.
- 05Accessibility statements posted on your website.
Penalties (and how they're really applied)
IASR penalties run up to $100,000 per day for corporations. Historically, enforcement has favored compliance orders over fines, but that's shifted: the Accessibility Directorate now issues administrative monetary penalties more readily, and procurement gatekeeping (your enterprise customers asking for proof) has become a more common forcing function than direct enforcement.
A 90-day plan that actually closes the gap
- 01Weeks 1–2: Baseline audit on your top 5 public flows against WCAG 2.2 AA.
- 02Weeks 3–8: Remediation of critical and serious findings, plus design-system patches.
- 03Weeks 9–10: Publish/refresh your accessibility statement and feedback channel.
- 04Weeks 11–12: Train designers and engineers; bake checks into your release process.