AODA compliance for Ontario websites: what businesses need to know

What AODA is

The Accessibility for Ontarians with Disabilities Act (AODA) is provincial legislation that came into force in 2005 with the goal of making Ontario fully accessible by 2025. It establishes accessibility standards across five areas: customer service, information and communications, employment, transportation, and the built environment.

For websites, the relevant area is information and communications. The AODA empowers the Ontario government to establish and enforce accessibility standards for how information is made available — including digital information on websites.

AODA applies to both the public sector (government, hospitals, schools, universities) and the private sector (businesses and non-profits). The requirements and timelines differ depending on the size and type of organisation, but most Ontario businesses with a website are subject to some form of AODA web accessibility requirement.

The IASR: where website requirements come from

The specific web accessibility requirements come from Ontario Regulation 191/11, the Integrated Accessibility Standards Regulation (IASR), specifically the Information and Communications Standards within it. These standards reference WCAG 2.0 — the Web Content Accessibility Guidelines published by the W3C — as the technical standard that websites must conform to.

This is the key link to understand: AODA does not define its own list of web accessibility requirements. Instead, it legally mandates conformance with WCAG 2.0 Level AA, meaning the detailed technical requirements are those defined in the WCAG standard. WCAG 2.0 Level AA has 38 success criteria covering things like text contrast, keyboard navigation, alternative text for images, captions for video, and clear page structure.

Who AODA applies to

AODA applies to any organisation that provides goods, services, or facilities in Ontario and that has at least one employee in Ontario. This covers the vast majority of Ontario businesses with a public-facing website.

The requirements are tiered by organisation size and type. Large organisations (50 or more employees) have had stricter requirements and earlier deadlines than small organisations (1 to 49 employees). The public sector has had requirements apply earlier than the private sector.

Sole proprietors with no employees are technically outside AODA's scope — the Act applies to organisations with employees. But even without AODA, the Ontario Human Rights Code applies to all businesses regardless of size (more on this below).

What WCAG 2.0 Level AA actually requires

WCAG 2.0 Level AA is the standard AODA mandates. It organises requirements into four principles — websites must be Perceivable, Operable, Understandable, and Robust — and sets success criteria at three levels (A, AA, AAA). AODA requires Level AA conformance, which means all Level A and Level AA criteria must be met.

The most commonly cited requirements at Level AA include: text must have a contrast ratio of at least 4.5:1 against its background (or 3:1 for large text); all functionality must be operable by keyboard without a mouse; images must have descriptive alternative text; form inputs must have visible labels; videos must have captions; pages must have descriptive titles; and heading structure must be logical and hierarchical.

Many of these requirements are also good web design practice regardless of legal obligation — a logical heading structure helps everyone navigate content, and high contrast text is easier for everyone to read, not just people with low vision. Accessibility and usability overlap substantially.

Compliance deadlines

The IASR set phased compliance deadlines for web content, and those deadlines have passed for most businesses. For private sector organisations with 50 or more employees, new and significantly refreshed web content was required to meet WCAG 2.0 Level AA by January 1, 2021. For smaller private sector organisations (1 to 49 employees), the equivalent deadline was January 1, 2021 as well for new content, though existing content published before January 1, 2012 is exempt.

In practice: if your website was built or significantly updated after 2014, its content is expected to conform to WCAG 2.0 Level AA under AODA. "Significantly updated" means substantive redesigns or content overhauls, not routine text edits.

The Ontario government has acknowledged that full compliance across the province has not been achieved, and enforcement has been uneven. But the legal requirement exists and the deadlines have passed.

Enforcement and penalties

AODA is enforced by the Accessibility Directorate of Ontario. Enforcement mechanisms include compliance audits, orders to comply, and administrative monetary penalties. Corporations can be fined up to $100,000 per day for contravening the AODA or its regulations. Individuals (including directors and officers) can be fined up to $50,000 per day.

Enforcement has focused primarily on larger organisations and the public sector, and active penalties against small businesses for web accessibility failures have been rare. However, the government has signalled an intent to increase enforcement, accessibility audits of private sector websites do occur, and the exposure exists.

More practically: individuals with disabilities can file complaints under the Ontario Human Rights Code when a website is inaccessible to them, which can lead to Human Rights Tribunal proceedings and remedies including damages and mandatory remediation. Human Rights Code complaints are more commonly used by individuals than AODA enforcement, and they carry their own risk.

The Ontario Human Rights Code: what AODA leaves out

The Ontario Human Rights Code prohibits discrimination on the basis of disability in services, goods, and facilities — and this prohibition applies to all businesses regardless of size, including sole proprietors. A website that is inaccessible to someone with a disability can constitute a barrier to service access, which may amount to discrimination under the Code.

The Human Rights Code does not specify WCAG compliance as a requirement the way AODA does. Instead, it establishes a duty to accommodate to the point of undue hardship. In practice, courts and tribunals have found that meeting WCAG 2.0 Level AA is strong evidence that a web accessibility duty to accommodate has been fulfilled. Non-conformance with WCAG is strong evidence in the other direction.

This means that even a business outside AODA's scope (a sole proprietor without employees, for example, or a business in another province serving Ontario customers) may have Human Rights Code obligations around web accessibility. The legal landscape is broader than AODA alone.

Common AODA failures on business websites

In accessibility audits of Ontario business websites, the same failures appear repeatedly. Images without alternative text — every meaningful image needs an alt attribute describing what it shows, and purely decorative images need an empty alt="" so screen readers skip them.

Insufficient colour contrast is one of the most common failures. Text that looks fine to someone with typical vision may be unreadable for someone with low vision or colour blindness. The 4.5:1 minimum ratio for normal text needs to be checked with a contrast tool, not estimated visually.

Form fields without labels are a widespread problem. A placeholder inside an input field is not a label — it disappears when the user starts typing and does not meet the WCAG requirement. Every input needs a visible <label> element properly associated with it.

Videos without captions exclude deaf and hard-of-hearing users. If you embed YouTube videos on your site, YouTube has auto-caption capabilities that help but should be reviewed for accuracy. Custom video players need caption track support.

Poor keyboard navigation affects users who cannot use a mouse. Dropdown menus that only work on hover, modals that trap keyboard focus, and custom interactive elements that are not reachable by Tab are all common keyboard accessibility failures.

What to do if your site is not compliant

Start with a baseline audit. Free tools like the WAVE Web Accessibility Evaluator (wave.webaim.org) or the axe browser extension will surface many common failures automatically. Run these on your key pages — home, services, contact, and any page with a form or video.

Prioritise the issues that block access entirely: missing form labels, images with no alt text, videos with no captions, and content that is completely keyboard-inaccessible. These are the failures most likely to prevent someone with a disability from using your site at all. Colour contrast and heading structure can be addressed in a second pass.

If you use WordPress, accessibility plugins like WP Accessibility can patch some common issues, but they are not a substitute for building accessibility in. A plugin can add a skip link and improve focus styles; it cannot add alt text to images you uploaded without it or fix a contact form with unlabelled fields. The fixes need to go into the content and templates themselves.

If you are rebuilding or significantly updating your site, commission an accessibility review as part of the build, not after. Retrofitting accessibility into a completed website is more expensive than building it in from the start. Any web developer doing Ontario business website work should be building to WCAG 2.0 Level AA as a baseline requirement.