Accessibility Compliance Ontario: AODA, the Federal ACA, and What Applies to You

Ontario runs on AODA. A short list of federally regulated industries run on a separate federal law with its own deadlines. Mixing the two up is the most common mistake I see.

Which accessibility law actually applies to my Ontario business, AODA or the federal Accessible Canada Act?

For the overwhelming majority of Ontario businesses, the answer is AODA, not the federal Accessible Canada Act (ACA), and the test isn’t where your business is headquartered. It’s whether you’re federally regulated.

Ontario’s provincial law, AODA, governs any business or organization operating in Ontario that isn’t federally regulated: retailers, clinics, law firms, restaurants, manufacturers, most nonprofits, municipalities, school boards, hospitals. The federal ACA only reaches a specific, narrow list of industries Parliament regulates directly: banks, telecom and broadcast carriers, airlines and other federally licensed transportation, and the federal government itself. If you’re not in one of those industries, the ACA simply doesn’t touch you, regardless of how large your business is.

Get this wrong in either direction and you’ll waste real effort. A 40-person Ontario law firm doesn’t need to track ACA deadlines. A federally regulated telecom subsidiary based in Ontario doesn’t get to treat AODA’s 50-employee website threshold as its only obligation. It answers to the ACA on top of provincial rules. When in doubt, the industry test decides it, not the province you happen to operate in.

AODA vs. the Accessible Canada Act: side by side

Line the two laws up and the differences that actually matter come into focus fast.

Notice the gap on the website-conformance row. Ontario businesses that owe a website duty have owed it since 2021. Federally regulated organizations get until December 5, 2028 for the equivalent public-facing website requirement, a longer runway, on a stricter underlying standard.

Does my sector change who has to comply under AODA?

Yes, and most explainers, including the pillar guide on this site, only walk through one of the two tests that decide it: the 50-employee private-sector threshold. There’s a second one.

Per Ontario’s own guidance on making websites accessible, the WCAG 2.0 AA website requirement applies to an organization if it is either a designated public-sector organization of any size, or a private-sector or nonprofit organization with 50 or more employees in Ontario. Read that twice. A 12-person municipal office is a designated public-sector body, and its website duty applies regardless of headcount. A 12-person retailer is private-sector, and it doesn’t. Same employee count, completely different legal answer, because sector, not just size, decides it.

There’s one more wrinkle worth knowing if you’re inside government specifically. The Government of Ontario and the Legislative Assembly carry an extra duty most organizations don’t: their internal websites, intranets and extranets, also have to meet WCAG 2.0 AA, where everyone else’s internal-only tools sit outside the standard entirely.

Everything about counting employees, and exactly where the private-sector 20-and-50 lines fall, is covered in full in the employee-thresholds guide. That piece is the deep dive on headcount; this section is the sector layer sitting on top of it.

What are the Accessible Canada Act’s 2026 to 2028 deadlines, and could they apply to me?

If your organization is federally regulated, the ACA runs on its own separate clock, and 2026 is a real date on it too, just not the one Ontario businesses are watching.

Federally regulated organizations that already published an accessibility plan owe their next annual progress report by June 1, 2026, per Deque’s tracking of ACA compliance deadlines. Plans and progress reports repeat on a roughly three-year renewal cycle, with annual updates filed in between. That’s a governance deadline, plans, consultation with people with disabilities, a public feedback process, not yet a technical website standard.

The technical standard arrives on its own separate timeline, under the ACA’s Digital Technologies Accessibility Regulations. December 5, 2027 is when federal government websites must fully conform to CAN/ASC-EN 301 549, and when mandatory accessibility training kicks in for staff working on digital technologies across all obligated entities. December 5, 2028 is when large (500+ employee) and medium (100–499 employee) federally regulated private organizations must bring their own public-facing websites, mobile apps, and digital documents into conformance, per Deque’s breakdown of the phased rollout. Federally regulated organizations under 100 employees currently sit outside that 2028 website requirement.

None of this replaces your AODA obligations if you’re also operating in Ontario. The two laws stack, they don’t substitute for each other.

Do different sectors face different accessibility rules within Ontario itself?

Yes, and the biggest split isn’t between industries, it’s between public and private/nonprofit. Designated public-sector organizations, municipalities, school boards, colleges and universities, hospitals, carry obligations the rest of the province doesn’t.

Two concrete differences. First, the one covered above: their website WCAG duty applies at any size, where a private business needs 50 or more employees to trigger the identical requirement. Second, their compliance-report cycle runs every two years instead of three. Their last filing was December 31, 2025, and their next lands in 2027, a full year before most private and nonprofit organizations file again on December 31, 2026.

Nonprofits, meanwhile, get no special carve-out. A registered charity with 55 staff answers to AODA exactly the way a 55-person for-profit company does, same 50-employee website threshold, same December 31, 2026 report deadline, same penalties on paper. The only sector distinction that matters for a nonprofit is whether it happens to be a designated public-sector body, a public hospital foundation, for instance, might be, or a straightforward private nonprofit, which most are.

What doesn’t change, across every sector: WCAG 2.0 Level AA is the technical bar, not a sliding scale. A hospital’s site and a hardware store’s site are held to the identical standard once each owes the duty. Only who owes it, and how often they report, moves with sector.

What happens if you don’t comply, under AODA, and under the ACA?

Both laws bite, but they’re built differently, and knowing which one applies changes what “non-compliance” actually costs.

