AODA Compliance for Websites — Ontario Accessibility Guide

What is AODA?

AODA stands for the Accessibility for Ontarians with Disabilities Act, 2005. It is a provincial law enacted in Ontario to create, implement, and enforce accessibility standards across key areas of daily life such as customer service, employment, transportation, information and communications, and the built environment. The legal purpose is to remove and prevent barriers that affect people with disabilities. The Act is not a voluntary framework, and it applies to government, public sector organizations, businesses, and non-profits based on how the standards are written.

The law also set a province-wide goal: accessibility for Ontarians with disabilities on or before January 1, 2025. That date is a milestone written into the statute, but it does not mean obligations ended in 2025. In practice, organizations are still required to meet standards, maintain accessible processes, and file required reports after 2025. Compliance under AODA is ongoing and operational, not one-time.

For websites, AODA matters because digital content is treated as part of information and communications accessibility. If your website is used to deliver information, services, transactions, forms, or customer support, web accessibility barriers can create legal and operational exposure. Organizations that treat accessibility as a release gate and governance control perform much better than organizations that treat it as a post-launch cleanup task.

Who must comply with AODA?

AODA applies broadly, but obligations vary by organization type and employee count. At a high level, designated public sector organizations are covered by AODA standards, and private/non-profit organizations in Ontario are covered as well. Some requirements, including specific web standards and reporting obligations, apply when an organization reaches certain size thresholds.

For web accessibility under IASR Section 14, designated public sector organizations and large organizations must make public internet websites and web content conform to WCAG 2.0 requirements according to the AODA schedule. Under Ontario guidance, “large organizations” include private-sector and non-profit organizations with 50 or more employees. Smaller organizations still have accessibility obligations under other AODA standards even if a specific website provision or reporting trigger differs.

Organization type	AODA coverage	Website standard impact	Reporting impact
Designated public sector	Covered by AODA and IASR	Public websites/web content must meet WCAG 2.0 Level AA schedule requirements	Must file accessibility compliance reports on the public-sector cycle
Private and non-profit, 50+ employees	Covered by AODA and IASR large-organization requirements	Public websites/web content must meet WCAG 2.0 Level AA schedule requirements	Included in the business/non-profit compliance reporting program
Private and non-profit, 20-49 employees	Covered by AODA with fewer large-organization requirements	Website rules differ by requirement scope; broader AODA duties still apply	Must file an accessibility compliance report every three years
Private and non-profit, fewer than 20 employees	Covered by applicable AODA duties	No general three-year report filing requirement, but legal obligations remain	No regular report filing trigger under current Ontario guidance

Two practical mistakes are common: first, assuming website rules only matter to government bodies; second, assuming fewer obligations means no obligations. Both assumptions are risky. AODA enforcement is based on legal requirements that apply to your organization profile, and those requirements still need active governance, documentation, and ongoing remediation.

What are the WCAG requirements under AODA?

Under the Information and Communications Standards in the IASR, Ontario requires covered organizations to make public websites and applicable web content conform with WCAG 2.0. The current requirement for designated public sector organizations and large organizations is WCAG 2.0 Level AA, with limited stated exceptions in the regulation and guidance, including the live captions and prerecorded audio description criteria referenced by Ontario’s public guidance.

This is important because many global accessibility programs now target WCAG 2.2 AA or WCAG 2.2 AA, while Ontario’s legal language for AODA web compliance remains based on WCAG 2.0 Level AA for the IASR requirement. In practice, many organizations use a “meet legal minimum, design to newer standard” approach. That means they ensure WCAG 2.0 AA legal coverage while implementing broader criteria from later WCAG versions to reduce user friction and future-proof design systems.

To operate this requirement effectively, organizations should apply WCAG checks across templates, dynamic components, forms, media, and user journeys. Compliance failures often come from recurring implementation patterns rather than single pages. A robust program includes component-level accessibility standards, content authoring rules, QA checklists, and change-management controls so regressions are caught before release.

What are the compliance deadlines?

AODA web requirements have phased deadlines in the IASR, and those phase dates have already passed for many organizations. The most important point in 2026 is that organizations are expected to already be conforming where requirements apply. For example, Ontario guidance states that as of January 1, 2021, designated public sector organizations and businesses/non-profits with 50 or more employees must make public websites accessible under the WCAG 2.0 AA rule framework.

In addition to implementation deadlines, report deadlines are active compliance obligations. Ontario’s Accessibility Compliance Reporting Portal guidance currently states that the reporting deadline for businesses and non-profits with 20 or more employees is December 31, 2026. For designated public sector organizations, the latest posted cycle shows a December 31, 2025 deadline, and organizations that missed that date are still required to file the 2025 report.

