All technologies that include interactive controls (such as links or form inputs).
This technique relates to Success Criterion 2.5.3: Label in Name (Failure).
The objective of this Failure is to describe situations where speech input users cannot reliably speak the name of a control because it differs from the visible label.
When speech input users interact with a web page, they usually speak a command followed by the reference to some visible label (like the text in a button or a link, or the text labelling some input). If the visible label does not match the accessible name of the control, speech users may be unable to directly activate that control.
There are techniques that go beyond the visible label text of elements. The idea is to provide more context for users of assistive technologies to whom the visible context may not be available. Examples are the use of accessible hidden (e.g., offscreen-positioned) text, the use of the aria-label attribute to overwrite the label text, or the use of the aria-labelledby attribute to compose a label text from one or more strings strings on the page.
When the use of these techniques results in an accessible name in which the exact string of the visible label does not occur in the accessible name, speech users may be unable to activate that control. Refer to the Accessible Name and Description Computation algorithm to work out the order of precedence in computing the accessible name of a control.
For all controls with a visible label (e.g., link text, button text, programmatically linked label, images in links with text), check that:
- The accessible name is the same as the visible label.
- The accessible name contains a match for the string of the visible label.
- If checks #1 and #2 are false, the content fails the Success Criterion.