Begin the sound review by turning the sound off. If the visitor can no longer understand the task, receive a result, or tell whether an action worked, audio is carrying information the interface has not provided another way. A busy venue adds another reason to run that test, but hearing access matters even in a quiet room.
The Smithsonian's inclusive digital interactives guide recommends pairing audio feedback with visual feedback and captioning video. It describes museum examples with headphones and notes that companions may still follow captions without putting on a headset. Those are design observations from exhibition practice, not proof that a particular event audio setup will work in its venue.
Separate three kinds of sound
An event interactive may contain atmosphere, instructions, and confirmation. Treat them differently. Music may create mood without changing the task. Spoken instructions may be the only explanation of what to do. A success tone may confirm that a button worked, yet provide no equivalent visual signal. In the build brief, identify each sound that carries necessary information and its visual or text counterpart.
For a browser-based video, the W3C media-planning guide explains when captions, transcripts, and audio description are relevant. Captions convey speech and meaningful non-speech sound; a transcript can also support people who cannot use synchronized media. WCAG requirements depend on the media type and whether it is prerecorded or live. This web guidance is a useful interface specification, not a certificate for the installed speaker system or venue.
Do not substitute ordinary dialogue subtitles for complete captions when sound effects identify an event, a speaker, or an outcome. A caption must remain visible long enough to read at the actual screen size, without covering the control the visitor needs next. For a sound-only success cue, an on-screen state such as “Result saved” is more direct than captioning a beep. These are design decisions to test with the intended audience.
Decide how people will listen
A loudspeaker lets bystanders hear the experience but competes with announcements, other installations, and nearby conversation. Headphones can make the spoken track more private; they introduce a physical handoff, cleaning, reach, and group-listening question. A visitor's own phone can deliver personal audio, but it also creates a scan and connection step. None of these choices solves every venue. The phone-or-shared-kiosk decision guide addresses that separate form-factor decision.
Write the audio route into the interaction: where does a visitor set volume, pause or replay a line, turn captions on, or choose a silent path? If audio starts automatically on a web page for more than three seconds, WCAG's audio-control criterion calls for a way to pause or stop it, or control its volume separately from overall system volume. A venue operator may also need a master limit; that is a deployment rule, not a visitor control.
Test the event, not just the edit suite
Run a full task at the installed station in three conditions: sound off, expected event noise, and the loudest planned music or announcement period. Ask a first-time tester to begin, make a choice, interpret the result, and recover from one mistake. Watch for missed feedback, captions hidden by glare or people, and a voice track that becomes hard to follow while the tester reads. Record the particular failure and revise that screen or sound, rather than simply raising the volume.
The accessible touchscreen brief covers the broader physical and digital requirements. This audio test supplies a narrower acceptance question: can someone complete the same essential task without hearing a word, while those who use audio can control and understand it?