AODA Website Compliance 2026: Deadlines & Penalties

Most Ontario businesses know they have privacy obligations. Far fewer realize they also have a legal duty to make their websites accessible — and that the next major reporting checkpoint is approaching at the end of 2026. The Accessibility for Ontarians with Disabilities Act (AODA) sets enforceable web accessibility standards, and the penalties for ignoring them are among the steepest of any provincial compliance regime in Canada.

This guide explains who must comply, what the technical standard actually requires, the deadlines that matter in 2026, and a practical path to getting compliant. It is written for owners, operations leads, and compliance officers — not lawyers — and it is general information, not legal advice.

Last updated: June 2026

What Is the AODA?

The AODA became law in 2005 with a stated goal of making Ontario accessible for people with disabilities. It works through enforceable standards under the Integrated Accessibility Standards Regulation (IASR), covering areas like customer service, employment, information and communications, transportation, and the design of public spaces.

The part that catches most businesses by surprise is the Information and Communications Standard, which includes web accessibility. If your organization meets the size threshold, your public website and web content must conform to a specific technical standard — and "we didn't know" is not a defence the regulator accepts.

Who Must Make Their Website Accessible?

This is where most third-party articles get it wrong, so it is worth being precise. Under the IASR, the web content accessibility requirement applies if you are either:

• A designated public sector organization, or
• A business or non-profit organization with 50 or more employees in Ontario.

The organization that controls the website — directly or through a contract with a web vendor — is the one on the hook. Using an outside agency does not transfer the legal obligation away from you.

The 50-employee line matters. Per the Government of Ontario's own guidance, the WCAG website obligation attaches to organizations with 50 or more employees. Smaller organizations (1 to 49 employees) are not required to bring their public websites into WCAG conformance under this specific standard, although they remain subject to other AODA standards (such as accessible customer service) and to the general expectation of accommodating people with disabilities.

You will see some vendor blogs claim that 1-to-49-employee businesses must meet "WCAG 2.0 Level A" for websites. Treat that with caution — it does not reflect the Ontario government's published position on the web content requirement. When in doubt, confirm against the official source rather than a vendor selling overlay widgets.

The Standard: WCAG 2.0 Level AA

For organizations that are covered, the requirement is conformance with the Web Content Accessibility Guidelines (WCAG) 2.0, Level AA. This applies to public websites and web content published or substantially refreshed after January 1, 2012.

There are two carve-outs written into the regulation:

• Success Criterion 1.2.4 — live captions for live audio content, and
• Success Criterion 1.2.5 — pre-recorded audio descriptions.

Everything else at Level A and Level AA is in scope. As the standard itself notes, you generally have to satisfy the Level A criteria before the Level AA criteria make sense — Level AA builds on Level A.

What WCAG 2.0 AA Actually Requires

WCAG is organized around four principles — content must be Perceivable, Operable, Understandable, and Robust (POUR). In plain terms, a conforming website typically needs to:

• Provide text alternatives for non-text content, so images, icons, and charts have meaningful alt text a screen reader can announce.
• Be fully keyboard operable, so every function works without a mouse, with a visible focus indicator and no keyboard traps.
• Allow text resizing up to 200% without loss of content or function.
• Meet color contrast minimums (generally 4.5:1 for normal text, 3:1 for large text).
• Provide captions and transcripts for multimedia (subject to the two exceptions above).
• Use clear, self-explanatory page titles, headings, and link text so the structure is navigable.
• Label form fields and surface errors in a way assistive technology can read.
• Be robust enough to work with current and future assistive technologies, which in practice means clean, valid, semantic HTML.

A useful mental model: if someone using only a keyboard and a screen reader can find, read, and complete every important task on your site, you are most of the way there.

The 2026 Deadline You Need to Know

Here is the second distinction that trips people up. There are really two separate obligations, with two different thresholds:

1. The website conformance obligation (WCAG 2.0 AA) — applies to organizations with 50+ employees, and the compliance date for public websites has already passed (January 1, 2021). If you are covered and not yet conformant, you are currently non-compliant, not "preparing."
2. The accessibility compliance report — a periodic filing that organizations with 20 or more employees must submit to the province. The next reporting deadline for private-sector and non-profit organizations is December 31, 2026.

So a business with, say, 30 employees has a filing obligation in 2026 even though it may sit below the 50-employee website-conformance line. A business with 80 employees has both: it must keep its website WCAG 2.0 AA conformant and file the report. Treating these as one thing is a common and costly mistake.

The regulation currently references WCAG 2.0, so conform to 2.0 AA today; designing new work with the newer WCAG 2.2 in mind is a sensible way to future-proof it.

Penalties for Non-Compliance

The AODA carries real teeth. On conviction for an offence, the Act provides for fines of up to $100,000 per day for a corporation and up to $50,000 per day for other persons, and a director or officer who fails in their duty can face fines of up to $50,000 per day (AODA, s. 37). Separately, the Act allows directors to issue compliance orders and administrative penalties (Part V).

Keep this in perspective: those figures are statutory maximums, not typical outcomes. Accessibility complaints and human-rights claims can also run in parallel with AODA enforcement.

Training Is Part of the Requirement

