AODA Compliance
The Accessibility for Ontarians with Disabilities Act (AODA) requires designated public sector organizations and organizations with 50 or more employees in Ontario to make their public websites and web content meet WCAG 2.0 Level AA.
Ontario, Canada
WCAG 2.0 Level AA Required
The final AODA web deadline was January 1, 2021: covered organizations' public websites must now meet WCAG 2.0 Level AA
In July 2026 Compliable measured 7,485 page scans across 1,045 Ontario public-sector organizations: at least 89.4% of the 884 AODA-bound organizations show at least one detectable WCAG 2.0 Level AA violation.
Who must comply?
The AODA web rule applies to designated public sector organizations and to businesses and non-profits with 50 or more employees in Ontario
Private Sector
50+ employees in Ontario
- WCAG 2.0 Level AA compliance
- Accessible feedback processes
- Accessibility policies and plans
- Accessible employment practices
Public Sector
Designated public sector organizations
- WCAG 2.0 Level AA compliance
- Multi-year accessibility plans
- Accessible procurement
- Accessibility training for staff
Non-Profit
50+ employees in Ontario
- WCAG 2.0 Level AA compliance
- Accessible customer service
- Accessible formats on request
- Accessibility compliance reports
Compliance timeline
January 1, 2014
New public websites, and significantly refreshed websites, must meet WCAG 2.0 Level A
Applies to: Designated public sector organizations and organizations with 50+ employees in Ontario
January 1, 2021
All public websites and web content published after January 1, 2012 must meet WCAG 2.0 Level AA (except live captions and pre-recorded audio descriptions)
Applies to: Designated public sector organizations and organizations with 50+ employees in Ontario
Ongoing
New and updated web content must continue to meet WCAG 2.0 Level AA
Applies to: Designated public sector organizations and organizations with 50+ employees in Ontario
WCAG 2.0 Level AA requirements
AODA requires compliance with WCAG 2.0 Level AA, which is based on four principles
Perceivable
- Text alternatives for non-text content
- Captions and audio descriptions for media
- Content is adaptable and distinguishable
- Sufficient color contrast (4.5:1 minimum)
Operable
- All functionality available via keyboard
- Users have enough time to read content
- No content that causes seizures
- Easy navigation and wayfinding
Understandable
- Text is readable and understandable
- Pages operate in predictable ways
- Users can avoid and correct errors
- Consistent navigation and identification
Robust
- Compatible with assistive technologies
- Valid HTML and proper ARIA usage
- Name, role, and value exposed properly
- Markup that parses without errors
Non-compliance penalties
The AODA allows administrative penalties, and on conviction for an offence, fines for each day or part of a day the offence continues
Source: Accessibility for Ontarians with Disabilities Act, 2005, and the Integrated Accessibility Standards Regulation (O. Reg. 191/11). This is general information, not legal advice.
Exemptions & exceptions
- Organizations with fewer than 50 employees (limited requirements)
- Content published before January 1, 2012 (unless republished)
- Websites and web content the organization does not control directly or through a contractual relationship
- WCAG 2.0 success criteria 1.2.4 (live captions) and 1.2.5 (pre-recorded audio descriptions)
- Cases where meeting the requirement is not practicable, as set out in the regulation
- Products and product labels, unless specifically provided for
Compliance reporting
What to Report
- • Accessibility policies and plans
- • Multi-year accessibility plan progress
- • Training records for employees
- • Accessible formats and communication supports
- • Website and web content accessibility
Filing Requirements
- • Designated public sector: compliance report every 2 years
- • Businesses and non-profits with 20+ employees: every 3 years
- • File through the Government of Ontario online reporting tool
- • Public sector: annual status reports on the multi-year plan
- • Maintain an accessible feedback process
Work toward AODA compliance
Compliable scans your pages in a real browser with the open-source axe-core engine and maps each finding to WCAG 2.0 Level AA and the AODA. Automated scanning finds part of all barriers; pair it with manual review to cover the rest.