Last updated:

Created by:

Success Criterion:

Description

Non-streaming video elements must have all audio and visual information available in a transcript.

Accessibility Requirements

This conformance rule relates to:

Test Procedure

Applicability

The rule applies to every non-streaming video element that is visible where the video contains audio.

Expectation

A text transcript containing all the visual and auditory information of the test target is available, either on the page or available through a link.

Note: A “text transcript” in the context of this rule is defined in WCAG 2 as a alternative for time based media.

Assumptions

This rule assumes that a mechanism is available to start the video and that the video element is not simply used to display the poster.

Accessibility support

There are no major accessibility support issues known for this rule.

Background

Test Cases

Passed

Passed example 1

A video element with a text transcript on the same page.

Code Snippet:
 <video controls>
  <source src="../test-assets/rabbit-video/video.mp4" type="video/mp4"></source>
  <source src="../test-assets/rabbit-video/video.webm" type="video/webm"></source>
</video>
<p>The above video shows a giant fat rabbit climbing out of a hole in the ground. 
He stretches, yaws, and then starts walking. 
Then he stops to scratch his bottom.</p>
 
Example Output: Open in a new tab/ window

Passed example 2

A video element with a link to a text transcript on a different page.

Code Snippet:
 <video controls>
  <source src="../test-assets/rabbit-video/video.mp4" type="video/mp4"></source>
  <source src="../test-assets/rabbit-video/video.webm" type="video/webm"></source>
</video>
<a href="../test-assets/rabbit-video/transcript.html">Transcript</p>
 
Example Output: Open in a new tab/ window

Failed

Failed example 1

A video element with an incorrect text transcript on the same page.

Code Snippet:
 <video controls>
  <source src="../test-assets/rabbit-video/video.mp4" type="video/mp4"></source>
  <source src="../test-assets/rabbit-video/video.webm" type="video/webm"></source>
</video>
<p>The above video shows a giant fat dog climbing out of a hole in the ground. 
He stretches, yaws, and then starts walking. 
Then he stops to scratch his bottom.</p>
 
Example Output: Open in a new tab/ window

Failed example 2

A video element with a link to an incorrect text transcript on a different page.

Code Snippet:
 <video controls>
  <source src="../test-assets/rabbit-video/video.mp4" type="video/mp4"></source>
  <source src="../test-assets/rabbit-video/video.webm" type="video/webm"></source>
</video>
<a href="../test-assets/rabbit-video/incorrect-transcript.html">Transcript</p>
 
Example Output: Open in a new tab/ window

Inapplicable

Inapplicable example 1

A video element that is not visible on the page.

Code Snippet:
 <video controls style="display: none;">
  <source src="../test-assets/rabbit-video/video.mp4" type="video/mp4"></source>
  <source src="../test-assets/rabbit-video/video.webm" type="video/webm"></source>
</video>
<a href="../test-assets/rabbit-video/transcript.html">Transcript</p>
 
Example Output: Open in a new tab/ window

Inapplicable example 2

A video element without audio.

Code Snippet:
 <video controls>
  <source src="../test-assets/rabbit-video/silent.mp4" type="video/mp4"></source>
  <source src="../test-assets/rabbit-video/silent.webm" type="video/webm"></source>
</video>
<a href="../test-assets/rabbit-video/transcript.html">Transcript</p>
 
Example Output: Open in a new tab/ window

Glossary

Visible

Content perceivable through sight.

Content is considered visible if making it fully transparent would result in a difference in the pixels rendered for any part of the document that is currently within the viewport or can be brought into the viewport via scrolling.

Content is defined in WCAG.

Test Aspects

Test aspects are defined as part of the ACT Rules format 1.0.
  • DOM Tree

  • CSS Styling

  • Audio output

  • Visual output

Contribute






GitHub

Contributing is open to anyone. We welcome any new issues or pull requests for changes. Auto WCAG Rules has conference calls every 4 weeks. If you are interested in becoming an active contributor or reviewer, we ask that you join the Auto WCAG Rules community group through the W3C Website. This requires setting up a W3C account, may require approval by the organization you work for if they are a W3C member.

Learn more about contributing to Auto WCAG Rules Join the Auto WCAG Rules community group now!