Web conformance is not the whole picture. Covered organizations must also train employees, volunteers, anyone who participates in developing the organization's policies, and anyone who provides goods, services or facilities on its behalf on the IASR and on the Ontario Human Rights Code as it relates to people with disabilities. Training must be appropriate to each person's duties and delivered as soon as practicable, and organizations with 50+ employees must document it — keep records of the dates training was provided and how many people received it (IASR, s. 7).

How AODA Fits With Your Other Canadian Obligations

AODA is an Ontario law. If you operate nationally, it sits alongside, not on top of, your privacy obligations. A typical Ontario SME is juggling:

• PIPEDA for the handling of personal information (see our PIPEDA compliance guide).
• CASL for commercial electronic messages.
• AODA for accessibility, if you meet the size thresholds.
• Quebec's Law 25, if you have customers or operations in Quebec.

If you want to see how Ontario's requirements line up against other provinces, our provincial privacy laws comparison and Ontario privacy compliance overview put the pieces side by side. Federally regulated organizations should also be aware of the separate Accessible Canada Act, which imposes its own accessibility planning and reporting duties distinct from the AODA.

A Practical AODA Website Compliance Checklist

You do not need to boil the ocean. Work through this sequence:

1. Confirm whether you are covered. Count your Ontario employees. At 50+, the website WCAG obligation applies. At 20+, the December 31, 2026 report applies regardless.
2. Run an accessibility audit. Combine automated scanning (which catches only some issues) with manual testing using a keyboard and a screen reader. Automated tools alone are not sufficient and overlay "accessibility widgets" do not, on their own, create legal conformance.
3. Fix in priority order. Start with blockers: keyboard operability, missing form labels, missing image alternatives, and color contrast failures. These affect the most users and are the most visible in an audit.
4. Address documents and media. PDFs, Word files, and videos posted to your site are "web content." Tag PDFs, add captions and transcripts, and remediate or replace inaccessible documents.
5. Bake accessibility into procurement. Require WCAG 2.0 AA conformance in contracts with web vendors and SaaS providers, and ask for a VPAT or accessibility conformance report before you buy.
6. Train your people and keep records. Deliver role-appropriate IASR and Human Rights Code training and log it.
7. File your accessibility compliance report before December 31, 2026 if you have 20+ employees.
8. Make it ongoing. Accessibility regresses every time you ship new content. Add an accessibility check to your publishing workflow and re-audit periodically.

Common Mistakes to Avoid

• Relying on an overlay widget. A one-line script that adds an accessibility toolbar does not remediate the underlying code and has been the subject of significant criticism and litigation. It is not a substitute for conformance.
• Auditing once and forgetting. A site that was conformant last year may not be today after a redesign or a few dozen new blog posts.
• Ignoring third-party components. Embedded booking widgets, chat tools, and PDFs are all in scope. Your conformance is only as strong as the least accessible thing on the page.
• Confusing the two thresholds. Remember: 50+ employees for the website standard, 20+ employees for the compliance report.

Frequently Asked Questions

Q: Does my small business website have to be AODA compliant? A: The WCAG 2.0 AA website conformance requirement under the IASR applies to organizations with 50 or more employees in Ontario (and to designated public sector organizations). If you have fewer than 50 employees, that specific website standard does not apply to you, though other AODA standards and general accessibility expectations still do — and if you have 20 or more employees, you still have a compliance report to file.

Q: What is the AODA deadline for 2026? A: December 31, 2026 is the next accessibility compliance report filing deadline for private-sector and non-profit organizations with 20 or more employees. The deadline to make public websites conform to WCAG 2.0 Level AA (for organizations with 50+ employees) was January 1, 2021 and is already in force.

Q: What WCAG version does the AODA require? A: WCAG 2.0 Level AA, with two exceptions — live captions (Success Criterion 1.2.4) and pre-recorded audio descriptions (Success Criterion 1.2.5).

Q: What are the penalties for AODA non-compliance? A: On conviction for an offence, the AODA allows fines of up to $100,000 per day for corporations and up to $50,000 per day for other persons, including directors or officers who fail in their duty (s. 37). These are statutory maximums. The Act also provides for compliance orders and administrative penalties.

Q: Will an accessibility overlay widget make my site AODA compliant? A: No. Overlay tools can supplement an accessible site but do not, by themselves, bring non-conformant code into WCAG conformance. Genuine compliance requires remediating the underlying website and content.

Q: Is AODA the same as the federal Accessible Canada Act? A: No. The AODA is an Ontario law. The Accessible Canada Act is a separate federal statute that applies to federally regulated organizations and carries its own accessibility planning and reporting obligations.

---

Stay Ahead of Your Ontario Obligations

Accessibility is one strand of a broader Canadian compliance picture that also includes PIPEDA, CASL, and Quebec's Law 25. To check whether your organization must file an AODA report this year, use the free AODA 2026 report checker. Canada Compliance AI helps Canadian SMEs work through CASL, PIPEDA and Quebec Law 25: a free two-minute compliance check, readiness scores, a prioritized task plan, a 24-month breach register and an exportable audit log. See what's live and what's planned.

Not sure where you stand? Take the free compliance assessment to see which obligations apply to your business, or reserve your founding-member access ahead of the full Q3 2026 launch.

Related reading: Ontario Privacy Compliance | Provincial Privacy Laws Comparison | PIPEDA Compliance Guide