Any alert carried only in sound risks disappearing entirely for someone with hearing loss
Aliases: sensory substitution · multimodal redundancy · accessible notification
What it is
Any critical information carried only through sound — notifications, incoming calls, alarms, spoken responses — risks failing completely for a user with hearing loss, no matter how carefully the sound itself is designed. The only reliable answer is to give every piece of auditory information an equivalent visual or tactile channel: not "a little supplementary hint tacked on," but a second channel that can, by itself, fully convey what the sound was meant to convey, so the user never needs to hear the sound first to understand what happened.
Why it happens
An auditory channel can't serve as the sole carrier of information because it rests on assumptions about the user's hearing, the device being worn, and the surrounding context — and if any one of those assumptions fails, the information the sound carried is lost entirely, in an all-or-nothing way: the user either received the full meaning of the cue or received nothing, with no partial fallback in between. Visual and tactile channels can serve as true equivalents because they run on entirely separate sensory pathways; a failure in one doesn't propagate to the other. As long as the design lets the non-auditory channel carry the complete information on its own — rather than acting as a decorative animation merely synchronized with the sound — the user has a stable path to the information that doesn't depend on their hearing status. This is also why the bar for "equivalent" is high: flashing the screen to signal "something happened" and showing text or an icon that states exactly what happened and what to do are not the same thing — only the latter genuinely achieves channel parity, while the former still locks the actual content inside the sound.
Where it stops holding
This principle applies to any case where critical information is placed only in sound. If a piece of information already appears visually as well (a notification banner that includes text, for instance), an added audio version is a nice-to-have rather than a requirement, and falls outside this principle. Conversely, pure background music or ambient sound effects that carry no specific information don't need a visual equivalent either, since they have no "content" to make equivalent in the first place.
Applying it
- Audit every notification in the product that relies on sound alone: incoming calls and messages need a corresponding visual banner or icon state, alarms need screen flashing or a high-contrast cue, and spoken announcements need synchronized text.
- For situations that need immediate awareness but where the user may not be looking at the screen (a device in a pocket or out of view), use tactile vibration as the equivalent channel, and vary its rhythm or intensity pattern to distinguish notification types rather than using one identical vibration for everything.
- How to verify it: mute the device and walk through the entire critical flow relying only on visual and tactile cues — check whether the task can be completed and every system response understood without sound. If any single step requires hearing the sound to know what happened, the equivalent channel isn't complete yet.