AODA Website Compliance Guide 2026

Ontario's Accessibility for Ontarians with Disabilities Act has been on the books since 2005. For many organizations, the December 2026 compliance reporting deadline is the practical forcing function. Here is what the law requires, who it covers, and what you need to do.

What AODA Requires for Websites

The Integrated Accessibility Standards Regulation (IASR), O. Reg. 191/11, is the enforceable regulation under AODA that governs web accessibility. Section 14 of the IASR's Information and Communications Standard requires organizations to:

1. Make their websites and web content conform to WCAG 2.0 Level AA
2. Apply this requirement to all new websites and significantly refreshed web content
3. Apply this requirement to all existing web content where technically feasible

The technical standard is WCAG 2.0 Level AA, published by the World Wide Web Consortium (W3C). This standard covers four principles: Perceivable, Operable, Understandable, and Robust (often called POUR).

The IASR was enacted when WCAG 2.0 was the current standard. WCAG 2.1 was published in 2018 and WCAG 2.2 in 2023. While these newer versions are not yet the explicit legal requirement under AODA, building to WCAG 2.1 AA is widely recommended as future-proofing, since Ontario regulatory updates are expected to reference newer versions.

Reference: Ontario.ca/laws — Integrated Accessibility Standards Regulation O. Reg. 191/11

Who Must Comply

Public sector organizations: All Ontario government bodies, municipalities, school boards, hospitals, universities, public libraries, and any organization that is a public sector body under the AODA must comply with web accessibility requirements. This applies regardless of employee count. Private sector and non-profit organizations: Organizations with 50 or more employees must meet web accessibility standards. Organizations with fewer than 50 employees are not required to meet the web standard under the IASR, though they remain subject to the Ontario Human Rights Code, which prohibits discrimination on the basis of disability.

Note that employee count is based on all employees in Ontario, not just those who work on websites. A manufacturer with 200 production workers and a small website still falls under the 50+ threshold.

The December 2026 Compliance Reporting Deadline

AODA requires large private sector and non-profit organizations to file compliance reports with the Ontario government every three years. These reports are submitted online at ontario.ca/page/file-your-accessibility-compliance-report.

For many large private sector organizations, the next compliance report covers the period up to and including 2026, with a filing deadline of December 31, 2026. The compliance report asks organizations to confirm they have met their AODA obligations across all standards, including the web accessibility standard.

This is not a certification process. Ontario does not review every website. But the compliance report creates a legal record. If the organization files that it is in compliance and is subsequently found to have non-compliant websites, the consequences are more serious.

WCAG 2.0 AA: The Specific Requirements

Perceivable

Content must be presentable in ways all users can perceive:

• 1.1.1 Non-text content (Level A): All images must have text alternatives (alt text). Decorative images should have empty alt attributes.
• 1.3.1 Info and relationships (Level A): Information conveyed through presentation (headings, lists, form labels) must also be conveyed through the markup structure.
• 1.4.3 Contrast (minimum) (Level AA): Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text).
• 1.4.4 Resize text (Level AA): Text must be resizable to 200% without loss of content or functionality.

Operable

Users must be able to operate all interface components:

• 2.1.1 Keyboard (Level A): All functionality must be available using only a keyboard.
• 2.4.1 Bypass blocks (Level A): A mechanism must exist to skip navigation and repeated content (skip nav link).
• 2.4.2 Page titled (Level A): Every page must have a descriptive title.
• 2.4.3 Focus order (Level A): Keyboard focus must follow a logical order through the page.

Understandable

Content and interface must be understandable:

• 3.1.1 Language of page (Level A): The HTML lang attribute must declare the page language.
• 3.3.1 Error identification (Level A): Form input errors must be identified and described in text.
• 3.3.2 Labels or instructions (Level A): Form fields must have labels or instructions.

Robust

Content must be robust enough to work with current and future assistive technologies:

• 4.1.1 Parsing (Level A): HTML must have no duplicate IDs or broken markup that breaks assistive technology.
• 4.1.2 Name, role, value (Level A): UI components must have accessible names, roles, and states that assistive technologies can determine.

What an AODA Web Audit Covers

An automated web accessibility audit checks your pages against detectable WCAG criteria. Automated tools typically catch 30-50% of WCAG violations — primarily the structural and attribute-based issues that have clear pass/fail rules.

Common issues automated scanning finds:

• Missing or empty HTML lang attribute
• Images without alt text attributes
• Form inputs without associated labels
• Empty links (anchor tags with no text content)
• Missing skip navigation link
• Missing or empty page title
• Inputs that rely only on placeholder text for labels

Issues that require manual review:

• Whether alt text is actually meaningful (not just present)
• Whether color contrast meets the 4.5:1 ratio
• Whether keyboard navigation is logical and complete
• Whether focus indicators are visible
• Whether custom interactive components work with screen readers

For AODA compliance documentation purposes, organizations should conduct both automated scanning and manual review. Automated scanning provides a baseline; manual testing covers what automation cannot detect.

Filing Your AODA Compliance Report

The AODA compliance report for large private sector organizations asks whether your organization has met each of its AODA requirements. For web accessibility specifically, you are confirming that your websites and web content conform to WCAG 2.0 AA.

Before filing, you should:

1. Run automated scans of your primary domains and subdomains
2. Address any critical or serious violations found
3. Document the audit and remediation work you have completed
4. Ensure new content published during the report period also met the standard
5. Keep records of your accessibility efforts in case of future inspection

The Ontario government can conduct compliance audits and inspections. Organizations that have filed compliance reports but cannot demonstrate actual compliance face greater risk, since the filing itself establishes that the organization represented it was in compliance.

Penalties: What the Law Actually Says

The Accessibility for Ontarians with Disabilities Act, S.O. 2005, c. 11, sets maximum fines at:

• CAD $100,000 per day for corporations
• CAD $50,000 per day for individuals (including directors and officers of corporations)

These are maximums. The Ontario government uses a graduated enforcement approach — inspections and compliance orders before monetary penalties in most cases. However, the penalties demonstrate that the legislature intended AODA to be taken seriously.

Beyond the AODA itself, organizations with inaccessible websites may face human rights complaints under the Ontario Human Rights Code, which can result in compensation orders and systemic remedies.

Practical Next Steps

If your organization has not completed a web accessibility audit:

1. Run automated scanning on your primary website and key subdomains
2. Review the violations found, prioritizing critical and serious issues
3. Schedule development work to fix identified violations before the December 2026 reporting period
4. Conduct or commission manual keyboard and screen reader testing
5. Document the process and results for your compliance records

Run a free scan with OnePageAudit to establish your current compliance baseline. The scan checks for the most common WCAG 2.0 AA violations that AODA audits target and produces a score and violation list in under 60 seconds.

A full PDF report ($19) documents every violation with WCAG success criterion, severity, affected HTML, and fix instructions — the kind of documentation that supports both remediation planning and compliance record-keeping.

Related reading:

• Accessible Canada Act: What Your Website Needs
• Canadian Website Accessibility Laws: Complete Guide
• ADA Compliance Checker: How to Test Your Website