WCAG 1.2.2 Captions — Testing Guide for Mobile & Web Apps

WCAG 1.2.2, "Captions (Prerecorded)," is a foundational accessibility requirement focusing on providing synchronized captions for all pre-recorded audio content within media. This means any spoken dia

Ensuring Captions for Pre-recorded Audio: A Practical Guide to WCAG 1.2.2

WCAG 1.2.2, "Captions (Prerecorded)," is a foundational accessibility requirement focusing on providing synchronized captions for all pre-recorded audio content within media. This means any spoken dialogue, important sound effects, or other audio cues in videos or audio-only files must have corresponding text displayed on screen. This is a Level A success criterion, meaning it's a basic requirement for making content accessible to a wide range of users.

What WCAG 1.2.2 Requires

In straightforward terms, if your application plays a video or audio file that has sound, you must provide captions. These captions should accurately represent everything that is said and any non-speech sounds that are crucial for understanding the content. This includes things like music if it's important to the narrative, or sound effects that convey an action. The captions must be synchronized with the audio, appearing on screen at the same time the sound is heard.

Why Captions Matter: Real User Impact

The necessity of captions extends far beyond a mere compliance checkbox. They are critical for individuals who are deaf or hard of hearing, enabling them to fully engage with and understand multimedia content. However, the benefits are far-reaching:

• Cognitive Disabilities: Users with cognitive disabilities, such as those with attention deficit disorders, can benefit from seeing the text, which aids comprehension and retention.
• Learning Environments: Students often use captions to reinforce learning, especially when encountering unfamiliar terminology or accents.
• Noisy or Quiet Environments: Users in loud public spaces (like a train) or quiet environments where audio playback is not feasible can read captions to follow along.
• Non-Native Speakers: For individuals learning a new language, captions provide a valuable tool for understanding spoken content and improving their language skills.
• Searchability: Captioned content is inherently more searchable, benefiting all users who might want to find specific information within a video or audio file.

Consider the impact of a banking app's tutorial video on financial planning being inaccessible to a deaf user. They would miss crucial information, potentially leading to poor financial decisions. Similarly, a news app failing to caption a video report on a public health crisis excludes a significant portion of the population from vital information, a concern highlighted by regulations like the EU's European Accessibility Act (EAA) and the Americans with Disabilities Act (ADA) in the US.

Common Violations and Examples

Violations of WCAG 1.2.2 often occur due to oversight or a lack of understanding of its scope. Here are common scenarios:

Mobile Apps:

1. Informational Videos with Dialogue: A mobile banking app features a short video explaining how to set up a new savings account. The video contains spoken instructions and visual cues. If no captions are present, deaf users cannot follow the setup process.
2. Marketing Videos with Sound Effects: A retail app uses a promotional video showcasing a new product. The video includes dialogue and sound effects like a "ding" to highlight a feature. If the "ding" sound is crucial to understanding the benefit, its absence in captions creates a barrier.
3. User-Generated Content (Less Common for strict prerecorded): While less common for *prerecorded* content, if a platform allows users to upload videos with spoken content and these are intended as part of the core app experience without moderation for captions, it can lead to violations.

Web Applications:

1. Tutorials and Demonstrations: A web-based learning platform hosts video lectures or software demonstrations. If these videos include spoken explanations and no captions, students who are deaf or hard of hearing will struggle to learn the material.
2. News Broadcasts or Documentaries: A news website embeds pre-recorded video segments of news reports or short documentaries. The spoken content and key sound effects must be captioned.
3. Product Demonstrations on E-commerce Sites: An online store uses videos to showcase how a product works. If the narration or important audio cues are not captioned, potential customers with hearing impairments may not fully grasp the product's functionality.

Testing for WCAG 1.2.2 Compliance

A multi-pronged approach ensures robust compliance.

#### Manual Testing Steps