Under AODA (S.O. 2005, c. 11, s. 37), penalties run as a flat daily rate that compounds for as long as the violation continues: up to $100,000 per day for a corporation, up to $50,000 per day for an individual, and directors or officers can be held personally liable for up to $50,000 per day if they didn’t take reasonable care to prevent the offence.

The ACA works on a per-violation, tiered model instead. The Accessibility Commissioner, housed inside the Canadian Human Rights Commission, can levy administrative monetary penalties from $250 up to $250,000 per violation depending on severity, per accessibility.works’ breakdown of ACA enforcement. Minor violations, like a missing accessibility plan, sit at the low end; obstructing an investigation or filing false information sits at the top. A continued violation across multiple days can count as a separate violation each day, so it compounds too, just on a different structure than AODA’s flat daily rate.

In practice, both regulators have leaned on warnings and compliance orders before reaching for the maximum fines, but “they usually don’t go to the max” isn’t a plan. The path to either number runs the same way: ignore an order, or file something false, and the number stops being theoretical.

What should an Ontario business actually do this quarter?

If you’re reading this in Q3 or Q4 2026, the December 31 deadline isn’t abstract anymore, it’s this quarter or next. Here’s a realistic run at it, month by month, assuming you’re starting from close to zero.

September: figure out what you actually owe

Count your Ontario employees properly, full-time, part-time, seasonal, and contract staff paid in Ontario, using the rules in the employee-thresholds guide. Confirm whether you’re a designated public-sector body (any-size website duty) or private/nonprofit (50-employee threshold). If you’re federally regulated, note that separately, you’re on the ACA’s clock, not just AODA’s.

October: get the real audit, not the assumption

If a website duty applies to you, this is the month to actually test the site, automated scan plus a manual keyboard and screen-reader pass, rather than assume a theme or a plugin already covers it. What a real accessibility audit actually covers walks through the process. October gives you roughly two months of runway to fix what it finds before you’re filing under pressure.

November: fix the findings, document your policies

Work through the punch list the audit produced. If you’re a large organization, this is also the month to get your accessibility policies written down, posted publicly, and your multi-year plan drafted, not left as something you do informally.

December: file, and don’t wait for December 31 itself

File through the Accessibility Compliance Reporting Portal well before the deadline. Government portals have bad days, especially on the day everyone in the province is trying to use them at once. If your remediation isn’t fully finished by the deadline, an honest, in-progress answer on the report beats an optimistic one you can’t back up.

When should I bring in someone to handle this for me?

The moment the audit and fix list outgrow what your internal team can responsibly own, usually that’s the 50+ employee point where the website duty is legally binding, or any point where December 31 is close enough that a DIY cycle no longer fits your runway.

The work itself doesn’t change with the client’s size. On any serious build, accessibility gets tested and signed off before launch, full stop; that discipline travels the same way to a Kitchener retailer’s WordPress site as it does to a larger platform, only the scale of the review shrinks. That’s what jbe.works’ accessibility service does: a real audit, real code-level fixes, and a record you can actually stand behind when you file. Get in touch and I’ll tell you straight where your site stands.

Your next step

Boil it down to three questions. Which law actually governs you, AODA or the federal ACA, an industry test, not a location test. Which sector tier you’re in under AODA, a designated public-sector body owes the website duty at any size, a private or nonprofit organization only at 50 or more employees. And what’s actually due this quarter, because December 31, 2026 is close enough now that “later” isn’t a real plan.

For the full mechanics behind the private-sector side of AODA, thresholds, the deadline, WCAG itself, start with the complete AODA website accessibility guide. If you need to know exactly what a proper audit involves before you commission one, here’s what’s actually in one. And if the honest answer is that your site wouldn’t survive a real WCAG check, that’s a conversation worth having before a compliance report forces it. Reach out.

Frequently asked questions

Quick, direct answers to what Ontario business owners ask most about accessibility compliance.

Does AODA or the federal Accessible Canada Act apply to my Ontario business?

AODA applies unless your industry is federally regulated: banks, telecom and broadcast carriers, airlines, interprovincial transport, and the federal government. Most Ontario businesses, regardless of size, answer to AODA, not the ACA.

What’s the difference between AODA and the Accessible Canada Act?

AODA is Ontario provincial law naming WCAG 2.0 Level AA as its website standard, enforced by the province with daily fines. The ACA is federal law naming a stricter standard (CAN/ASC-EN 301 549, incorporating WCAG 2.1 AA), enforced by the Accessibility Commissioner with per-violation penalties.

Do public-sector organizations have different accessibility rules than private businesses in Ontario?

Yes. Designated public-sector organizations owe the website WCAG duty at any size and report every two years. Private and nonprofit organizations only owe the website duty at 50 or more employees and report every three years.

What are the Accessible Canada Act’s 2026-2028 deadlines?

June 1, 2026 for annual progress reports (organizations with an existing plan); December 5, 2027 for federal government website conformance and staff training; December 5, 2028 for 100+ employee federally regulated private organizations’ public-facing websites.

What happens if my business doesn’t comply with accessibility law in Ontario?

Under AODA, fines run up to $100,000 per day for a corporation and $50,000 per day for an individual or director. Federally regulated organizations under the ACA instead face per-violation penalties up to $250,000, depending on severity.

What should I do this quarter to prepare for the December 31, 2026 deadline?

Confirm your Ontario employee count and sector tier, get a real audit if a website duty applies to you, fix what it finds and document your policies, then file through the Accessibility Compliance Reporting Portal well before December 31.