WCAG 2.2 Demo SuiteSign Language (Prerecorded)
Sign language interpretation is provided for all prerecorded audio in synchronised media.
Who this affects
Deaf users whose first language is a sign language. For many, a signed language is native and the written language of the page is a second language read at reduced fluency — captions alone are not equivalent.
The failure and the fix
Each example below is a self-contained page, loaded in a frame so its markup cannot affect this page. Open either one on its own to test it with a keyboard or screen reader.
Fails 1.2.6
Open the failing example in a new tab
fail.html — the problem
<h1>How to reserve a book</h1>
<!-- FAILURE: the video is captioned, so it passes 1.2.2 at Level A. There is
no sign language interpretation, so it fails 1.2.6 at AAA.
Why captions are not always enough: for many Deaf people a signed language
is their FIRST language, and the written language of the page is a second
language, often read at reduced fluency. Someone whose first language is
British Sign Language is reading English captions the way a hearing person
might read a second language they learned at school - possible, slower,
and lossy. BSL, ASL and Auslan are distinct languages with their own
grammar; they are not signed English. -->
<video controls width="640">
<source src="../../assets/media/shop-tour.mp4" type="video/mp4">
<track kind="captions" src="../../assets/media/shop-tour-captions.vtt"
srclang="en" label="English" default>
</video>Meets 1.2.6
Open the passing example in a new tab
pass.html — the fix
<h1>How to reserve a book</h1>
<!-- FIX: a sign language interpretation is provided alongside the video.
Two common patterns:
a) picture-in-picture, with the interpreter inset over the video
b) a separate signed version the user selects
Requirements that are easy to get wrong:
- the interpreter must be large enough to read. Facial expression and
mouth pattern are grammar in signed languages, not decoration, so a
tiny corner inset is useless.
- the interpreter must not be croppable or coverable by player controls
- it must be the RIGHT signed language for your audience -->
<p>
<button type="button" class="button button--secondary" id="sign-toggle" aria-pressed="false">
Show British Sign Language interpretation</button>
</p>
<div class="with-signer">
<video controls width="640">
<source src="../../assets/media/shop-tour.mp4" type="video/mp4">
<track kind="captions" src="../../assets/media/shop-tour-captions.vtt"
srclang="en" label="English" default>
</video>
<div class="signer" id="signer" hidden>BSL interpreter</div>
</div>
<div class="note">
<p><strong>A note on this demo.</strong> The panel above is a placeholder, not a
real interpreter. Producing genuine signed video requires a qualified Deaf or
hearing interpreter and cannot be synthesised, so this suite marks the position
and size an interpreter must occupy rather than faking the content.</p>
<p>For real projects: commission a qualified interpreter, film them against a
plain contrasting background, and give the viewer a control to show, hide and
enlarge the panel.</p>
</div>How to test it
Confirm a sign language track or picture-in-picture interpreter is available, in the correct sign language for the audience (BSL, ASL and others are distinct languages).
-
Automated
Requires a fluent human reviewer.
No axe rule maps to this criterion. It has to be checked by a person.
-
Keyboard
Unplug the mouse. Move through the page with Tab, Shift+Tab, Enter, Space and the arrow keys. See the keyboard testing script.
-
Screen reader
Listen to both examples with NVDA, JAWS, VoiceOver or TalkBack and compare what is announced. See the screen reader cheat sheets.
-
Visual
Zoom to 200% and 400%, narrow the viewport to 320 px, and apply the text-spacing overrides. See the visual testing procedures.
Related criteria
In the specification
- Understanding 1.2.6 Sign Language (Prerecorded) — the W3C explanation, intent and exceptions
- 1.2.6 in the WCAG 2.2 Recommendation — the normative wording