For the purposes of this Label in Name Success Criterion, "label" is not
#Spell accessible code
However, it is worth noting that "label" in that HTML5 statement is in code bracketsĪnd links to the label element. The HTML5 specification states The placeholder attribute should not be used as an alternative to a. Note that placeholder text within an input field is not considered an appropriate Reading technologies to enjoy consistency between the nearby visible label and the With the element via its conventionally positioned label, and allows users of screen Interpretation of labeling allows users of speech recognition technologies to interact Testers, and end users to identify the label targeted for evaluation in this SC. The single string in close proximity to the component makes it easier for developers, Of this Success Criterion (SC) by lessening predictability. Liberal interpretations of what constitutes a text label can jeopardize the value It is important to bias towards treating only the adjacent text as a label because The rationale for some of these conventions is explained in G162: Positioning labels to maximize predictability of relationships. inside buttons and tabs or immediately below icons serving as buttons.immediately to the right of checkboxes and radio buttons.(or in the absence of left-side labels, immediately above and aligned with the left immediately to the left of comboboxes, dropdown lists, text inputs, and other widgets.The typical positioning for left to right languages is: Label as being only the text in close proximity.Ĭonventionally the label for user interface components is the adjacent text string. However, there are reasons why it is best to conservatively interpret the There are often multiple text strings in a user interface that may be relevant toĪ control.
To determine which text on the screen should be considered a label for any given control. In order for the label text and accessible name to be matched, it is first necessary Speech output that does not match the visible label. It also creates extra cognitive load for a text-to-speech user to absorb and understand To say a speech command that is different from the visible label they see on a control. Mismatches create an extra cognitive load for speech-input users, who must remember Of an issue for speech-input and text-to-speech users who also have cognitive challenges. Mismatches between visible labels and programmatic names for controls are even more InĪddition, when the accessible name is different from the visible label, it may functionĪs a hidden command that can be accidentally activated by speech-input users. Is not part of) the accessible name that is enabled as a speech-input command. Navigation fails because the visible label spoken by the users does not match (or Of navigation or selection (e.g., "move to Password") will be unsuccessful. When theyĭon't match, speech-input users who attempt to use the visible text label as a means Where text labels exist and are properly linked to the user interface components throughĮstablished authoring practices, the label and name will normally match. Note that where a visible text label does not exist for a component, this SuccessĬriterion does not apply to that component. Screen readers) will also have a better experience if the text they hear matches the Sighted users who use text-to-speech (e.g., Navigate by speaking the visible text labels of components, such as menus, links,Īnd buttons, that appear on the screen. These match, speech-input users (i.e., users of speech recognition applications) can Visible label of a control match or are contained within the accessible name. Users typically have a much better experience if the words and characters in the Those same controls have a programmatic name, also known as the Accessible Name.
Most controls are accompanied by a visible text label. Helps ensure that people with disabilities can rely on visible labels as a means to The intent of this Success Criterion is to ensure that the words which visually labelĪ component are also the words associated with the component programmatically. Success Criterion 2.5.3 Label in Name (Level A): For user interface components with labels that include text or images of text, the name contains the text that is presented visually.Ī best practice is to have the text of the label at the start of the name. Understanding Success Criterion 2.5.3: Label in Name