Deaf/Hard of Hearing Design

Providing captions, transcripts, and visual alternatives for audio-based content.

stellae.design

Accessibility

Design for deaf and hard of hearing users ensures that all audio and auditory information has equivalent visual alternatives. Approximately 466 million people worldwide have disabling hearing loss (WHO). WCAG 2.1 SC 1.2.1 (Audio-only and Video-only, Level A) requires alternatives, SC 1.2.2 (Captions, Level A) requires synchronized captions for prerecorded video, SC 1.2.4 (Captions Live, Level AA) covers live captions, and SC 1.2.5 (Audio Description, Level AA) addresses visual information in video. Beyond media, this includes providing visual alerts instead of audio-only notifications, ensuring phone/voice-based services have text alternatives, and considering sign language for key content.

Why It Matters

Over 430 million people worldwide have disabling hearing loss, making audio-dependent interfaces a significant barrier to access. Products that rely solely on sound for alerts, instructions, or content exclude a substantial user population and often violate accessibility regulations like WCAG and ADA. Designing for deaf and hard of hearing users strengthens the experience for everyone — think noisy environments, muted devices, or users who simply prefer reading over listening.

Real-World Examples

YouTube Auto-Generated Captions with Manual Editing

YouTube provides auto-generated captions as a baseline and allows creators to upload corrected transcripts. This layered approach ensures some caption coverage exists immediately while enabling high-quality corrections. The result is a scalable captioning system that serves hundreds of millions of videos across languages.

Slack Visual and Haptic Notification System

Slack pairs audio notifications with visual badges, dock bounces, and mobile haptic feedback for every message and mention. Users can configure notification preferences to rely entirely on non-auditory channels without missing any information. This multi-channel approach ensures deaf and hard of hearing users have full access to real-time communication.

Counter-example

Emergency Alert System Using Only Sirens

Some campus or building emergency systems broadcast critical safety alerts exclusively through loudspeaker sirens with no accompanying visual displays, text messages, or flashing lights. Deaf and hard of hearing individuals receive no warning during emergencies, creating a life-safety risk. This single-channel approach fails the most fundamental requirement of accessible alert design.

Role-Specific Guidance

Common Mistakes

• The most frequent error is treating captions as an afterthought — auto-generating them without review leads to inaccurate transcripts that confuse rather than inform. Teams also commonly forget non-video audio such as notification sounds, error beeps, and background music that convey meaning without any visual equivalent. Another pitfall is assuming that providing captions alone is sufficient while ignoring sign language interpretation for complex or nuanced live content.