An accessibility playbook for event organizers

Accessibility on events tends to be either heroic (every event a per-session scramble) or absent (an aspirational statement on the program page that doesn't match what attendees experience). Neither is sustainable. The teams that consistently run accessible events have moved the work from per-event heroics to operational defaults — accessibility happens because the system makes it happen, not because someone fought for it this Tuesday.

This playbook is what those teams have in common. It's organized by event lifecycle: before, during, after. It covers the captioning baseline (which is what most accessibility programs anchor around) plus the surrounding decisions — registration, room setup, speaker prep, post-event archive — that make the captioning actually land.

Before the event

Default to captioned. Make captions a checkbox in your event-creation flow, not a per-event budget conversation. The marginal cost of captioning a session approaches zero with modern platforms — once you've removed the cost barrier, the social barrier (defaulting to caption everything) is the only one left, and it's the easiest to remove.

Publish a clear accessibility statement. One paragraph on the registration page describing what's available — captions, ASL on request, accessible registration form, dietary accommodations, mobility access. This both informs attendees and creates a public record of your program's commitments. Templates are easier to maintain than per-event statements.

Build accessibility into the registration form. Test for keyboard navigation, screen-reader compatibility, sufficient contrast. Add an optional accommodations field so attendees who need ASL, mobility access, or other support can request it without contacting the organizer separately. Most accessibility incidents start at the registration page, not the event itself.

Brief speakers. A 30-minute speaker briefing covers most of the operational impact: describe slides verbally, avoid 'as you can see here,' pace yourself for caption rendering, repeat audience questions before answering. Speakers who get this briefing produce dramatically more accessible sessions; speakers who don't, don't.

During the event

Distribute the caption viewer link in three places. Printed QR codes on room signage, embedded link in the conference app's session detail page, in-meeting chat for fully-virtual sessions. The redundancy matters because every attendee finds links differently.

Confirm captions are running before the speaker starts. Have an AV operator open the viewer URL on a phone and watch captions appear during the room test. This catches setup mistakes before they become attendee-visible failures.

Keep an escalation path. If captioning fails mid-session, what do you do? Have a written answer: typically a backup recording with post-event captioning, or a live captioner on standby for high-stakes events. Documented escalation paths matter more in audits than perfect uptime.

Run ASL alongside captions for high-stakes sessions. Captions and ASL serve overlapping but different audiences. Major public sessions (keynotes, town halls, government-mandated events) typically warrant both.

After the event

Caption the recording. WCAG 2.2 1.2.2 requires captions on prerecorded media. Most modern captioning platforms produce a transcript that drops directly into recordings as a caption file (SRT or VTT). The marginal cost is zero; the compliance value is significant.

Publish the transcript at a stable URL. Attendees who missed the live event, attendees who want to revisit specific moments, and search engines all benefit from a persistent, searchable transcript. For public events, the transcript also becomes an SEO asset that keeps producing visibility months after the live audience has moved on.

Document accessibility outcomes. What was captioned? What languages? What accommodations were provided? Build the record as you go so audit responses don't become a per-audit reconstruction project.

Solicit attendee feedback specifically about accessibility. A question like 'Were captions available and useful to you?' on the post-event survey produces actionable data and signals to attendees that accessibility is a tracked metric, not a one-off effort.

What to skip (or de-prioritize)

Don't put captions on the main room display. Per-device captioning is dramatically better in almost every dimension. The exception is small rooms with explicit accessibility framing.

Don't try to manually edit transcripts to perfection before publishing. A 5-minute pass to fix proper nouns and remove obvious filler is sufficient. Spending two hours per session is a waste.

Don't promise ASL on every session. It's expensive and isn't required by WCAG or ADA at every level. Offer it on request for major sessions and accommodate when requested for smaller ones; treating it as a default for every breakout is unsustainable and not what most accessibility programs prioritize.

The compounding effect

Accessibility done well compounds. Each event makes the next one easier — the speaker briefings get refined, the registration form templates get reused, the captioning playbook gets faster, the transcript archive grows, the audit documentation accumulates.

After two or three event cycles, an accessibility program that started as 'we should probably do this' becomes operational infrastructure: it just works, every time, without anyone having to fight for it. That's the asymptote teams should aim for — not 'we did our best for this event' but 'accessibility is how every event runs by default.'