The Accessibility for Ontarians with Disabilities Act (AODA) is a provincial law passed in 2005 with an ambitious goal: to make Ontario fully accessible to people with disabilities. Unlike some accessibility laws that rely on courts to define what compliance looks like, the AODA takes a standards-based approach. It sets out specific, enforceable accessibility standards — including detailed requirements for websites and web content — that organizations operating in Ontario must meet by fixed deadlines.
For website owners, the most important piece of the AODA is the Integrated Accessibility Standards Regulation (IASR), which spells out exactly which organizations must make their sites accessible and to what technical standard. The short version: if your organization has 50 or more employees in Ontario, or you're a public sector organization, your public-facing websites and web content are required to conform to WCAG 2.0 Level AA, and that requirement has been in force since January 1, 2021.
This guide walks through who the AODA applies to, what it actually requires for digital properties, how enforcement works, and the practical steps to get — and stay — compliant.
WCAG 2.0 AA is the legal standard
The AODA explicitly requires websites to conform to WCAG 2.0 Level AA (with narrow exceptions for live captions and pre-recorded audio description), making it one of the few laws that names a specific technical benchmark.
Applies at 50+ employees
Private and non-profit organizations with 50 or more employees in Ontario, plus all public sector organizations, must meet the web accessibility requirements. Smaller organizations have lighter obligations but are still covered by the Act.
Deadlines have already passed
The full WCAG 2.0 AA requirement for websites took effect on January 1, 2021. If your covered organization's site isn't conformant today, you're out of compliance — not ahead of a deadline.
Real financial penalties
The AODA authorizes fines of up to $100,000 per day for corporations and up to $50,000 per day for individuals and directors, alongside administrative penalties for issues like failing to file compliance reports.
What the AODA is and why it exists
The AODA became law in 2005, building on the earlier Ontarians with Disabilities Act of 2001. Its stated purpose was to achieve an accessible Ontario by 2025 by developing, implementing and enforcing accessibility standards across five areas: information and communications, employment, transportation, design of public spaces, and customer service.
Web accessibility falls under the Information and Communications standard within the IASR. That standard treats your website the same way the law treats a physical storefront: it's a place where you serve the public, and people with disabilities are entitled to use it. Roughly one in five Canadians has a disability, so this is far from an edge case — it's a meaningful share of your customers, applicants and users.
Who must comply
The AODA applies to every organization in Ontario — government, private business, and non-profit — that has at least one employee in the province. Obligations scale with organization size, and the web accessibility requirements specifically target larger organizations.
- Government of Ontario and the Legislative Assembly: the strictest requirements and earliest deadlines.
- Designated public sector organizations (municipalities, universities, colleges, school boards, hospitals): must meet WCAG 2.0 AA for websites and web content.
- Private and non-profit organizations with 50+ employees in Ontario: must make websites and web content published after January 1, 2012 conform to WCAG 2.0 AA.
- Organizations with 20+ employees: must file accessibility compliance reports with the province on a recurring cycle, even though the web standard itself applies at the 50-employee threshold.
- Organizations with fewer than 50 employees: exempt from the WCAG website requirement, but still subject to other AODA obligations such as accessible customer service and accessible formats on request.
What the law requires for websites
The IASR requires covered organizations to make their internet websites and web content conform to WCAG 2.0 Level AA. There are two carve-outs: success criterion 1.2.4 (live captions) and 1.2.5 (pre-recorded audio descriptions) are not required. The requirement applies to sites and content published after January 1, 2012; significantly refreshed sites are also captured.
In practice, WCAG 2.0 AA means things like: text alternatives for images, captions on pre-recorded video, sufficient colour contrast, full keyboard operability, clear focus indicators, properly labelled forms, logical heading structure, and content that works with screen readers. It covers web applications and documents posted on your site (like PDFs), not just marketing pages.
Beyond the website rule, the Information and Communications standard also requires organizations to provide accessible formats and communication supports on request, and to make feedback processes (contact forms, surveys, complaint channels) accessible.
How AODA relates to WCAG
WCAG — the Web Content Accessibility Guidelines from the W3C — is the technical yardstick the AODA points to. The law currently references WCAG 2.0, which was published in 2008, while the W3C has since released WCAG 2.1 and 2.2 with additional criteria covering mobile use, low vision, and cognitive accessibility.
Most accessibility professionals recommend building to WCAG 2.1 or 2.2 Level AA even though the AODA only mandates 2.0 AA. The newer versions are backwards-compatible — if you meet WCAG 2.2 AA, you meet 2.0 AA automatically — and aligning with the current standard also positions you well for other laws you may be subject to, such as the ADA in the United States or the European Accessibility Act, which lean on newer WCAG versions.
Enforcement and penalties
The AODA is enforced by the Ontario government rather than through private lawsuits. Enforcement tools include mandatory accessibility compliance reports, desk audits, inspections, director's orders, and monetary penalties. Under the Act, corporations can face fines of up to $100,000 per day for major offences, and individuals or unincorporated organizations up to $50,000 per day. Administrative penalties can also be levied for failures like not filing a compliance report.
Historically, day-to-day enforcement has leaned on compliance reporting and audits rather than maximum fines, and Ontario's own reviews of the Act have criticized enforcement as too light. But the legal exposure is real, the reporting obligation is routinely checked, and an inaccessible website can also invite human rights complaints under the Ontario Human Rights Code, which operates independently of the AODA.
Practical steps to comply
AODA compliance is achievable with a structured approach. Because the standard is explicitly WCAG 2.0 AA, you have a concrete checklist to work against rather than a vague legal duty.
- Audit your site against WCAG 2.0 AA (ideally 2.1/2.2 AA) using a combination of automated scanning and manual testing with a keyboard and screen reader.
- Fix the high-impact issues first: missing alt text, poor contrast, keyboard traps, unlabelled form fields, and videos without captions.
- Check your documents too — PDFs, Word files and slide decks posted on your site are web content under the AODA.
- Build accessibility into your workflow so new pages, components and campaigns ship accessible instead of being retrofitted. Tools like AccessWiser can help you monitor issues and improve accessibility continuously, though no tool on its own guarantees legal compliance — remediation and testing still matter.
- File your accessibility compliance report on time if you have 20 or more employees, and keep records of your accessibility policies and training.
- Provide an accessible feedback channel and respond to accessible-format requests promptly.
Frequently asked questions
Does the AODA apply to my company if we're based outside Ontario?
The AODA applies to organizations with employees in Ontario. If you have no employees in the province, the law doesn't directly bind you — but if you serve Ontario customers, accessible design is still wise, and other laws (like the ADA for U.S. audiences or the European Accessibility Act for the EU) may apply to you instead.
Which WCAG version does the AODA require?
WCAG 2.0 Level AA, excluding success criteria 1.2.4 (live captions) and 1.2.5 (pre-recorded audio descriptions). Meeting the newer WCAG 2.1 or 2.2 at Level AA automatically satisfies this, so most teams target the current version.
My business has fewer than 50 employees. Do I need an accessible website?
The specific WCAG 2.0 AA website requirement applies at 50+ employees (and to all public sector organizations). Smaller organizations still have other AODA duties, such as accessible customer service and providing accessible formats on request, and accessibility complaints can also be raised under the Ontario Human Rights Code regardless of company size.
What happens if I don't comply?
You could face government audits, orders and monetary penalties — the Act allows fines up to $100,000 per day for corporations. In practice, enforcement often starts with compliance reporting checks and audits, but non-compliance also exposes you to human rights complaints and reputational damage.
Was everything supposed to be accessible by 2025?
The AODA set 2025 as the target for an accessible Ontario, and all of the currently published deadlines — including the January 1, 2021 website requirement — have now passed. That means covered organizations should already be conformant; independent reviews have found the province fell short of the full 2025 goal, but the legal obligations for websites remain in force.
This article is provided for general information about accessibility regulations and standards. It is not legal advice — consult a qualified professional about your specific compliance obligations.