Live Captions and WCAG 2.2: A Guide to Making Your Events Accessible and Compliant

You're hosting a major virtual event. Your keynote speaker is delivering a powerful message, the audience is engaged, and everything is running smoothly. But is it running smoothly for everyone? Globally, around 430 million people experience disabling hearing loss. Without real-time captions, a significant portion of your audience might be missing out entirely.

This isn't just about inclusivity; it's about legal and ethical responsibility. Digital accessibility lawsuits are on the rise, with over 5,114 cases filed in 2025 alone. And a staggering 94.8% of websites still have detectable accessibility failures. For event organizers, this means the stakes have never been higher. Understanding and implementing WCAG live captions compliance isn't just good practice—it's essential.

This guide will walk you through the specifics of the Web Content Accessibility Guidelines (WCAG) for live captions, explain what’s new in version 2.2, and give you practical steps to make your next event both accessible and compliant.

Understanding Success Criterion 1.2.4 (Captions - Live)

At the heart of live event accessibility is WCAG Success Criterion 1.2.4, which falls under the Level AA conformance level—the standard most laws and legal precedents point to. The intent is straightforward: provide synchronized text for live audio content so that people who are deaf or hard of hearing can access the information in real-time.

Think of it this way: captions provide a text equivalent of everything happening in the audio track. This includes:

• Spoken dialogue: Who is saying what.
• Speaker identification: Essential when a person isn't visible on screen.
• Non-speech sounds: Things like [laughter], [applause], or [music playing] that add crucial context.

This criterion applies to "synchronized media," meaning audio and video presented together, like a live-streamed webinar, a virtual conference, a corporate town hall, or a product launch. It's designed for broadcast-style events. It's important to note this isn't intended to cover two-way video calls between a few individuals; the responsibility lies with the host broadcasting the content.

To comply, you need a solution that can generate accurate, real-time captions as the event happens. This ensures that everyone in your audience has the opportunity to engage with your content equally.

What's New in WCAG 2.2 for Live Events?

WCAG 2.2 was officially released to build upon previous versions, and while it doesn't replace WCAG 2.1, it adds new criteria to address modern digital experiences. The updates primarily focus on improving usability for users with cognitive or learning disabilities, those with low vision, and people using mobile devices.

While Success Criterion 1.2.4 for live captions remains a core component from previous versions, WCAG 2.2 introduces nine new success criteria. These new rules address things like:

• Focus Not Obscured (AA): Ensuring that interactive elements, when focused, are not hidden by other content like sticky headers or pop-ups.
• Target Size (Minimum) (AA): Making sure that clickable targets are large enough to be easily activated by users with motor impairments or those on touchscreens.
• Consistent Help (A): Placing help options in the same relative spot across pages to make them easy to find.
• Accessible Authentication (AA): Banning the use of cognitive function tests (like memorizing a password or solving a puzzle) as the sole method for authentication.

So, while the core rule for live captions hasn't changed, the overall landscape for event platform accessibility has become more robust. Running a compliant event in 2026 and beyond means looking at the entire user journey—from how attendees log in to how they interact with your event player—through the lens of these updated guidelines.

Open vs. Closed Captions: Which Should You Use?

When implementing captions, you have two primary options: open captions and closed captions (CC). The choice has a direct impact on user experience and compliance.

Open Captions (OC) are "burned" directly into the video file. They are always visible and cannot be turned off by the viewer.

• Pros: They guarantee that captions are always displayed, regardless of the platform or the viewer's settings. This can be useful for social media clips where videos auto-play on mute.
• Cons: The user has no control. They can't be turned off, which may be distracting for some viewers. They also can't be resized or restyled, which can cause readability issues on different screen sizes. For multilingual events, you would need to produce a separate video file for each language.

Closed Captions (CC) are delivered as a separate text file that plays in sync with the video. Viewers can toggle them on or off using the media player's controls.

• Pros: This is the preferred method for accessibility because it gives users control over their experience. Platforms can allow users to customize the appearance (font, size, color) for better readability. It's also much easier to offer captions in multiple languages, as the user can simply select their preferred track.
• Cons: They rely on the video player to support them and on the user to know how to enable them.

