If your Ontario website hosts video — a product demo, a testimonial, an embedded webinar recording — pre-recorded captions are not optional under Ontario's web accessibility rules. They are a Level A requirement, the most fundamental tier of WCAG (Web Content Accessibility Guidelines), below even the Level AA that Ontario law names as its floor. But the same regulation that mandates pre-recorded captions explicitly exempts two other video-related criteria — and most Ontario businesses know neither fact.
Key facts
- WCAG Success Criterion 1.2.2 Captions (Pre-recorded) is Level A — the most basic WCAG tier — and is required for large organizations (50+ employees) under Ontario's IASR (Integrated Accessibility Standards Regulation, O. Reg. 191/11) s.14 (ontario.ca, O. Reg. 191/11).
- Ontario IASR s.14 mandates WCAG 2.0 Level AA but explicitly exempts two criteria: 1.2.4 Captions (Live) and 1.2.5 Audio Descriptions (Pre-recorded) — these two are carved out of the legal obligation by name in the regulation (ontario.ca, O. Reg. 191/11).
- WCAG 1.2.3 Audio Description or Media Alternative (Pre-recorded) is Level A and is not exempt — so pre-recorded video must include either an audio description track or a full text alternative describing the visual content (W3C, WCAG 2.0).
- Auto-generated captions from YouTube, Vimeo, or any platform do not satisfy WCAG 1.2.2 — the criterion requires accurate, synchronized captions; machine-generated approximations with errors in names, numbers, or technical terms fall short (W3C, WCAG 2.0 Understanding Documents).
- 5,114 ADA (Americans with Disabilities Act) digital accessibility lawsuits were filed in 2025 across federal and state courts; plaintiffs with hearing or auditory disabilities are the second-largest claimant group, frequently targeting missing or inaccurate video captions (UsableNet, 2025 Year-End Accessibility Lawsuit Report).
- The next ACR (Accessibility Compliance Report) deadline for private-sector and non-profit organizations with 20 or more employees in Ontario is December 31, 2026 (ontario.ca).
What does Ontario's AODA actually require for video on websites?
Ontario's AODA (Accessibility for Ontarians with Disabilities Act) sets the policy; the IASR (O. Reg. 191/11) sets the technical rules. Section 14 of the IASR requires large organizations — those with 50 or more employees — to make public websites and web content conform to WCAG 2.0 Level AA, with two specific exemptions named in the text.
Three WCAG 1.2 "time-based media" criteria apply without exemption:
1.2.1 Audio-only and Video-only (Pre-recorded) — Level A. Content that is audio-only or video-only, with no synchronized counterpart, requires a text alternative. A podcast excerpt embedded on your site needs a transcript. A silent product video (no audio) needs a text description or audio narration of the visual content.
1.2.2 Captions (Pre-recorded) — Level A. Any pre-recorded video that contains spoken audio must include accurate, synchronized captions. This covers product demonstrations, explainer videos, recorded webinars, testimonials, and promotional content — anything with a person speaking or a voiceover. No exceptions apply to this criterion under the IASR.
1.2.3 Audio Description or Media Alternative (Pre-recorded) — Level A. Pre-recorded synchronized media (video with an audio track) must include either an audio description track or a full text alternative that conveys the same information as the video. This criterion is not exempt. Critically, 1.2.3 gives the option of providing a detailed descriptive transcript in lieu of a spoken audio description track — making it more achievable for most organizations than the Level AA version.
What are the two IASR exemptions — and what do they mean in practice?
The IASR s.14 is precise: the WCAG 2.0 Level AA obligation applies to Ontario websites "other than success criteria 1.2.4 Captions (Live) and success criteria 1.2.5 Audio Descriptions (Pre-recorded)" (ontario.ca, O. Reg. 191/11).
1.2.4 Captions (Live) — explicitly exempt. Live video streams, online events, and webinars are not required to provide real-time captions under the IASR. If your organization hosts a live product launch, a live Q&A, or a live training session streamed on your website, you do not face an IASR obligation for simultaneous captioning. Providing live captions is good practice and meaningfully extends access, but it is not compelled by the regulation as it stands.
1.2.5 Audio Description (Pre-recorded) — explicitly exempt. Audio description is a supplementary audio track that narrates what is happening visually in a video — on-screen text, actions, speaker changes — for users who cannot see the screen. Producing a separate audio description track is technically demanding. The IASR does not require it. You still must satisfy 1.2.3, but 1.2.3 accepts a detailed descriptive transcript instead of an audio description track, which is far less costly to produce.
Understanding both sides of this matters. Knowing you are not required to provide live captions prevents unnecessary spend on equipment or services for every online event. Not knowing you are required to caption your pre-recorded product videos is a gap that a human rights complaint or an ADA lawsuit can surface.
Do YouTube's automatic captions count as WCAG compliance?
No — and this is among the most widespread misconceptions in web accessibility.
YouTube and Vimeo generate automatic captions via speech-recognition software. These are a convenience feature, not an accessibility deliverable. Under favorable conditions — clear speech, standard accents, quiet backgrounds — accuracy can reach 80–90%, but it drops substantially for technical vocabulary, product names, proper nouns, numbers, and speakers with accents or speech differences. Errors cluster exactly where business content is most specific.
WCAG 1.2.2 requires captions that are accurate, synchronized, and complete. The W3C's Understanding Documents for WCAG 2.0 specify that captions must capture all spoken dialogue, speaker identification where relevant, and important non-speech audio. An auto-generated caption file that mishears a product name, omits a sentence, or attributes dialogue to the wrong speaker does not meet the standard.
The practical correction is not to discard the auto-generated file but to edit it. Export the .vtt or .srt from YouTube or Vimeo, review it against the audio, correct errors using a caption editor, and re-upload the corrected file. The machine draft saves time; it cannot replace the accuracy review.
This same gap applies to accessibility overlays that advertise caption functionality — a script bolted onto the page cannot reach inside a video file and add accurate captions that were never there. The FTC's $1,000,000 order against an overlay vendor in April 2025 targeted unsupported coverage claims of exactly this kind.
What about video with no spoken words — background music or a silent product loop?
WCAG 1.2.1 handles these cases:
- Video-only (no audio track): A silent product-showcase video or an animation needs a text alternative or an audio description that conveys the same information visually presented.
- Audio-only (no video track): An audio testimonial or podcast clip embedded on a page needs a text transcript.
- Background music only: A video with no dialogue and only ambient or promotional music does not trigger 1.2.2's captioning obligation. The criterion targets spoken audio. If the only audio is non-speech background sound, captions are not required under 1.2.2 — though a brief textual note describing the music ("background: upbeat instrumental") can be good practice for users with hearing disabilities.
- Video that is itself a media alternative: If a video exists only as an alternative to text content that is already on the page, and is clearly labelled as such, 1.2.1 does not apply to it. This exception is narrow and not a general escape.
How does AODA's legal floor compare to WCAG 2.2 best practice for video?
The IASR legal floor is WCAG 2.0 Level AA with the two named exemptions. The current best practice for new work is WCAG 2.2 Level AA, which covers the same 1.2 criteria without those carve-outs — meaning that at WCAG 2.2 AA, live captions (1.2.4) and pre-recorded audio descriptions (1.2.5) are expected even though Ontario law does not currently require them.
If you sell to US customers, the gap between the IASR floor and the effective standard widens. The DOJ's 2024 final rule for ADA Title II entities adopts WCAG 2.1 Level AA, and federal ADA case law consistently references WCAG 2.1 AA as the private-sector benchmark. Neither 1.2.4 nor 1.2.5 carries an equivalent exemption under that framework. An Ontario e-commerce business selling to US customers faces a higher practical standard for video than the IASR alone requires — making live captions and audio description tracks strategically sensible investments even if Ontario law doesn't compel them yet.
What happens if a person with a disability cannot access your video content in Ontario?
In Ontario, the AODA has no private right of action — individuals cannot sue under it. The enforcement path is the HRTO (Human Rights Tribunal of Ontario), which hears complaints of discrimination under the Ontario Human Rights Code. A person with hearing loss who cannot follow your product demo or your recorded webinar because captions are missing or inaccurate has a plausible complaint about unequal access to your goods and services.
The practical defense is the same as for other accessibility failures: documented remediation. A video content inventory, edited caption files with revision dates, and a re-upload record in your audit log show that you identified the gap and corrected it. That documented record — not a footer statement, not an overlay, not auto-captions left uncorrected — is what holds up if a complaint is tested.
The ACR (Accessibility Compliance Report) deadline for organizations with 20 or more employees is December 31, 2026 (ontario.ca). An honest ACR includes a realistic account of what your video content currently does and does not provide — and your remediation timeline for the gaps.
See whether your site's video content flags any caption or accessibility issues — free Vayle Report, about 30 seconds: vayle.art. It detects overlays, surfaces real WCAG failures, and tells you exactly what legally applies to your organization in Ontario. No obligation.
Vayle is a remote-first accessibility-engineering studio serving Ontario. General information, not legal advice.