Audio output
This test aspect includes all auditory data output from the web page into an audio channel.
Video element auditory content has captions
This rule checks that captions are available for audio information in non-streaming video
elements.
This rule applies to every non-streaming video
element that is visible where the video contains audio.
For each test target, audio information that is not conveyed visually in the video, is available through captions.
Note: Captions can be either embedded in the video file itself or can be made available trough a separate track.
This rule assumes that the video element is used to play a video (for example, not only used to display an image), and that there is a mechanism to start the video.
There are no major accessibility support issues known for this rule.
A video element that has captions for all the audio baked into it.
<video src="/test-assets/perspective-video/perspective-video-with-captions.mp4" controls></video>
A video element with an associated track element that contain captions for all the audio.
<video src="/test-assets/perspective-video/perspective-video.mp4" controls>
<track src="/test-assets/perspective-video/perspective-caption.vtt" kind="captions" />
</video>
A video element without any form of captions.
<video src="/test-assets/perspective-video/perspective-video.mp4" controls></video>
A video element with an associated track element that contain incorrect captions.
<video src="/test-assets/perspective-video/perspective-video.mp4" controls>
<track src="/test-assets/perspective-video/perspective-incorrect-caption.vtt" kind="captions" />
</video>
A video element with a text on the same page that described the audio in the video.
<p>
The video below shows a man working on a keyboard. A voiceover is heard saying the following text: Web accessibility
perspectives. Keyboard compatibility. Not being able to use your computer because your mouse doesn't work, is
frustrating. Many people use only the keyboard to navigate websites. Either through preference or circumstance.
</p>
<video src="/test-assets/perspective-video/perspective-video.mp4" controls></video>
A video element with an explicitly associated text on the same page that described the audio in the video.
<p id="text">
The video below shows a man working on a keyboard. A voiceover is heard saying the following text: Web accessibility
perspectives. Keyboard compatibility. Not being able to use your computer because your mouse doesn't work, is
frustrating. Many people use only the keyboard to navigate websites. Either through preference or circumstance.
</p>
<video src="/test-assets/perspective-video/perspective-video.mp4" controls ariadescribedby="text"></video>
A video element without audio.
<video src="/test-assets/perspective-video/perspective-video-silent.mp4" controls></video>
A video element that is not visible.
<video src="/test-assets/perspective-video/perspective-video.mp4" controls style="display: none;"></video>
This test aspect includes all auditory data output from the web page into an audio channel.
A non-streaming media element is an HTML Media Element for which the duration
property is not 0.
An outcome is a conclusion that comes from evaluating an ACT Rule on a test subject or one of its constituent test target. An outcome can be one of the three following types:
Note: A rule has one passed
or failed
outcome for every test target. When there are no test targets the rule has one inapplicable
outcome. This means that each test subject will have one or more outcomes.
Note: Implementations using the EARL10-Schema can express the outcome with the outcome property. In addition to passed
, failed
and inapplicable
, EARL 1.0 also defined an incomplete
outcome. While this cannot be the outcome of an ACT Rule when applied in its entirety, it often happens that rules are only partially evaluated. For example, when applicability was automated, but the expectations have to be evaluated manually. Such "interim" results can be expressed with the incomplete
outcome.
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.
For more details, see examples of visible.
This section is not part of the official rule. It is populated dynamically and not accounted for in the change history or the last modified date. This section will not be included in the rule when it is published on the W3C website.
Tool | Consistency | Complete | Report |
---|---|---|---|
QualWeb | consistent | Yes | View Report |