For WCAG compliance, closed captions are generally the better and more flexible choice. They provide the necessary accessibility for those who need it while giving control to those who don't. Both open and closed captions can meet WCAG standards if they are accurate and synchronized, but the user control offered by closed captions makes them the industry-standard best practice.

The Difference Between Captions and Subtitles for Compliance

The terms "captions" and "subtitles" are often used interchangeably, but they serve different purposes, and the distinction is critical for accessibility.

Subtitles are created for viewers who can hear the audio but do not understand the language being spoken. Their primary function is translation. They assume the viewer can hear sound effects, music, and other non-speech audio cues, so they only include the spoken dialogue.

Captions, on the other hand, are designed for viewers who cannot hear the audio. They aim to provide a full auditory experience through text. This means they include not only the dialogue but also important non-speech information like:

• [applause]
• [upbeat music]
• [door slams]
• Speaker identification (e.g., "SPEAKER 2:")

For WCAG live captions compliance, you must use captions (or "subtitles for the deaf and hard-of-hearing," often abbreviated as SDH). Subtitles alone are not sufficient because they leave out the contextual audio information that is essential for a person who is deaf or hard of hearing to fully understand the content.

How to Implement Compliant Live Captions on Your Event Platform

Making your live events accessible doesn't have to be a technical nightmare. With the right approach and tools, you can ensure WCAG compliance and deliver a truly inclusive experience.

First, your streaming platform must support the integration of a live captioning solution. Many modern platforms like Zoom, Teams, Google Meet, and YouTube Live have built-in functionalities or allow for third-party integrations.

The next step is to choose how the captions will be generated.

1. Automated Speech Recognition (ASR): AI-powered engines can transcribe spoken words into text in real-time. While ASR technology has improved dramatically, it may not be accurate enough on its own to meet WCAG standards, especially with complex terminology, multiple speakers, or background noise. Some state-of-the-art ASR systems can reach 90% accuracy, but only under ideal audio conditions.
2. Human Captioning (CART): Communication Access Realtime Translation (CART) involves a professional human stenographer who transcribes the event live. This method provides the highest level of accuracy because a human can understand context, accents, and nuanced audio cues that an AI might miss.
3. AI + Human Hybrid Model: The most robust approach combines the speed of AI with the accuracy of human oversight. An AI provides the initial real-time transcription, and human linguists or captioners review and correct it.

At InterpretWise, we champion a flexible hybrid model. Our browser-based platform allows you to choose between AI-powered captions for speed and scalability or professional human captioners for maximum accuracy, all within the same interface. Setup takes just minutes, and attendees can access live captions and multilingual audio simply by scanning a QR code—no app download required.

Ready to see how easy it is to make your next event compliant and accessible? Book a demo to explore our live captioning and interpretation solutions.

FAQs: WCAG Compliance for Live Video

PAA: Does WCAG require captions for live video?

Yes. WCAG Success Criterion 1.2.4 requires captions for all live audio in synchronized media (video with audio) to achieve Level AA conformance. This applies to live-streamed events like webinars, conferences, and news broadcasts. The goal is to make content accessible to people who are deaf or hard of hearing in real-time.

PAA: What is the difference between open and closed captions for accessibility?

Open captions are permanently embedded into the video and cannot be turned off, while closed captions are a separate track that viewers can enable or disable. Closed captions are generally preferred for accessibility because they give the user control over their viewing experience and often allow for customization of font size and color.

PAA: Are subtitles the same as captions for accessibility?

No, they are not the same. Subtitles translate spoken dialogue for viewers who don't understand the language, assuming they can hear other sounds. Captions are for viewers who cannot hear the audio and include both dialogue and important non-speech sounds (like [applause] or speaker IDs) to provide full context. For WCAG compliance, captions are required.

PAA: How accurate do live captions need to be for WCAG compliance?

WCAG does not specify an exact percentage for accuracy, but the captions must be sufficient to be understandable and convey the same meaning as the audio content. While automated captions have improved, human captioners (CART) or a hybrid AI-human approach are often recommended for live events to ensure the highest accuracy, especially with technical jargon, multiple speakers, or poor audio quality.