WCAG 1.2.6 Sign Language: When Is It Required for Web Accessibility?

WCAG 1.2.6 Sign Language explains when sign-language interpretation is required for prerecorded video with audio. This article describes what the success criterion covers, when it applies, and practical steps to meet it for web content.

What WCAG 1.2.6 covers

WCAG 1.2.6 is a success criterion in WCAG 2.1 that addresses sign-language interpretation for prerecorded, synchronized media. Its aim is to make audio content accessible to people who rely on sign language. The requirement applies to prerecorded video where meaning depends on the audio track.

When sign language is required

Sign language is required under this criterion when three things are true:

• The media is prerecorded and synchronized video with audio.
• The audio conveys information essential to understanding the content.
• No effective alternative already meets the needs of sign-language users for that content.

Practical examples where sign language will usually be required include training videos, public service announcements, or recorded talks where spoken content carries meaning not present in the visuals.

Legal and policy triggers

Whether you must provide sign language can also depend on law, contract, or organisational policy. For example, public sector accessibility rules that require compliance with WCAG 2.1 level AA will make this criterion applicable where the content matches the points above. Always check the specific accessibility regulations that apply in your country or sector.

When captions or transcripts are enough

Captions and transcripts remain essential and usually required. For many users captions provide sufficient access. Sign language is specifically intended for users whose first or preferred language is a signed language, or who get better comprehension from sign than from text captions.

Use captions when:

• The audience reads the page language well.
• The audio is not culturally or linguistically nuanced in a way captions cannot convey.

Provide both captions and a transcript together with any sign-language version.

How to implement sign language for prerecorded media

Follow a clear, repeatable process. This reduces rework and keeps costs predictable.

1. Scope the content. Identify which videos contain audio that is essential. Prioritise emergency, legal, public-facing and high-traffic materials.
2. Choose the right sign language. Use the native signed language of your target audience. For UK audiences that may be British Sign Language. Confirm local preferences with Deaf organisations.
3. Hire a qualified interpreter. Use a professional interpreter or presenter fluent in the chosen sign language. Native fluency matters for clarity and cultural accuracy.
4. Decide presentation method. Common options are an inset interpreter window, a split-screen version, or a separate sign-language video served alongside the original. Allow users to switch between versions if possible.
5. Record with accessibility in mind. Ensure good lighting, a neutral background, and camera framing that keeps hands and facial expressions fully visible.
6. Deliver multiple tracks. Provide the sign-language version, captions, and a text transcript. Label each clearly in the player and in page metadata.
7. Make the player accessible. Ensure controls are keyboard operable and labelled for screen readers so users can toggle versions and tracks.

Technical tips

• Offer a player toggle to switch between original and sign-language tracks rather than forcing a new page load.
• Place an inset interpreter window so it does not hide critical visuals. Test at common screen sizes.
• Provide a separate sign-language file if your CMS or player cannot present two synchronized video tracks cleanly.
• Include descriptive metadata and clear labelling so assistive technology and content managers can find the sign-language version.

Testing and quality checks

Automated checks cannot verify sign-language quality. Test with native signers before publishing.

• Confirm timing and sync between interpreter delivery and the original audio.
• Ask native signers if regional signs, register, and tone are appropriate.
• Check visibility across devices and common screen sizes.
• Verify player controls are reachable by keyboard and described to screen readers.

Common mistakes to avoid

• Relying only on automated sign-language avatars. These are not acceptable substitutes for professional interpreters.
• Offering captions alone when the video targets sign-language-first users.
• Using tiny inset windows that hide hands or facial expressions.
• Failing to test with real users who are native signers.

Costs, prioritisation and practical trade-offs

Producing sign-language versions has a cost. You can reduce expense by prioritising essential content and reusing interpreted segments across multiple videos. For large catalogues, consider these approaches:

• Start with high-priority items such as public notices and training.
• Reuse interpreter footage for common introductions or standard disclaimers.
• Offer a clear schedule for rolling out sign-language versions so expectations are managed.

Quick WCAG 1.2.6 compliance checklist

• Have you identified prerecorded videos where audio is essential?
• Have you provided sign-language interpretation for those videos or a justified alternative?
• Do captions and transcripts accompany every version?
• Have native signers tested the delivered interpretation?
• Are player controls keyboard operable and screen reader labelled?

Where to get help

Work with local Deaf organisations and qualified sign-language interpreters. For technical clarification, consult the official WCAG documents and reach out to experienced accessibility consultants. User testing with native signers gives the best verdict on real accessibility.

If you want, I can help map which of your videos likely need sign language and produce a rollout plan with estimated time and cost.