Audio-only as a media alternative for text
Last updated:
Created by:
Last updated:
Created by:
This rule checks audio
is a media alternative for text on the page.
The rule applies to every non-streaming audio
element that is:
Note: A play button is an interactive element that when activated, plays the audio.
The auditory information of each test target is available as text (directly or via text alternatives) that is visible and included in the accessibility tree.
Each target element is labelled as an audio alternative for text on the page.
The label (from expectation 2) is visible and included in the accessibility tree
Note: The term label does not refer to the label
element.
There are currently no assumptions
There are no major accessibility support issues known for this rule.
An audio element that describes some of the text on the same page. The text on the page labels the audio as an alternative.
An audio element that describes some of the text on the same page. The audio contains more information than the text does.
An audio element that describes some of the text on the same page. The text is not visible on the page.
An audio element that describes some of the text on the same page. The text on the page does not label the audio as an alternative.
An audio element that describes some of the text on the same page. The text on the page labels the audio as an alternative but the label is not visible on the page.
An audio element that describes some of the text on the same page. The text on the page labels the audio as an alternative but the controls are not visible on the page.
An audio element that describes some of the text on the same page. The text on the page labels the audio as an alternative but there are no controls.
An HTML Media Element for which the duration
property is not 0.
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-hidden
attribute with a value oftrue
. 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.
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.
DOM Tree
CSS Styling
Audio output
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!