video only element has transcript
video elements without audio must have all visual information available in a transcript.
The visual information of each test target is available through a text transcript that is available either on the page or through a link. The text transcript needs to be visibile and included-in-the-accessibility-tree.
Note: A “text transcript” in the context of this rule is defined in WCAG 2 as an alternative for time based media.
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.
There are no major accessibility support issues known for this rule.
A silent video element with a text transcript on the same page.
A silent video element with a link to a text transcript on a different page.
A silent video element with an incorrect text transcript on the same page.
A silent video element with a link to an incorrect text transcript on a different page.
A silent video element with an invisible text transcript on the same page.
A silent video element with a text transcript on the same page that is not included in the accessibility tree.
A silent video element that is not visible on the page.
A video element with audio.
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.
Elements included in the accessibility tree of platform specific accessibility APIs. Elements in the accessibility tree are exposed to assistive technologies, allowing users to interact with the elements in a way that meet the requirements of the individual user.
The general rules for when elements are included in the accessibility tree are defined in the core accessibility API mappings. For native markup languages, such as HTML and SVG, additional rules for when elements are [included in the accessibility tree] can be found in the HTML accessibility API mappings and the SVG accessibility API mappings.
Note: Users of assistive technologies might still be able to interact with elements that are not included in the accessibility tree. An example of this is a focusable element with an
aria-hiddenattribute with a value of
true. Such an element could still be interacted with using sequential keyboard navigation regardless of the assistive technologies used, even though the element would not be included in the accessibility tree.
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!