AccessiTech LLC

WCAG Guideline 1.2.6: Sign Language (Prerecorded) Explained

Estimated read time: 8–10 minutes

Guideline 1: Perceivable

The first principle of WCAG, Perceivable, ensures that information and user interface components must be presented to users in ways they can perceive. This means content can’t be invisible to all of a user’s senses—whether they are seeing, hearing, or feeling the content through assistive technology.

Guideline 1.2: Time-based Media

Guideline 1.2 focuses on making time-based media—like audio and video—accessible to everyone. This includes providing alternatives such as transcripts, captions, and audio descriptions so users with different abilities can access the content.

What Is Guideline 1.2.6 Sign Language (Prerecorded)?

"Sign language interpretation is provided for all prerecorded audio content in synchronized media."

Guideline 1.2.6 is a Level AAA requirement in the Web Content Accessibility Guidelines (WCAG) .

  • All prerecorded video content with audio should have a sign language interpretation track or overlay.
  • Sign language interpretation makes content accessible to users who are deaf and use sign language as their primary means of communication.
  • This is especially important for educational, governmental, and public service content.

This ensures that users who rely on sign language can fully understand your video content.

Who This Helps

Remember: This guideline specifically serves the culturally Deaf community (capital D) — people for whom sign language is their primary language, not a secondary accommodation.

  • Deaf individuals whose first language is a sign language (ASL, BSL, Auslan, etc.) and who may have limited English or text literacy
  • Native signers who think, communicate, and process information visually through sign language
  • People who identify as culturally Deaf and are part of the vibrant Deaf community and culture

This guideline does NOT replace captions (WCAG 1.2.2 ) for deaf/hard-of-hearing users who prefer written text. Both sign language and captions may be needed to serve all users.

Why Does It Matter?

Remember: This guideline is specifically for Deaf individuals whose primary language is sign language — not all deaf/hard-of-hearing users.

  • Inclusivity: According to the World Federation of the Deaf (WFD) , there are over 70 million Deaf people worldwide who use more than 300 different sign languages. In the United States, the National Association of the Deaf (NAD) reports that approximately 500,000 people use American Sign Language (ASL) as their primary language. For these individuals, written captions are not equivalent — sign language is their native language.
  • Educational Outcomes: Research from Gallaudet University demonstrates that Deaf students who receive instruction in their native sign language show significantly higher literacy rates and academic achievement compared to those who rely solely on written English. Native signers process visual-spatial information differently than text, making sign language interpretation essential for full comprehension.
  • Comprehension Gap: Studies show that for native signers, sign language comprehension rates can be 30-40% higher than reading equivalent written text, particularly for complex or technical content. Written English is effectively a second language for many Deaf individuals who use ASL, BSL, or other sign languages as their primary mode of communication.
  • Legal Compliance: This is a Level AAA requirement in WCAG 2.2 and is increasingly referenced in accessibility laws, particularly for government, educational, and public service content.
  • Cultural Recognition: Providing sign language interpretation recognizes Deaf culture as a distinct linguistic and cultural identity, not merely a medical condition requiring accommodation.

For more, see W3C's sign language docs and the NAD's position on sign language access .

⚠️ Scope Note: Sign Language vs. Captions

These are different accommodations for different user groups:

GuidelineUser GroupSolutionLanguage ModeWCAG Level
1.2.2 Captions (Prerecorded)Deaf/hard-of-hearing users who read English/textText captions synchronized with audioWritten languageA (required)
1.2.4 Captions (Live)Deaf/hard-of-hearing users who read English/textReal-time text captionsWritten languageAA (required)
1.2.6 Sign Language (Prerecorded)Culturally Deaf users whose primary language is sign languageSign language interpretation overlay/trackVisual-spatial language (ASL/BSL/etc.)AAA (aspirational)

Why BOTH may be needed: A video may require captions (1.2.2/1.2.4) for deaf users who prefer text AND sign language interpretation (1.2.6) for Deaf users who use sign language as their primary language. These are not interchangeable — they serve distinct communities with different communication preferences.

What You Can Do Right Now

