Filing the report and having a compliant website are not the same project — here’s the realistic version of what gets an Ontario business from “we should probably look into this” to actually done.
- “AODA website compliance” is three separate deliverables stacked on top of each other, not one checkbox: a filed report (20+ employees), documented policies and a multi-year plan (50+), and a website that actually conforms to WCAG 2.0 AA (50+).
- The compliance report is a self-attestation — nobody from the province tests your site before you’re allowed to submit it.
- Ontario’s own last published compliance and enforcement data shows the gap that creates: 94% of organizations that filed a report in 2017 said they were fully compliant, but when large businesses and non-profits were actually audited, only 63% had proof of completed training and 67% had a real multi-year accessibility plan on file.
- Real compliance leaves a paper trail — audit notes, a fix log, posted policies — not just a submitted form.
- It isn’t a one-time project. The multi-year accessibility plan has to be reviewed at least once every five years, and every redesign or new page is a fresh chance to break WCAG conformance you already paid to fix.
What does AODA website compliance actually mean?
It means three things, and most business owners only ever hear about the first one. File an accessibility compliance report if you employ 20 or more people in Ontario. Publish documented accessibility policies and a multi-year accessibility plan if you’re at 50 or more. And, at that same 50-employee tier, make your public website genuinely conform to WCAG 2.0 Level AA — tested against the standard, not assumed to meet it because the site looks fine.
Those three pieces don’t arrive together, and treating them as one task is exactly how a business ends up filing a clean-looking report on top of a website nobody’s actually checked. The full legal breakdown of who owes what lives in the complete AODA website accessibility guide — this piece assumes you’ve read that or don’t need it re-explained, and instead walks through what getting to “actually compliant” looks like as a project, plus the part almost nobody talks about: how thin the word “compliant” can be on a form nobody checks before you submit it.
Who actually has to do this?
Your obligation scales in two steps, at 20 employees and at 50, and mixing up which step you’re on is the most common mistake I see Ontario owners make.
| Ontario employees | File the report? | Website must hit WCAG 2.0 AA? |
|---|---|---|
| Under 20 | No | No |
| 20–49 | Yes, by Dec 31, 2026 | No |
| 50+ | Yes, by Dec 31, 2026 | Yes, plus posted policies and a multi-year plan |
If you need the worked examples — a 35-person firm versus a 120-person distributor, exactly how to count seasonal and contract staff — that’s covered in full in the employee threshold breakdown. This article picks up from whichever row you land on.
Is filing the report the same thing as being compliant?
No, and this is the split that trips up more businesses than anything else in the law. The report is a filing obligation at 20+ employees; an actually conformant website is a separate, harder obligation that only attaches at 50+. You can file a completely honest, fully compliant report at 35 employees and never have touched your website’s code, because the law simply doesn’t ask you to at that size.
Where it gets risky is at 50+, where the report itself asks you to confirm the website duty is met — and that’s precisely the question worth slowing down on before you click submit. The filing mechanics, the portal, and the exact December 31, 2026 date are covered step by step in the 2026 deadline explainer. What that piece doesn’t get into is what happens between “I filed the report” and “my site is genuinely accessible” — which is the whole rest of this one.
Why does “compliant on paper” so often mean something different in practice?
Because the compliance report is a promise, not a receipt. You log into the portal, answer a set of questions about what your organization has done, and submit. Nobody from the province visits your office or scans your site first. The report only becomes evidence of anything if what’s behind it is actually true.
Ontario’s own numbers make the gap concrete. The province’s last published accessibility compliance and enforcement report — covering the 2017 filing cycle, published March 2018 — found that 94% of organizations that submitted a report that year said they were in full compliance. But when the government actually audited large businesses and non-profits behind those self-reports, only 63% had proof of completed accessibility training, and only 67% had a genuine multi-year accessibility plan on file. That’s not a scandal, and it’s not organizations lying outright — it’s what self-attestation naturally produces when a box gets checked before the paperwork behind it fully exists.
The enforcement side of that same report is worth sitting with too: of 1,746 compliance activities across Ontario that year, only 16 were serious enough to be closed by an inspector, and of those, 6 resulted in a Director’s Order, with 3 carrying an actual monetary penalty. Enforcement is real but it’s slow and selective — which means the gap between what a business attests to and what’s actually true on its website can sit unnoticed for a long time before anyone checks. That’s not a reason to skip the work. It’s a reason not to let a filed report be the thing that convinces you the work is done.
If you want a genuine self-check before you attest to anything, Ontario publishes its own Accessibility Standards Checklist — a downloadable worksheet covering the full IASR: customer service, training, information and communications, and employment. It’s a solid first pass for the policy side of AODA. It is not a WCAG audit, and it won’t tell you whether your website’s contrast, keyboard navigation, or form labels actually pass. For that you need the kind of checklist covered in the AODA audit checklist — a separate, technical pass this general worksheet was never built to do.
What does an actually compliant website look like, concretely?
It looks like a paper trail you’d be comfortable showing to a director, not just a form you’d be comfortable submitting. Five things, specifically.
- Audit evidence. A record of what was tested, when, and how — automated scanning plus a genuine manual pass, not a scanner badge screenshotted once and filed away.
- Fixed code, not a bolted-on script. Contrast, alt text, keyboard behaviour, and form labels corrected in the actual markup and CSS. An overlay widget doesn’t produce this evidence, because it never touches the underlying code in the first place — the full reasoning on why is in the overlay compliance breakdown.
- Documented, posted policies (50+ employees) — written down, publicly available, not just practiced informally by whoever happens to be running the front desk that week.
- A real multi-year accessibility plan (50+ employees) that names what’s been done and what’s still open, reviewed at least once every five years per ontario.ca’s rules for businesses and non-profits.
- A retest. Fixes verified after they ship, not assumed to have worked because the developer said so.
Put those five together and you have something worth attesting to. Skip straight to the report without them and you’re filing the same kind of self-report the 2017 data shows so often didn’t hold up under a closer look.
What’s a realistic timeline to get compliant before December 31, 2026?
Work backward from the deadline, and there’s enough runway left from today to do this properly — but only if you start now instead of in the spring.
| Phase | What happens |
|---|---|
| Scope and audit | Confirm your employee tier, then run a real WCAG audit — automated scan plus manual keyboard and screen reader testing across a representative sample of your site. |
| Fix in code | Remediate what the audit found, in the actual templates and components, ranked by real user impact rather than by how many issues a scanner flagged. |
| Document (50+ employees) | Write and post accessibility policies, and put together a multi-year accessibility plan that names what’s done and what’s still open. |
| Retest | Verify the fixes actually hold — a second keyboard and screen reader pass, not just a rerun of the automated scanner. |
| File | Submit through the Accessibility Compliance Reporting Portal well ahead of December 31, 2026 — a submission that stalls with no runway left is its own kind of problem. |
Compress that into a scramble in November 2026 and something gets skipped — usually the retest, which is exactly the step that catches a fix that looked right in code review but didn’t actually work with a real screen reader.
Should you DIY your AODA compliance, or hire someone?
DIY works fine for the report itself if whoever fills it out is honest and organized. DIY gets a lot shakier for the website portion once you’re actually at 50+ employees, because WCAG remediation is development work — writing real alt text, restructuring headings, fixing keyboard traps in a slider — not a form field.
A 20–49 employee business with a simple brochure site can often run a self-check with Ontario’s own checklist tool, plus a basic keyboard-and-contrast pass, and file honestly. A 50+ employee organization, an e-commerce site, or anything built on a heavy page builder is a different calculation — that’s exactly the territory where a plugin can’t reach the underlying markup, covered in the AODA-on-WordPress guide if that’s your stack.
Real remediation is a one-time project cost rather than a recurring subscription, and it typically runs from a few days to a few weeks depending on the size of the site and what the audit turns up — the same math that makes an ongoing overlay subscription a worse deal than it looks. If you’d rather hand this to someone who does WCAG remediation for Ontario businesses, that’s what jbe.works Accessibility is for, and a free scan will tell you honestly where your site currently stands before you commit to anything.
How do you stay compliant after you file?
You don’t get to file once and walk away — AODA website compliance is a standing state, not a one-time event, and two things routinely undo it quietly.
The first is time. If you’re a large organization, the multi-year accessibility plan has to be reviewed at least once every five years, and treating that review as a real check-in rather than a rubber stamp is how you catch drift before a complaint does. The second is your own website team. Every new page, every redesigned template, every plugin update is a fresh chance to reintroduce a contrast failure or an unlabeled form field into code that used to pass. Folding an accessibility check into your normal publishing and QA process, rather than treating it as a once-every-three-years fire drill before the report is due, is the difference between staying compliant and re-discovering the same gaps next cycle.
If a redesign or a platform move is already on your roadmap, that’s the cheapest point to lock this in for good — fold the accessibility work into the same project instead of paying for it as a second, separate expense later.
Where should you actually start?
Confirm your tier first — the 20 vs. 50 threshold breakdown settles that in a few minutes. Then get a real audit against WCAG 2.0 AA rather than assuming your site passes; the AODA audit checklist walks through exactly what to test and how. If the acronyms themselves are still tangled, the a11y, WCAG, and AODA explainer sorts out which one’s the law and which one’s the daily practice.
And if you’d rather not run that audit yourself, or you already know your site wouldn’t survive one, jbe.works Accessibility does this work at the code level, not with a widget — reach out and I’ll tell you straight where you stand.
Frequently asked questions
Quick answers to what Ontario business owners ask most about getting to AODA website compliance.
Need the site to pass WCAG 2.0 AA before the December 31, 2026 AODA deadline?
Audit, remediation and the compliance report, handled end to end for Ontario businesses.
AODA & WCAG Accessibility Compliance →Is your site costing you customers?
Enter your website and get a free 60-second performance, SEO & accessibility report.
~60 seconds · No login