Accessibility should be planned into a holographic or spatial event from the first production meeting, not added after the show is built. This checklist helps creators and event teams track device access, captions, audio description, alternative 2D delivery, venue sightlines, motion, flashing content, and audience support so more viewers can participate in a way that works for them.
Overview
A live holographic event may involve several audience experiences at once: a projected image in a venue, a web player on a laptop, a mobile AR view, a headset-based spatial scene, or a conventional video stream. Each format creates different access requirements. A viewer may have an older phone, limited bandwidth, low vision, hearing loss, motion sensitivity, or no suitable headset at all.
The practical goal is not to make every format identical. It is to provide a dependable way to understand and enjoy the important parts of the program without requiring one specific device, sensory ability, or physical position. Treat the 3D experience as one layer of the event, then build equivalent routes through the content.
Use this checklist during creative development, technical rehearsals, venue planning, and post-event review. For a broader distribution plan, see the Spatial Streaming Delivery Guide. Accessibility decisions should also be coordinated with the venue, platform, captioning team, performers, and anyone responsible for audience support.
What to track
Accessibility requirements matrix
Record each requirement, the person responsible, the delivery format, and the point at which it will be tested. A simple matrix prevents accessibility work from becoming an assumption shared by nobody.
| Audience need | Production response | Where to verify |
|---|---|---|
| Hearing access | Live captions, translated captions when planned, readable text styling, and a transcript or replay captions where practical | Broadcast feed, web player, venue screens, and rehearsal recording |
| Low vision or blindness | Audio description for important visual action, clear spoken scene changes, and an audio-only or descriptive route where feasible | Program script, audio mix, stream player, and venue listening system |
| Limited device access | Responsive 2D video or web viewing that does not require a headset, AR-capable phone, or special display | Supported browsers, phones, tablets, laptops, and low-bandwidth test conditions |
| Mobility access | Step-free routes, suitable seating, accessible controls, and staff support without requiring a viewer to change locations | Venue walk-through, seating map, entry route, and evacuation plan |
| Motion or sensory sensitivity | Reduced-motion option, warnings for intense effects, controlled transitions, and a quieter viewing route when available | Full program review, effects cue sheet, headset mode, and venue environment |
| Communication access | Plain-language instructions, visible help information, and a clear way to request assistance before and during the event | Registration page, confirmation email, venue signage, and support desk |
Captions and audio description workflow
Captions should be treated as part of the live production pipeline rather than a separate post-production asset. Identify every spoken element, including presenters, performers, remote guests, recorded clips, and important audience announcements. Decide whether captions will be generated, typed, or supplied from a prepared script, then assign a person to monitor accuracy and timing during the show.
Review caption placement against the visual composition. A caption box that covers a performer, key graphic, or spatial object may technically exist but still reduce access to the content. Test text size, contrast, line length, speaker identification, and legibility from the intended seating areas and common viewing devices.
Audio description should explain visual information that is necessary to follow the event: entrances, gestures, changes in the holographic scene, physical demonstrations, on-screen text, and meaningful lighting or projection changes. Write descriptions into the running order, leave suitable pauses when possible, and check that the narration does not obscure dialogue or essential sound cues.
Alternative 2D viewing plan
Do not describe a 2D stream as merely a backup. It can be the best route for viewers whose devices cannot display spatial content or who prefer a conventional interface. Define what the 2D audience will see: a wide camera, a close-up feed, a picture-in-picture layout, or a director-selected edit. Include captions, audio description, chat or question access, and the same key announcements available to the venue audience.
Test the 2D route independently. A spatial feed may be impressive in a headset but confusing when flattened into a single frame. Check framing, occlusion, camera cuts, readable graphics, latency, audio synchronization, and whether a viewer can tell where attention should go.
Device and onboarding checklist
- Publish supported device and browser information in plain language.
- Explain whether viewers need an app, account, camera permission, headset, headphones, or a high-speed connection.
- Provide a non-spatial route before ticket purchase or registration, not only on the day of the event.
- Offer a short test page or preview so viewers can confirm that video, audio, captions, and controls work.
- Design instructions for keyboard, touch, and controller use where those inputs are supported.
- Provide contact details for technical and access support, including the hours when help is available.
Venue, seating, and sightlines
For an in-person live hologram event, accessibility includes more than a ramp or reserved seat. Check whether the spatial display is visible from wheelchair positions, companion seats, standing areas, and different rows. Avoid placing accessible seating where equipment, railings, camera operators, or other audience members block the main visual field. Confirm that captions or auxiliary displays can be seen without forcing viewers to turn away from the performance.
Inspect sound coverage, lighting contrast, aisle clearance, and the route to restrooms and quiet areas. If the show uses headsets, controllers, or wearable devices, plan for alternative controls, cleaning procedures, assistance with fitting, and a way to participate without sharing equipment.
Motion and flashing-content review
Review the complete show for rapid camera movement, depth changes, simulated falling, intense parallax, strobing, abrupt brightness shifts, and repeated visual patterns. The same effect may feel manageable on a large venue display and uncomfortable in a headset or mobile AR view. Mark each risk in the cue sheet and decide whether to remove it, soften it, add a warning, or provide a reduced-motion version.
Warnings should be specific and early enough for viewers to make a choice. A general notice that the event contains visual effects is less useful than identifying the relevant segment and explaining how to switch to an alternative view.
Cadence and checkpoints
Accessibility changes as the show changes. Use the following checkpoints rather than waiting for a final compliance review:
- Concept stage: list audience formats, access goals, alternative delivery routes, and budget or staffing implications.
- Content lock: identify dialogue, visual-only information, effects, music cues, on-screen text, and moments requiring description or warnings.
- Technical integration: test captions, audio description, player controls, device support, and the 2D route with the actual production stack.
- Venue rehearsal: walk accessible routes, inspect sightlines, measure caption visibility, test sound coverage, and rehearse audience assistance.
- Live event: monitor caption accuracy, stream failures, support requests, and any change to the running order.
- Post-event review: record what worked, which devices failed, where viewers needed help, and which assets should be improved for replay.
Review platform accessibility features, browser and headset capabilities, captioning workflows, venue guidance, and applicable requirements at least annually and whenever a major platform, device, distribution method, venue, or standard changes. For recurring shows, a quarterly review is a practical minimum; review sooner if the audience profile, format, or production technology changes.
How to interpret changes
Not every accessibility issue is a technology problem. Separate failures into four categories: content, such as missing descriptions; delivery, such as captions not appearing in the web player; environment, such as a blocked sightline; and support, such as unclear instructions or no trained contact person. This classification makes the fix easier to assign.
Prioritize issues that prevent a viewer from entering, understanding, or safely leaving the event. A broken alternative stream, absent captions, inaccessible seating route, or unannounced intense effect should be addressed before lower-impact cosmetic adjustments. Compare feedback by format rather than averaging it across the whole audience: a venue display, headset experience, and 2D stream may have different failure patterns.
Track both completion and usability. “Captions were enabled” does not show whether they were readable, synchronized, or visible against the scene. “A 2D stream existed” does not show whether it carried the same essential information. Ask testers to complete realistic tasks, such as joining the event, changing caption settings, finding help, following a scene change, and leaving the experience safely.
When to revisit
Reopen this checklist before every new venue, audience segment, show format, and distribution channel. Revisit it after changes to the cast, script, spatial scene, projection system, headset build, streaming platform, caption provider, or player interface. A new digital performer or mixed reality workflow may introduce different visual and audio requirements; the Digital Avatar Live Performance Workflow and Mixed Reality Live Production Workflow can help map those production changes.
Before publishing the next event, assign owners for captions, audio description, device support, venue access, audience communication, and incident response. Run one full rehearsal through the primary spatial experience and one through the alternative 2D route. Keep a dated record of platform capabilities, tested devices, known limitations, and fixes. That record turns accessibility from a one-time promise into a repeatable part of live holographic event production.
Audience-support briefing template: Tell staff who can request assistance, where the accessible entrance and seating are located, how to provide or adjust captions and audio description, what the alternative viewing route is, how to respond if a viewer feels unwell or overwhelmed, and who owns technical escalation. Staff should offer help without assuming what a person needs, explain options clearly, and protect the viewer’s privacy.
For related planning, use the Live Hologram Event Safety and Venue Requirements Checklist and the Low-Latency Spatial Streaming Checklist. Update this accessibility review on a regular cadence, then verify it again whenever the show or its delivery environment changes.