Don't wait for an AAA compliance audit. Here's how to start:

  • 🔍 Audit Your Video Content: Review your video library and identify high-priority content (government services, educational materials, public health information, community announcements) that would most benefit the Deaf community. Prioritize content where sign language interpretation would significantly improve access for native signers.
  • 🛠️ Implement Sign Language Interpretation: Start with one high-impact video. Hire a certified sign language interpreter (see qualification standards below) and record interpretation as a picture-in-picture overlay or separate track. Test with Deaf community members who use sign language as their primary language.
  • 📢 Escalate to Decision-Makers: Share this guide with your video production team, content creators, and accessibility leads. Make the case that true inclusion means recognizing sign language as a distinct language — not just an alternative format for captions. Reference NAD and WFD advocacy for sign language access.
  • 📚 Learn More About Deaf Culture: Before implementing sign language interpretation, educate your team about Deaf culture and identity . Understanding that Deaf individuals form a linguistic and cultural community (not just people who "can't hear") will inform better, more respectful implementation decisions.

What Needs Sign Language Interpretation?
  • Prerecorded video content with audio (webinars, tutorials, online courses)
  • Any synchronized media with spoken content

All such media should have sign language interpretation available.

How to Provide Sign Language Interpretation
  • Record or embed a sign language interpreter in the video
  • Offer a separate sign language track or overlay
  • Make the sign language option easy to enable and view
  • Ensure interpretation is accurate and synchronized

For more, see W3C's sign language docs .

Implementation Examples

Option 1: Picture-in-Picture Sign Language Overlay (Most Common)

Embed the sign language interpreter directly in the video frame as a picture-in-picture overlay.

Best for: Government announcements, public health information, educational content where all users see the same video.

<video controls>
  <source src="public-service-announcement-with-asl.mp4" type="video/mp4" />
  <track kind="captions" src="captions-en.vtt" srclang="en" label="English" />
</video>
<p>This video includes American Sign Language (ASL) interpretation in the lower right corner.</p>

Production specs:

  • Interpreter positioned in lower right or lower left corner (consistent placement across all videos)
  • Minimum size: 25-30% of video frame width
  • High contrast background behind interpreter (solid color, not transparent)
  • Interpreter's hands, face, and upper body fully visible
  • No visual elements (text, graphics, main content) obstructing interpreter

Option 2: Side-by-Side Layout

Best for: Webinars, lectures, presentations where screen real estate allows dual display.

<div style="display: flex; gap: 1rem;">
  <video controls style="flex: 1;">
    <source src="lecture-main.mp4" type="video/mp4" />
  </video>
  <video controls style="flex: 1;">
    <source src="lecture-asl.mp4" type="video/mp4" />
  </video>
</div>
<p>Left: Main presentation | Right: ASL interpretation</p>

Option 3: Separate Sign Language Video Version

Best for: Platforms that don't support overlays, or when offering multiple regional sign languages (ASL, BSL, Auslan).

<video controls>
  <source src="tutorial.mp4" type="video/mp4" />
  <track kind="captions" src="captions-en.vtt" srclang="en" label="English" />
</video>

<h3>Sign Language Versions:</h3>
<ul>
  <li><a href="tutorial-asl.mp4">Watch with ASL (American Sign Language)</a></li>
  <li><a href="tutorial-bsl.mp4">Watch with BSL (British Sign Language)</a></li>
  <li><a href="tutorial-auslan.mp4">Watch with Auslan (Australian Sign Language)</a></li>
</ul>

Platform-Specific Considerations

YouTube:

  • Does not support separate sign language tracks
  • Bake sign language interpretation into the video itself (picture-in-picture)
  • Or upload separate video versions with ASL/BSL in the title

Vimeo:

  • Supports text captions via WebVTT
  • Does not natively support sign language video tracks
  • Use picture-in-picture or upload separate sign language versions

Custom HTML5 Players:

  • Can offer toggle button to show/hide sign language overlay
  • Can provide full-screen interpreter option
  • Consider Able Player which has built-in sign language support

Regional Sign Language Selection

Critical: Sign languages are NOT universal. ASL (American Sign Language) is different from BSL (British Sign Language), which is different from Auslan (Australian Sign Language), LSF (French Sign Language), etc.

  • United States: Use ASL certified interpreters (RID certification )
  • United Kingdom: Use BSL certified interpreters (NRCPD registration )
  • Australia: Use Auslan certified interpreters (ASLIA accreditation )
  • Canada: Use ASL or LSQ (Langue des signes québécoise) depending on region
  • International content: Offer multiple sign language versions or default to the region's primary sign language

