EventRecast
Start free
Guide

WCAG 2.2 event accessibility, in practice

WCAG 2.2 is the working baseline for accessibility on most public-facing events. This guide explains the success criteria that apply to live and recorded event content, what counts as compliant, and where teams typically fall short.

Start free trial
Published

WCAG 2.2 — Web Content Accessibility Guidelines, version 2.2 — is the standard most accessibility programs reference when evaluating digital content. It's the basis for ADA Title III enforcement guidance in the US, EN 301 549 in the EU, and most institutional accessibility policies. For event teams, the guidelines that matter cluster around captioning, audio descriptions, and accessible viewer interfaces.

This guide is for accessibility coordinators and event teams who want to know what 'WCAG 2.2 AA captioned media' actually means in practice — and how to operate at that bar without making it a heroic effort per event.

What this guide covers

Captioned media success criteria

The two captioning criteria (1.2.2 for prerecorded, 1.2.4 for live) and what compliance looks like for each.

Audio descriptions

When 1.2.3 / 1.2.5 / 1.2.7 apply to event content, and what counts as a sufficient audio description.

Caption display requirements

The display-side criteria — text size, contrast, time-based media controls — that affect captioning UX.

Multilingual considerations

How translated captions interact with WCAG criteria and where the standard is silent.

Documentation expectations

What auditors and procurement teams expect to see as evidence of WCAG 2.2 compliance.

The captioning success criteria step by step

  1. Identify whether the content is live or prerecorded

    WCAG splits captioning into two criteria. 1.2.2 (Captions, Prerecorded) is Level A and applies to recordings, archived events, and on-demand video. 1.2.4 (Captions, Live) is Level AA and applies to real-time streamed events.

  2. Provide synchronized captions for live events (1.2.4)

    Captions must be synchronous with the spoken audio and must include any audio information necessary for understanding. The standard doesn't specify a numeric latency or accuracy threshold but requires captions be 'understandable.' Real-time captioning platforms typically achieve 1.5-3 second latency and 90%+ accuracy on clean audio.

  3. Provide captions for prerecorded content (1.2.2)

    Once the event is recorded and made available on-demand, the recording must have captions. These can be the live captions (cleaned up if accuracy was marginal) or post-production captions. They must be synchronized with the audio track.

  4. Document the captioning workflow

    Procurement reviews and auditor evaluations expect documentation: which platform produced the captions, what the latency and accuracy targets are, how transcripts are retained. A captioning platform that exposes this in its admin console reduces the documentation effort to near zero.

Audio descriptions: when they apply to events

WCAG 2.2 has three audio-description-related criteria: 1.2.3 (Audio Description or Media Alternative, Prerecorded — Level A), 1.2.5 (Audio Description, Prerecorded — Level AA), and 1.2.7 (Extended Audio Description, Prerecorded — Level AAA). For event content, the practical question is whether visual information is essential to understanding (charts, slides, on-stage demos) and not conveyed in the spoken audio.

If a speaker presents data slides while saying 'as you can see, conversions doubled in Q3' — the data point is in the audio. No audio description needed. If a speaker walks through a complex visualization without narrating what's on screen, audio description is needed for blind and low-vision attendees.

Live events are not covered by these audio description criteria (the criteria apply to prerecorded content). For live events, the practical mitigation is speaker training: present visuals out loud, describe images and charts, verbally walk through demos. Captioning then carries that description into the captioned record.

Caption display: 1.4.x criteria that affect UX

The 1.4.x family of criteria addresses how content is displayed, including captions. 1.4.3 (Contrast Minimum, AA) requires sufficient contrast between caption text and its background. 1.4.4 (Resize Text, AA) requires that captions can be resized up to 200% without loss of content or function. 1.4.10 (Reflow, AA) requires that the content reflow at narrow viewport widths.

Most modern captioning platforms handle these natively — captions are HTML text in the viewer page, attendees can adjust font size and contrast, and the page is responsive. The thing to verify when evaluating a platform is that the viewer's caption display itself meets these criteria, not just the marketing site.

What auditors and procurement actually look for

Accessibility audits and procurement reviews tend to ask the same questions: (1) Are live captions provided? On what platform? With what accuracy target? (2) Are recordings captioned? (3) How long are transcripts retained, and are they accessible to attendees who request them? (4) Are captions available on mobile? (5) What's the documented escalation path when captioning fails during an event?

Having short, written answers to each of these — with the captioning platform named, contract documentation linked, and an example transcript shown — is usually the difference between an audit that takes a half-day and one that takes a week. Accessibility coordinators who have fought this battle once tend to template the responses.

Frequently asked questions

Try EventRecast on a real event

Free trial. No credit card to start.

Start free trial

Related

ADA compliance for virtual events

How WCAG 2.2 maps to ADA Title III requirements for virtual and hybrid events.

EventRecast for accessibility coordinators

How accessibility programs use captioning as the operational layer that makes WCAG compliance scalable.

Searchable transcripts

The post-event transcript that satisfies WCAG 2.2 1.2.2 (Captions, Prerecorded).