Deadline management should be treated as a legal operations function. Teams should track report cycles, assign an accountable certifier, gather evidence before filing, and avoid end-of-cycle scrambling. Filing late or failing to file can trigger compliance escalation even when some accessibility work has been done, because reporting itself is a separate statutory obligation.

What are the penalties for non-compliance?

AODA enforcement can include inspections, audits, compliance orders, administrative penalties, and offence-level prosecution. Ontario’s IASR framework contains administrative penalty schedules, and in serious cases the director can treat penalty amounts as daily penalties up to statutory maximums. Separately, the AODA offence provisions include maximum fines that are frequently cited in compliance guidance and legal summaries.

The high-end offence amounts are significant: up to $100,000 per day for corporations and up to $50,000 per day for individuals, including directors or officers in certain circumstances. These are maximum exposure figures, not automatic default penalties, but they are material enough to justify executive-level governance. Even below maximum fines, enforcement action can create legal costs, operational disruption, remediation rush costs, and reputational damage.

Organizations should also understand that non-compliance risk is cumulative. A website issue, a missed report, weak documentation, and repeated failures to remediate can compound enforcement outcomes. The strongest risk reduction strategy combines regular testing, tracked remediation, documented policies, staff training, and timely filing of required reports.

What is the IASR?

IASR stands for the Integrated Accessibility Standards Regulation, formally Ontario Regulation 191/11 under AODA. It is the regulation that operationalizes many of the law’s core standards and timelines. Rather than leaving accessibility requirements at a high-level principle, the IASR defines concrete obligations across information and communications, employment, transportation, and design of public spaces.

For website teams, IASR matters because it contains the legal web accessibility section (Section 14) that references WCAG 2.0 conformance levels and implementation schedules. It also interacts with adjacent obligations such as accessible formats and communication supports, accessibility policies, training, and other governance measures that affect how digital services are delivered in practice.

Think of AODA as the statute-level framework and IASR as the implementation-level rulebook. If an organization only reads high-level summaries and skips the regulation text, it can miss scope details, exceptions, and scheduling language that determine real compliance status.

How does AODA relate to WCAG?

WCAG is the technical web accessibility standard created by W3C, while AODA is Ontario law. AODA does not replace WCAG; instead, the IASR incorporates WCAG 2.0 Level A/AA requirements into enforceable legal obligations for covered organizations. In other words, WCAG tells teams what accessible web content should look like technically, and AODA tells covered Ontario organizations when and where that standard is legally required.

This relationship is why accessibility programs need both legal and technical ownership. Legal/compliance teams track obligations, deadlines, and reporting, while product, design, and engineering teams implement the technical criteria in code and content workflows. When either side operates alone, organizations either miss requirements or fail to execute them in production systems.

A practical approach is to map each applicable WCAG criterion to component libraries, CMS authoring patterns, QA automation, and manual test scripts. That creates a repeatable control system rather than a point-in-time audit exercise. It also makes report certification easier because evidence is already organized in a structured way.

Do organizations outside Ontario need to comply?

AODA is a provincial Ontario law, so direct legal obligations are tied to whether the organization is within the Act’s scope. An organization headquartered outside Ontario may still face AODA obligations if it operates in Ontario in ways that bring it under the relevant standards. Scope depends on organizational facts, structure, and legal interpretation, so cross-border organizations should validate applicability with qualified legal counsel.

Even when AODA does not directly apply, many organizations still adopt AODA-aligned or WCAG-aligned standards as an operating baseline. This reduces fragmentation across jurisdictions and supports broader compliance with other laws such as ADA-focused U.S. programs, European accessibility frameworks, and public-sector procurement rules. In multi-region environments, the cost of multiple accessibility standards is usually higher than setting one strong baseline and maintaining it consistently.

The safest operational position is to treat accessibility as a core product quality requirement regardless of jurisdiction and then layer legal obligations by market. That approach lowers legal risk, improves usability, and reduces expensive retrofits when regulations evolve.

How LEWCA helps

LEWCA helps organizations manage AODA-related website risk by scanning WordPress sites for accessibility issues tied to WCAG success criteria and recurring implementation patterns. This gives teams a faster way to identify barriers that can affect legal compliance and user access. Instead of relying on infrequent manual checks, teams can use ongoing monitoring to catch regressions as themes, plugins, and content change.

LEWCA also supports remediation workflows by helping teams prioritize issues and track progress across releases. That is useful for internal governance, leadership reporting, and audit readiness. You can review the platform capabilities at /features/ and compare options at /pricing/.