Video Production Specs:

  • Frame rate: Minimum 30fps (sign language requires smooth motion; 60fps preferred for fast signing)
  • Resolution: Minimum 720p for interpreter visibility (1080p preferred)
  • Lighting: Consistent, shadow-free lighting on interpreter's face and hands
  • Background: Solid color contrasting with interpreter's skin tone (dark background for light skin, light background for dark skin)
  • Positioning: Interpreter centered in frame with full upper body visible (waist to top of head)
  • Camera angle: Straight-on, not angled or tilted

For technical guidance, see Gallaudet University's video production standards and NAD's best practices .

How to Test Your Sign Language Interpretation

Quick Visibility Tests
  1. Interpreter Visibility: Can you see the interpreter's face, hands, and upper body clearly at all times? No obstructions from text overlays, graphics, or other video elements?
  2. Synchronization: Is the sign language interpretation synchronized with the spoken audio? Test by comparing interpreter's signing to captions (if present) — they should match in timing.
  3. Contrast and Clarity: Is the background behind the interpreter high-contrast and solid (not busy patterns)? Can you distinguish hand shapes and facial expressions clearly?

Quality Checklist
  • Interpreter Qualifications: Is the interpreter certified by the regional authority (RID for US/ASL, NRCPD for UK/BSL, etc.)?
  • Regional Appropriateness: Does the sign language match your audience's region? (ASL for US, BSL for UK, Auslan for Australia, etc.)
  • Native/Near-Native Fluency: Is the interpreter a native or near-native signer, not someone who learned sign language as an adult foreign language?
  • Cultural Competency: Does the interpreter understand Deaf culture and community norms? (Critical for respectful, accurate interpretation)
  • Subject Matter Expertise: For technical content, does the interpreter have experience in that domain (medical, legal, educational, etc.)?
  • Lighting and Framing: Is the interpreter well-lit with no shadows on face or hands? Is the full upper body visible?
  • Frame Rate: Is the video at least 30fps? (Sign language requires smooth motion; choppy video makes comprehension difficult)
  • No Auto-Generated Sign Language: Confirm you are NOT using AI-generated or avatar-based sign language — these tools do not meet WCAG 1.2.6 and are often incomprehensible to native signers.

Deaf Community User Testing

The most important test: Have Deaf individuals who use sign language as their primary language review your video.

  • Recruit testers from local Deaf community organizations or schools for the Deaf
  • Ask specifically: "Is the interpretation clear, accurate, and culturally appropriate?"
  • Ask: "Would you recommend this video to other Deaf community members?"
  • Pay testers fairly for their expertise (they are providing professional review services)

For testing recruitment, contact NAD local chapters or Deaf community centers .

Common Questions

Isn't this the same as captions?

No. Captions serve deaf/hard-of-hearing users who read English or another written language. Sign language interpretation serves culturally Deaf users whose primary language is a sign language (ASL, BSL, etc.). For many native signers, written English is effectively a second language. Both captions (WCAG 1.2.2) and sign language interpretation (WCAG 1.2.6) may be needed to serve all users.

Which sign language should I use?

Match your audience's region:

  • United States: ASL (American Sign Language)
  • United Kingdom: BSL (British Sign Language)
  • Australia: Auslan (Australian Sign Language)
  • France: LSF (Langue des signes française)
  • International content: Offer multiple sign language versions or default to ASL (most widely used globally)

Remember: Sign languages are NOT universal. ASL and BSL are mutually unintelligible — they are distinct languages, not regional dialects.

Is WCAG 1.2.6 required for AA conformance?

No. Guideline 1.2.6 is Level AAA only — it is not required for A or AA conformance. However, AAA is best practice for government, education, public health, and public service content where true inclusion is the goal, not minimum compliance.

Can I use auto-generated or avatar-based sign language?

No. AI-generated sign language avatars and auto-translation tools do not meet WCAG 1.2.6. Sign language is a visual-spatial language with grammar, syntax, and cultural nuances that automated tools cannot accurately reproduce. Only qualified human interpreters provide the accurate, culturally competent interpretation required by this guideline. Using avatar tools may actually harm accessibility by providing incomprehensible or offensive "signing."

For guidance, see NAD's position on sign language avatars and WFD's statement on automated sign language .

What about deaf users who prefer captions over sign language?

Both may be needed. Not all deaf/hard-of-hearing users use sign language as their primary language. Some prefer written captions (WCAG 1.2.2). Best practice is to provide both captions and sign language interpretation so users can choose their preferred access method.

