The 2025 TestParty Guide to WCAG 1.2.8 – Media Alternative (Prerecorded) (Level AAA)

Why did the accessibility specialist write a screenplay for every video? Because WCAG 1.2.8 said "lights, camera, transcription!"

WCAG 1.2.8 requires a full text alternative—essentially a screenplay or detailed narrative—for all prerecorded synchronized media (video with audio) and video-only content. This goes beyond captions and audio descriptions to provide a complete, readable document that captures everything happening in the media. It's the gold standard for accessibility, ensuring that users who are deaf-blind or prefer reading can access 100% of your multimedia content.

Table of Contents

• What WCAG 1.2.8 Requires
• Why This Matters
• Quick Implementation Guide
• Common Mistakes to Avoid
• How to Test for WCAG 1.2.8
• How TestParty Helps
• FAQs

What WCAG 1.2.8 Requires

WCAG 1.2.8 mandates a comprehensive text alternative for prerecorded multimedia content. Think of it as a screenplay or detailed transcript that describes both the audio track and all visual information.

What needs a media alternative:

• Synchronized media: Any prerecorded video with an audio track (training videos, webinars, product demos, marketing videos)
• Video-only content: Silent videos that convey information through visuals alone (animations, demonstrations, visual tutorials)

Key characteristics of a compliant media alternative:

• Includes all dialogue and narration (like a transcript)
• Describes all meaningful visual information (actions, settings, on-screen text, speaker identification)
• Captures sound effects and music when relevant to understanding
• Presented in reading order that makes sense sequentially
• Clearly labeled as an alternative to the media content

What's exempt:

• Live content (covered by other criteria)
• Media that is itself an alternative to text (e.g., a video version of a written article, if clearly labeled)
• Pure decoration or ambient content with no informational purpose

This is a Level AAA requirement, meaning it's not legally mandated for most compliance frameworks but represents best practice for maximum accessibility.

Why This Matters

Media alternatives serve users who cannot access video or audio content through conventional means. Deaf-blind users rely on refreshable braille displays to consume content—captions and audio descriptions don't help them. Users with cognitive disabilities may prefer reading at their own pace rather than processing time-based media.

Legal and compliance context:

While WCAG 1.2.8 is Level AAA and not required for baseline ADA or Section 508 compliance, some organizations adopt AAA standards voluntarily. Government agencies pursuing enhanced accessibility, educational institutions serving diverse learners, and organizations with specific contractual obligations may need to meet this criterion. The European Accessibility Act and EN 301 549 reference WCAG AA as the baseline, but many organizations exceed that threshold.

Business benefits:

Media alternatives improve SEO—search engines can index the full text of your video content. They provide repurposable content for blog posts, documentation, and social media. Users in sound-sensitive environments (open offices, public transit) can read instead of watch. And they demonstrate a genuine commitment to inclusive design that goes beyond legal minimums.

Quick Implementation Guide

Creating a media alternative is straightforward but requires effort. Here's how to do it right:

1. Write a comprehensive document that includes: - All spoken dialogue and narration - Speaker identification when multiple people appear - Descriptions of meaningful visual content (actions, settings, on-screen text, graphics) - Relevant sound effects and music cues - Scene changes and transitions

2. Structure it for readability: - Use headings to break up long documents - Format speaker names consistently (e.g., Jane: or [Jane]:) - Describe visuals in brackets or italics to distinguish from dialogue

3. Link it clearly from the media player:

<div class="video-container">
  <video controls>
    <source src="product-demo.mp4" type="video/mp4">
    <track kind="captions" src="captions.vtt" srclang="en" label="English">
  </video>
  <p>
    <a href="/transcripts/product-demo-full-transcript.html">
      Read the full text alternative for this video
    </a>
  </p>
</div>

4. Consider using the `<object>` element with fallback content:

<object data="training-video.mp4" type="video/mp4">
  <div class="media-alternative">
    <h2>Training Video: Onboarding Process</h2>
    <p><strong>Scene 1:</strong> The video opens with the company logo...</p>
    <p><strong>Narrator:</strong> Welcome to Acme Corp. This training will guide you through...</p>
    <!-- Full alternative continues -->
  </div>
</object>

5. Label it explicitly so users know it's an alternative, not supplementary content.

Relevant WCAG techniques: G69 (Providing an alternative for time-based media), G159 (Alternative for video-only content), H53 (Using the body of the object element).

Common Mistakes to Avoid

Even well-intentioned teams make these errors when implementing media alternatives:

Not labeling the alternative clearly: Users need to know the text document is a full alternative to the video, not just a transcript or summary. Use explicit language like "Full text alternative" or "Complete media alternative for [video title]."

Providing only a transcript: A transcript captures dialogue but omits visual information. A media alternative must describe what's happening on screen—who's speaking, what they're doing, what text or graphics appear, and relevant environmental details.

Omitting meaningful visual content: If a training video shows someone clicking through software, your alternative must describe those actions. If a product demo highlights features with on-screen callouts, describe them. Visual information is content.

