How accessible is your website?Start free check

Deafness: How Deaf People Use the Web

Also called: Deaf people, Hearing loss, Hard of hearing

Definition

Deafness is a substantial, uncorrectable hearing loss in both ears. Deaf people use websites without relying on sound, so speech and other audio must also be available as text – captions, transcripts – and, for some users, in sign language.

Deafness rarely stops anyone from reading a web page – but it shuts people out of everything a page only says out loud. A product video without captions, a podcast without a transcript, a support line that only takes phone calls or a voice assistant without a text option: for a deaf visitor, that content simply does not exist.

What it means

W3C's page on auditory disabilities describes a range: from mild or moderate hearing loss in one or both ears – often called "hard of hearing" – to deafness, a substantial, uncorrectable hearing loss in both ears. Some people hear sounds but not clearly enough to follow speech, especially with background noise, including many who wear hearing aids. People who are deafblind have both hearing and vision loss and often read the web on a braille display.

Two points are easy to miss. For some deaf people a sign language is their first language, and written text is a second language they may read less fluently. And not every deaf person knows sign language – and there is no single sign language, but many across countries and regions.

W3C lists the typical barriers. These are the WCAG criteria behind them:

Barrier WCAG criterion Level
Videos with speech but no captions 1.2.2 Captions (Prerecorded) A
Audio-only content (podcasts, recordings) without a transcript 1.2.1 Audio-only and Video-only A
Live streams and webinars without live captions 1.2.4 Captions (Live) AA
Sound that plays automatically and can't be stopped – see audio control 1.4.2 Audio Control A
Important videos without sign language interpretation 1.2.6 Sign Language (Prerecorded) AAA

On top of that, W3C names media players that don't show captions or don't let users change caption size and color, and services that work only by voice.

Examples

Example
<!-- Inaccessible: video with speech, no captions, autoplay with sound -->
<video src="product-tour.mp4" autoplay></video>

<!-- Accessible: controls, captions track, transcript link, no autoplay -->
<video controls>
  <source src="product-tour.mp4" type="video/mp4">
  <track kind="captions" src="product-tour.en.vtt" srclang="en" label="English" default>
</video>
<p><a href="/product-tour-transcript">Read the transcript of the product tour</a></p>

The track element with kind="captions" adds captions the visitor can switch on in the player – see MDN on the track element. The transcript is useful for deafblind users, who read it on a braille display.

Do

Caption every video with speech, including who speaks and important sounds like "[alarm beeps]". Offer transcripts for podcasts, let people contact you by email, chat or form, and show alerts as text as well as sound.

Don't

Rely on auto-generated captions without checking them, autoplay videos with sound, put key instructions only in a voice-over, or make a phone number the only way to reach support or verify an account.

How to check your site for deaf visitors

    Questions

    What do deaf people need on a website?

    Captions for videos with speech, transcripts for audio, text alternatives for sound alerts and a way to get in touch without a phone call. For some deaf users, sign language for key content helps most.

    What is the difference between deafness and being hard of hearing?

    Hard of hearing usually means mild to moderate hearing loss; many people use hearing aids and can still follow some speech. Deafness means a substantial hearing loss in both ears, so sound can't be relied on at all.

    Are automatic captions enough for deaf viewers?

    Not on their own. Auto-generated captions often get names, technical terms and punctuation wrong. They are a good starting point, but someone should review and correct them before publishing.

    Does WCAG require sign language videos?

    Only at Level AAA, criterion 1.2.6. Most laws, such as the European Accessibility Act, build on Level AA, which requires captions for prerecorded and live video, but not sign language.

    • Captions: Accessible Video for Deaf Viewers

      Captions are synchronized text versions of a video's audio: the dialogue, who is speaking and the non-speech sounds needed to follow it. WCAG 1.2.2 requires them at Level A for all prerecorded audio in synchronized media.

      Read definition: Captions: Accessible Video for Deaf Viewers
    • Transcript: Text Alternative for Audio and Video

      A transcript is a text version of time-based media: the spoken words, who says them, important sounds and, for video, what happens on screen, in the right order. WCAG 1.2.1 requires such an alternative at Level A for prerecorded audio-only and video-only content.

      Read definition: Transcript: Text Alternative for Audio and Video
    • Audio Control: Stop Autoplay Sound

      Audio control is WCAG success criterion 1.4.2. If audio on a web page plays automatically for more than 3 seconds, there must be a way to pause or stop it, or to control its volume independently of the system volume.

      Read definition: Audio Control: Stop Autoplay Sound
    • Blindness: How Blind People Use the Web

      Blindness is a substantial, uncorrectable loss of vision in both eyes. Blind people use websites without seeing them, through a screen reader that reads content aloud or shows it on a refreshable braille display, and they navigate with the keyboard or touch gestures.

      Read definition: Blindness: How Blind People Use the Web

    Let AI Handle Website Accessibility

    Built in Europe. Set up in 2 minutes, no developer needed. Put website accessibility on autopilot with AI-powered fixes and automated monitoring.

    1. 1Choose your plan
    2. 2Install in 2 min
    3. 3AI fixes your website
    4. Done