Proposed Video element visual content has description track
Deprecated
This rule has been deprecated as descriptions tracks were removed in #1665 as a way to provide video alternative. This rule is not maintained anymore and should not be used.
Description
This rule checks that description tracks that come with non-streaming video
elements are descriptive.
Applicability
This rule applies to every non-streaming video
element that is visible where the video contains audio and a track
element with a kind
attribute value of descriptions
.
Expectation
The visual information of each test target not available through its audio is described with a description track
element.
Note: Multiple description track
elements may be useful for different languages, but at least one must match the language of the video.
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
Currently the description track is not supported by most assistive technology. Accessibility support for the description track attribute is relatively low to non-existent. Video players may be able to work around the lack of support for the description track by using aria-live but few do this today.
This means that the rule can only provide a pass for these success criteria if assistive technology support the description track or if the video player that is used has implemented such a work around.
Background
Bibliography
- Understanding Success Criterion 1.2.3: Audio Description or Media Alternative (Prerecorded)
- Understanding Success Criterion 1.2.5: Audio Description (Prerecorded)
- G78: Providing a second, user-selectable, audio track that includes audio descriptions
- H96: Using the track element to provide audio descriptions
Accessibility Requirements Mapping
G78: Providing a second, user-selectable, audio track that includes audio descriptions
- Learn more about technique G78
- Not required for conformance to any W3C accessibility recommendation.
- Outcome mapping:
- Any
failed
outcomes: technique is not satisfied - All
passed
outcomes: technique needs further testing - An
inapplicable
outcome: technique needs further testing
- Any
H96: Using the track element to provide audio descriptions
- Learn more about technique H96
- Not required for conformance to any W3C accessibility recommendation.
- Outcome mapping:
- Any
failed
outcomes: technique is not satisfied - All
passed
outcomes: technique needs further testing - An
inapplicable
outcome: technique needs further testing
- Any
Input Aspects
The following aspects are required in using this rule.
- DOM Tree
- CSS Styling
- Audio output
- Visual output (no link available)
- Language
Test Cases
Passed
Passed Example 1
A video element with a track element that contains descriptions.
<html lang="en">
<video controls>
<source src="/test-assets/rabbit-video/video.mp4" type="video/mp4" />
<source src="/test-assets/rabbit-video/video.webm" type="video/webm" />
<track kind="descriptions" src="/test-assets/rabbit-video/descriptions.vtt" />
</video>
</html>
Failed
Failed Example 1
A video element with a track element that contains incorrect descriptions.
<html lang="en">
<video controls>
<source src="/test-assets/rabbit-video/video.mp4" type="video/mp4" />
<source src="/test-assets/rabbit-video/video.webm" type="video/webm" />
<track kind="descriptions" src="/test-assets/rabbit-video/incorrect-descriptions.vtt" />
</video>
</html>
Inapplicable
Inapplicable Example 1
A video element without a track element.
<html lang="en">
<video controls>
<source src="/test-assets/rabbit-video/video.mp4" type="video/mp4" />
<source src="/test-assets/rabbit-video/video.webm" type="video/webm" />
</video>
</html>
Inapplicable Example 2
A video element that is not visible.
<html lang="en">
<video controls style="display: none;">
<source src="/test-assets/rabbit-video/video.mp4" type="video/mp4" />
<source src="/test-assets/rabbit-video/video.webm" type="video/webm" />
<track kind="descriptions" src="/test-assets/rabbit-video/descriptions.vtt" />
</video>
</html>
Inapplicable Example 3
A video element without audio.
<html lang="en">
<video controls>
<source src="/test-assets/rabbit-video/silent.mp4" type="video/mp4" />
<source src="/test-assets/rabbit-video/silent.webm" type="video/webm" />
<track kind="descriptions" src="/test-assets/rabbit-video/descriptions.vtt" />
</video>
</html>
Glossary
Attribute value
The attribute value of a content attribute set on an HTML element is the value that the attribute gets after being parsed and computed according to specifications. It may differ from the value that is actually written in the HTML code due to trimming whitespace or non-digits characters, default values, or case-insensitivity.
Some notable case of attribute value, among others:
- For enumerated attributes, the attribute value is either the state of the attribute, or the keyword that maps to it; even for the default states. Thus
<input type="image" />
has an attribute value of eitherImage Button
(the state) orimage
(the keyword mapping to it), both formulations having the same meaning; similarly, “an input element with atype
attribute value ofText
” can be either<input type="text" />
,<input />
(missing value default), or<input type="invalid" />
(invalid value default). - For boolean attributes, the attribute value is
true
when the attribute is present andfalse
otherwise. Thus<button disabled>
,<button disabled="disabled">
and<button disabled="">
all have adisabled
attribute value oftrue
. - For attributes whose value is used in a case-insensitive context, the attribute value is the lowercase version of the value written in the HTML code.
- For attributes that accept numbers, the attribute value is the result of parsing the value written in the HTML code according to the rules for parsing this kind of number.
- For attributes that accept sets of tokens, whether space separated or comma separated, the attribute value is the set of tokens obtained after parsing the set and, depending on the case, converting its items to lowercase (if the set is used in a case-insensitive context).
- For
aria-*
attributes, the attribute value is computed as indicated in the WAI-ARIA specification and the HTML Accessibility API Mappings.
This list is not exhaustive, and only serves as an illustration for some of the most common cases.
The attribute value of an IDL attribute is the value returned on getting it. Note that when an IDL attribute reflects a content attribute, they have the same attribute value.
Non-streaming media element
A non-streaming media element is an HTML Media Element for which the duration
property is not 0.
Outcome
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:
- Inapplicable: No part of the test subject matches the applicability
- Passed: A test target meets all expectations
- Failed: A test target does not meet all expectations
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.
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.
For more details, see examples of visible.
Rule Versions
This is the first version of this ACT rule.