How much does sign language interpretation cost?

Costs vary based on:

  • Interpreter certification level and experience
  • Video length and complexity
  • Regional market rates (RID interpreters in the US typically charge $75-150/hour)
  • Rush or specialized content (medical, legal) may cost more

Budget for interpretation during video production planning — retrofitting sign language later is more expensive.

Do I need different interpreters for different topics?

Yes, for specialized content. Certified interpreters with subject matter expertise produce more accurate interpretation. For example:

  • Medical content: Interpreter with healthcare interpretation experience
  • Legal content: Certified Deaf Interpreter (CDI) or legal specialist
  • Technical/academic: Interpreter familiar with discipline-specific vocabulary

Consult RID's specialist certification programs for guidance.

Interpreter Qualifications

Critical: Only use certified, qualified sign language interpreters. Using unqualified signers produces inaccurate interpretation and may violate accessibility laws.

Certification Standards by Region

Interpreter Qualifications Checklist
  • Certified/Registered: Holds valid certification from regional authority (RID, NRCPD, ASLIA, etc.)
  • Native or Near-Native Fluency: Native signer or learned sign language at a young age (not adult-learned as foreign language)
  • Cultural Competency: Understands and respects Deaf culture, community norms, and identity
  • Subject Matter Expertise: For technical content, has experience interpreting in that domain (medical, legal, educational, etc.)
  • Ethical Standards: Adheres to RID Code of Professional Conduct or equivalent regional ethics code
  • Ongoing Professional Development: Participates in continuing education to maintain certification

Where to Find Qualified Interpreters

Never:

  • Use unqualified signers (family members, friends, students)
  • Use AI-generated or avatar-based sign language
  • Assume someone who knows "some sign language" can interpret professionally

For hiring guidance, see NAD's guide to working with interpreters and RID's consumer resources .

Common Mistakes to Avoid
  • No sign language interpretation for video content
  • Interpretation that is out of sync or hard to see
  • Not making the sign language option easy to find
  • Using unqualified interpreters

Audit your site regularly and use accessibility checkers to ensure all video content has proper sign language interpretation. For more, see ADA.gov's Effective Communication guidance .

Differences Between A, AA, and AAA for Guideline 1.2.6 in WCAG 2.2
  • Level A: No requirement for 1.2.6.
  • Level AA: No requirement for 1.2.6.
  • Level AAA: Requires sign language interpretation for all prerecorded audio content in synchronized media. This is the core requirement for 1.2.6 and is mandatory for AAA conformance.

For more, see the W3C’s official documentation for 1.2.6 Sign Language (Prerecorded).

🎯 AAA Level: Aspirational, Not Required — But Best Practice for True Inclusion

Important context: AAA conformance is not required for most websites. WCAG 2.2 Level AA is the international standard for web accessibility and the target for most compliance frameworks (ADA, Section 508, etc.).

However, AAA guidelines like 1.2.6 represent best practices for going beyond compliance to achieve true inclusion:

  • Government and public service content: Agencies serving diverse populations should aspire to AAA to ensure no one is excluded
  • Educational institutions: Schools, universities, and online learning platforms should provide sign language interpretation to serve Deaf students equitably
  • Healthcare and public health: Medical information should be accessible in users' primary languages — including sign languages
  • Community and advocacy organizations: Groups serving the Deaf community should model AAA practices

The distinction matters: Meeting Level AA (captions for deaf users) is required. Meeting Level AAA (sign language for Deaf users) is aspirational — but it's the difference between minimum legal compliance and recognizing sign language as a distinct, equal language.

For guidance on AAA adoption, see W3C's Understanding Conformance and NAD's advocacy for sign language access.

Quick Checklist
  • All prerecorded video content with audio has sign language interpretation
  • Interpretation is accurate and synchronized
  • Sign language option is easy to enable and view
  • Interpreters are qualified and clear
  • Tested with users and assistive technology

Summary

Guideline 1.2.6 is essential for making video content accessible to culturally Deaf users whose primary language is sign language. By providing certified, qualified sign language interpretation, you recognize Deaf culture and linguistic diversity, improve comprehension for native signers, and meet AAA best practices. Make sign language interpretation a standard part of your video production process — and consult with the Deaf community to ensure your implementation is accurate, respectful, and truly inclusive.

Key resources: