An AI chatbot, an AI-drafted web page, or an AI-generated video doesn't arrive with an accessibility exemption attached. Two Canadian regimes — one federal, one provincial — already decide whether that content has to be accessible, and neither one cares whether a person or a model produced it.
Key takeaways
The Accessible Canada Act sets an ambitious national goal — its purpose section states the Act exists to benefit all persons, especially persons with disabilities, through “the identification and removal of barriers, and the prevention of new barriers,” working toward “a Canada without barriers, on or before January 1, 2040” (Accessible Canada Act, s.5). Barriers in “information and communication technologies” are named as one of seven areas the Act targets directly — squarely covering AI-driven interfaces, chatbots and digital content.
The scope trap is in section 7. The Act applies to specific “regulated entities”: the federal government, Crown corporations, the Canadian Forces, and “any person, partnership or unincorporated organization that operates a work or carries on an undertaking or business that is within the legislative authority of Parliament” (Accessible Canada Act, s.7(1)) — in practice, banks, telecommunications carriers, broadcasters, airlines and interprovincial transport, alongside the federal public service itself. It does not apply to an ordinary provincially incorporated business just because that business uses AI. A retailer, a law firm or a marketing agency is not a federally regulated entity merely by virtue of running a chatbot.
For most Canadian businesses, the accessibility rule that matters in practice is provincial, and Ontario's is the most detailed and the most concretely sourced. Ontario's own guidance states the threshold precisely: “As of January 1, 2021, the AODA requires you to make all public websites accessible if you are either: a designated public sector organization or a business or non-profit organization with 50 or more employees” (ontario.ca, How to make websites accessible). The obligation attaches to whoever controls the website — directly or through a contractual relationship over its appearance, functionality or content — and applies to content published after January 1, 2012.
The technical standard is specific rather than vague: covered organizations must meet “WCAG 2.0 Level AA success criteria, except for: 1.2.4 (live captions) 1.2.5 (pre-recorded audio descriptions)” — two success criteria listed as exceptions, not one combined requirement — (ontario.ca, How to make websites accessible). WCAG 2.0 — the Web Content Accessibility Guidelines — is an internationally developed standard covering things like text alternatives for non-text content, sufficient colour contrast, and full keyboard operability. None of those requirements reference how the content was produced. A page a generative AI tool assembled is still required to meet the same success criteria as a page a person built by hand.
A designated Ontario non-profit with 60 employees adds an AI-powered virtual assistant to its public-facing website to answer common questions. Because the organization is covered by the AODA at its current size, the assistant's interface — not just the surrounding page — has to meet WCAG 2.0 Level AA: it needs to be operable without a mouse, its responses need to be exposed to assistive technology as they appear rather than rendered as an inaccessible visual-only widget, and any video or audio content it surfaces needs the same captioning that any other video on the site would need. None of that changes because a model is generating the responses in real time rather than a person having pre-written them. Getting this right up front is the same category of problem as catching an AI failure mode before launch rather than after — a compliance gap discovered post-launch is more expensive to fix than one designed around from the start.
Ontario businesses working through the AODA's website rules in general — not specific to AI — can start from a fuller walk-through of who is covered and what the standard requires (treadstonelaw.ca, AODA website accessibility rules for Ontario businesses).
Scope
Scope, stated plainly. This page covers the federal Accessible Canada Act and Ontario's AODA. Other provinces run their own accessibility regimes, with different scope, thresholds and standards. A business operating outside Ontario, or outside federally regulated sectors, needs to confirm the rule in its own province rather than assume either regime above applies.
Accessibility sits alongside privacy and security as one of the places an AI deployment's real risk surface differs from the demo — the mechanism is explored more broadly in how to tell if an AI output is trustworthy.
No. Neither the federal Accessible Canada Act nor Ontario's AODA references how content was produced. If an organization is otherwise covered — by sector under the federal Act, or by size under the AODA — its AI-produced content is covered the same way its hand-built content would be.
Usually not directly. It binds federally regulated entities — banks, telecommunications carriers, broadcasters, interprovincial transport, the federal government — not ordinary provincially regulated businesses. Most businesses using AI should look to their own province's accessibility law instead.
For the specific public-website requirement, yes — the threshold is 50 or more employees for a business or non-profit (designated public-sector organizations are covered regardless of size). A business just under that threshold should still confirm which other AODA standards may apply to it, since the website rule is only one part of the Act.
Accessibility is one of several compliance questions that come up the moment AI-drafted content reaches an actual public audience rather than an internal draft.
