Design for Deaf People: Why "Zero Volume" Is a Design Challenge (and Not Just a Button).

When we think of a deaf user, we often picture an older person with a hearing aid.

Wrong. Deafness is a vast spectrum ranging from mild hearing loss to profound deafness, and it can affect anyone because of illness, accidents, or simply prolonged exposure to loud noise.

Designing for people who cannot hear is not just a "moral duty" or a matter of accessibility laws: it is a User Experience choice that improves the product for everyone. Think about how often you watch social media videos without sound on a train or at the office. At that moment, you too are "situationally deaf."

Deafness is a spectrum (and the numbers matter)

Hearing is measured in decibels (dB). Most of us fall within the "normal" range (up to 15 dB of hearing loss). But it takes very little to change the rules of the game:

• Mild hearing loss (16–25 dB):

  You miss up to 10% of speech if the person speaking is more than a meter away.

• Moderate hearing loss (41–55 dB):

  You can hear almost nothing of a conversation at normal volume.

• Profound deafness (91+ dB):

  You perceive only very strong vibrations, such as a car horn or music played at full volume.

Three myths to bust (Spoiler: sign language isn't universal)

Many of the design decisions we make today are based on mistaken assumptions:

1. Is sign language universal? No.

   There are about 300 different sign languages. A deaf British user often won't understand a deaf American user.

2. Can everyone read lips? No.

   You can decipher only 30% of words by watching the movement of the mouth. The rest comes from intuition and context.

3. Is written text enough? Not always.

   For someone born deaf, sign language is their native language (4D, made up of space, time, and facial expressions), while written Italian is often their "second language." Filling a page with complicated text can be a barrier.

4 Golden Rules for Inclusive UX

If you're designing software or a website, here's how you can make a difference:

1. Stop requiring a phone call:

   Never make a phone number the only way to get in touch. Offer chat, email, or messaging systems.

2. Haptic and visual feedback:

   If an app needs to send an alert, use vibration (haptic feedback) or visual cues (flashes or pop-ups). Don't rely only on the "ding."

3. "Speaking" subtitles:

   In videos, don't just write down what people say. Include descriptions of ambient sounds (e.g. [heavy rain], [group laughter]).

4. Identify who's speaking:

   In subtitles and transcripts, always specify the name of the person speaking, especially if they're off-screen.

Graffico's Take 🔴

Why is this topic essential for a technology partner?

Because accessibility doesn't happen by accident: it's a deliberate decision.

Companies often see accessibility as an "extra cost" or a burden to tack on at the last minute like a crutch. At Graffico, we believe that designing with deaf people (and not just "for" them) leads to better products for everyone:

• Less friction:

  A visually clear interface helps a distracted user just as much as it helps a deaf user.

• More value:

  Making content (such as podcasts or company videos) accessible through accurate transcripts also improves search engine indexing.

• Reliability:

  A system that doesn't require users to use their hearing is a more robust system in any environment (noisy offices, public transport, enforced silence).

Accessibility isn't a favor we do for a minority; it's the guarantee that our software works for everyone, everywhere.