1. Identify all pre-recorded media: Audit your application for any videos or audio files that play automatically or are initiated by user action.
2. Play the media: Observe the audio content carefully. Listen to all spoken dialogue and significant non-speech sounds.
3. Check for captions: Look for a caption track or a CC (Closed Captions) button.
4. Enable captions: If captions are available, turn them on.
5. Verify accuracy and synchronization:

• Read the captions while listening to the audio. Do they accurately reflect what is being said?
• Are the captions appearing and disappearing in sync with the audio?
• Do the captions describe important non-speech sounds (e.g., [door slams], [applause])?

1. Test without audio: Mute your device's audio. Can you still understand the essential information conveyed by the video through the captions alone?

#### Automated Tools

While manual verification is crucial for nuance, automated tools can flag potential issues.

• Browser Developer Tools: Many browsers offer accessibility testing tools that can identify missing caption tracks for web-based media.
• Dedicated Accessibility Checkers: Tools like WAVE, AXE, or Lighthouse can scan web pages and report on various accessibility issues, including potential captioning problems.
• Video Editing Software: Many professional video editing suites include captioning tools and can export caption files (e.g., .srt, .vtt). These tools can help verify the format and accuracy of existing captions.

#### Mobile-Specific Considerations

• Platform Native Players: On Android and iOS, media players often have built-in captioning support. Ensure your app correctly leverages these features.
• Third-Party Libraries: If using custom video players or third-party libraries, verify their captioning compatibility and how they handle caption rendering.
• Device Settings: Test with device-level captioning settings enabled and disabled to ensure your app's behavior is consistent.

Fixing Violations

The primary solution is to provide accurate, synchronized captions.

1. Generate Captions:

• Manual Transcription: Hire a transcription service or transcribe the audio yourself.
• Automated Transcription Services: Utilize AI-powered services (e.g., rev.com, Happy Scribe) for initial drafts, but always review and edit for accuracy.

1. Create Caption Files: Generate caption files in standard formats like WebVTT (.vtt) for web and .srt for broader compatibility.
2. Integrate Captions:

• Web: For HTML5 video, use the element:

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

• Mobile (Android/iOS): Integrate captioning through the native media playback APIs or your chosen video player SDK. Ensure the player is configured to load and display the caption track.

1. Include Non-Speech Sounds: Do not forget to caption important sound effects or music cues that convey meaning.

How SUSA Checks for WCAG 1.2.2

SUSA (SUSATest) autonomously explores your application, mimicking diverse user behaviors, and identifies accessibility violations, including those related to WCAG 1.2.2.

• Autonomous Exploration: SUSA's AI navigates through your app, encountering pre-recorded media. It doesn't rely on pre-written scripts for this discovery phase.
• Media Detection: During its exploration, SUSA identifies embedded videos and audio players.
• Caption Analysis: For detected media, SUSA checks for the presence and proper implementation of caption tracks. It can detect if a caption option is available and if it's being rendered correctly.
• Persona-Based Testing: SUSA's 10 user personas are crucial here. For instance, its "curious" or "novice" personas might interact with media in ways that reveal missing captions. More importantly, the "accessibility" persona is specifically designed to probe for these types of barriers.
• WCAG 2.1 AA Compliance: SUSA performs WCAG 2.1 AA testing as part of its autonomous runs. While 1.2.2 is Level A, SUSA's comprehensive testing suite covers it.
• Reporting: SUSA flags any identified issues, including missing or improperly implemented captions, providing actionable insights in its reports. It can identify the specific screen or component where the violation occurs.
• Regression Script Generation: After identifying issues, SUSA can auto-generate Appium (for Android) or Playwright (for Web) regression test scripts. This means if you fix a captioning issue, future automated runs will verify that the fix remains in place.

By integrating SUSA into your QA process, you gain a powerful tool to proactively identify and address WCAG 1.2.2 violations, ensuring your applications are usable by a broader audience and compliant with accessibility standards.