Ontario AODA compliance deadline: December 31, 2026Check your risk
PassProof.
← Guides

AODA Compliance for Ontario Businesses (2026): The Complete Guide

What the AODA actually requires of Ontario businesses in 2026 — who must comply, the Dec 31 deadline, WCAG level, penalties, and how to get compliant without an overlay.

If you run a business in Ontario, "AODA" has probably landed in your inbox more than once this year — usually with a scary number attached. This guide cuts through it. Here's what the law actually requires, who it applies to, what the real risks are, and how to get compliant in a way that holds up.

What is the AODA?

The Accessibility for Ontarians with Disabilities Act (AODA) is provincial law aimed at making Ontario accessible by 2025. For most businesses, the part that matters is the Integrated Accessibility Standards Regulation (IASR) and its Information and Communications standard — which is what brings your website into scope.

The technical benchmark the IASR points to is the Web Content Accessibility Guidelines (WCAG).

Who must comply (by employee count)

Headcount drives your obligations (count full-time, part-time, seasonal, and contract staff):

  • 1–19 employees: Exempt from filing the compliance report. But you're still exposed under the Ontario Human Rights Code and must provide accessible formats on request.
  • 20–49 employees: Must file an Accessibility Compliance Report (ACR). The next deadline is December 31, 2026.
  • 50+ employees (and the public sector): File the ACR plus meet WCAG 2.0 Level AA for public websites and content, maintain documented accessibility policies, and keep a multi-year plan.

The deadline that matters

December 31, 2026 — the next ACR filing deadline for organizations with 20+ employees. The public-sector deadline (December 31, 2025) has already passed. Most private businesses haven't started. Filing is a legal obligation, done through the Ontario government's Accessibility Compliance Reporting portal.

What WCAG level is required?

  • The legal floor (IASR): WCAG 2.0 Level AA, minus two items (1.2.4 live captions, 1.2.5 audio description).
  • Best practice (recommended, not law): WCAG 2.1 / 2.2 AA — these add mobile and cognitive accessibility. At PassProof we build to 2.2 AA so you're future-proof, while being clear that 2.0 AA is the legal minimum.

What about the penalties?

You'll see "up to $100,000/day for corporations" and "$50,000/day for directors, personally." Those are the statutory maximums on conviction — and, as of 2026, they have never actually been applied. Real administrative penalties have run in the hundreds to low thousands, under a progressive process: notice of non-compliance → director's order → monetary penalty → (only for severe, repeated cases) prosecution.

So the honest picture: the headline fine is a backstop, not the everyday risk. The everyday risk is the deadline, the complaint path below, and reputational/revenue loss.

The real lawsuit path: the Human Rights Code

Here's the nuance most articles miss: the AODA doesn't let an individual sue you directly. The actual litigation exposure runs through the Human Rights Tribunal of Ontario (HRTO) — a person can file a disability-discrimination complaint about an inaccessible service. Defending even one commonly costs $30,000+, win or lose. Sell into the U.S.? You also carry ADA exposure.

A recent audit + a remediation plan + evidence you've started fixing the code is what shifts you from "negligent" to "good-faith" — and that materially reduces both the odds and the cost of a complaint.

Why an "accessibility widget" doesn't solve this

Overlay widgets (accessiBe, UserWay, AudioEye) promise instant compliance. They don't deliver it: automated tools catch only 30–40% of WCAG issues, courts don't accept overlays as a defense, and in 2025 the FTC fined accessiBe $1M for overstating what its widget does. More on that here and the lawsuit data here.

How to actually get compliant (4 steps)

  1. Audit — automated and manual testing (keyboard + screen readers) against WCAG 2.2 AA. What it costs in Ontario.
  2. Remediate — fix the real source code, not a cosmetic layer. Overlay vs remediation.
  3. Document — keep an audit report + remediation plan (your good-faith evidence). Note: ACR ≠ VPAT.
  4. File your ACR before December 31, 2026. Step-by-step guide.

And you may not have to pay for it out of pocket — Ontario businesses can often fund the work through CSBFP and CanExport.

See where your site stands — free

The PassProof Report scans your site against Ontario's AODA/WCAG rules in ~30 seconds: your top failures, whether you've got an overlay and what it's missing, what applies to your size, and a fixed-price path.

👉 Get your free PassProof Report


PassProof is a remote-first accessibility-engineering studio serving Ontario. This is accessibility-engineering guidance, not legal advice; we work alongside your counsel.

See where your site stands — free

Get your top WCAG failures, any overlay we detect, what applies to a company your size, and a fixed-price path — in about 30 seconds.