Failing to maintain the alternative: When you update a video, the media alternative must be updated too. Outdated alternatives confuse users and fail the criterion.

How to Test for WCAG 1.2.8

Testing for media alternatives requires manual review. Here's your checklist:

Automated checks (limited):

• Scan for the presence of links or references near video elements
• Verify that linked documents are accessible (proper HTML structure, headings, etc.)
• Confirm that alternatives are not hidden or removed from the accessibility tree

Manual review (essential):

• Watch or view the media content in full
• Read the provided text alternative alongside it
• Verify that all dialogue, narration, visual information, and relevant sound is captured
• Confirm the alternative is clearly labeled as such
• Check that the reading order makes logical sense
• Ensure the alternative is accessible to screen readers and braille displays

What to look for:

• Is every speaker identified?
• Are on-screen text, graphics, and animations described?
• Are scene changes and visual transitions noted?
• Can someone who has never seen the video understand the full content from the text alone?

How TestParty Helps

TestParty automates the detection of missing or improperly labeled media alternatives and guides your team through creating compliant solutions.

What TestParty detects:

TestParty's automated scanning identifies <video>, <audio>, and <object> elements in your codebase and flags those lacking accessible alternatives. It checks for:

• Video and audio elements without adjacent or linked text alternatives
• Unlabeled or ambiguously labeled links near media players
• Media alternatives that are hidden from assistive technology (e.g., aria-hidden="true" or display: none without proper disclosure controls)
• Inaccessible alternative documents (PDFs without tagging, HTML without proper structure)

For organizations pursuing AAA compliance, TestParty's scans surface every multimedia element that requires a media alternative, creating a clear remediation roadmap.

How TestParty suggests fixes:

While TestParty cannot auto-generate the content of a media alternative (that requires human understanding of the video), it provides:

• Templated code snippets for linking to or embedding media alternatives
• Guidance on labeling conventions ("Full text alternative for [video title]")
• Recommendations for structuring alternative documents with proper headings and semantic HTML
• Integration with your content management workflow to flag videos uploaded without accompanying alternatives

TestParty's AI can analyze video metadata, filenames, and surrounding page context to suggest placeholder text and remind content teams to complete the alternative before publishing.

Developer workflow integration:

TestParty integrates into your CI/CD pipeline and pull request workflow to catch missing media alternatives before they reach production:

• Pre-merge checks: When a developer or content editor adds a new video element, TestParty flags it in the PR if no alternative is linked or embedded
• CI/CD gates: Block deployments that introduce new multimedia content without compliant alternatives (configurable for AAA enforcement)
• IDE annotations: Real-time feedback in code editors when video elements lack proper alternative references

This shift-left approach prevents regressions. Once you've achieved AAA compliance for existing media, TestParty ensures new content meets the same standard.

Ongoing monitoring:

TestParty's dashboard tracks media alternative compliance across your entire digital estate:

• Inventory of all multimedia elements and their alternative status
• Trend reports showing compliance improvements over time
• Alerts when updates to media content aren't reflected in alternatives
• Audit-ready reports for procurement, legal, or certification processes

For large organizations with hundreds or thousands of videos, TestParty provides the visibility needed to manage AAA compliance at scale.

Some TestParty features described in this article are currently under development. Visit TestParty.ai to learn more about our current capabilities and roadmap, or book a demo at TestParty.ai/book-a-demo to see TestParty in action.

Disclaimer: Some of this article was generated with Large Language Models (LLMs) and Artificial Intelligence (AI). There may be some errors and we advise you to consult with human professionals for detailed questions.

FAQs About WCAG 1.2.8

What is WCAG 1.2.8 in plain language?

WCAG 1.2.8 requires a full text alternative—like a detailed screenplay—for all prerecorded videos and synchronized media. This goes beyond captions to include descriptions of all visual content, making multimedia fully accessible to users who cannot see or hear it, including deaf-blind users who rely on braille displays.

Is WCAG 1.2.8 required for ADA compliance?

No, WCAG 1.2.8 is a Level AAA criterion and is not required for baseline ADA, Section 508, or EN 301 549 compliance (which mandate Level AA). However, some organizations adopt AAA standards voluntarily to provide enhanced accessibility or meet specific contractual obligations.

How is a media alternative different from captions and audio descriptions?

Captions provide text for spoken dialogue and sound effects. Audio descriptions add narration for visual content. A media alternative combines both into a single, comprehensive text document that can be read sequentially, making it accessible to users who cannot access time-based media at all, such as deaf-blind users.

Can I use an extended transcript as a media alternative?

Yes, if the transcript includes all visual information—not just dialogue. A standard transcript captures what's said; a media alternative (or extended transcript) captures what's said and what's shown. If your transcript describes actions, settings, on-screen text, and speaker identification, it qualifies as a media alternative.

Do I need a media alternative if I already have captions and audio descriptions?

For Level AAA compliance, yes. Captions and audio descriptions are separate tracks that require time-based media playback. A media alternative is a static text document that users can read, search, and navigate at their own pace. It serves users who cannot or prefer not to engage with video or audio formats.