|
|
|
|
|
Links and User Controls
Guideline
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
Intent
The intent of this regulation is to help users understand the purpose of each link so they can decide whether they want to follow the link and to ensure that Assistive Technologies (AT) can gather information about, activate(or set) and keep up to date on the status of user interface controls in the content. Whenever possible, provide link text that identifies the purpose of the link without needing additional context. Assistive technology has the ability to provide users with a list of links that are on the Web page. Link text that is as meaningful as possible will aid users who want to choose from this list of links. Meaningful link text also helps those who wish to tab from link to link. Meaningful links help users choose which links to follow without requiring complicated strategies to understand the page.
The text of, or associated with, the link is intended to describe the purpose of the link. In cases where the link takes one to a document or a web application, the name of the document or web application would be sufficient to describe the purpose of the link (which is to take you to the document or web application). Note that it is not required to use the name of the document or web application; other things may also describe the purpose of the link. When standard controls from accessible technologies are used, this process is straightforward. If the user interface elements are used according to specification the conditions of this provision will be met.
If custom controls are created, however, or interface elements are programmed (in code or script) to have a different role and/or function than usual, then additional measures need to be taken to ensure that the controls provide important information to assistive technologies and allow themselves to be controlled by assistive technologies.
Finding Applicable Components
- Active the JAWS screen reader.
- View a list of page links by pressing .
- View a list of buttons by pressing .
- Identify all components that visually function as input controls.
Inspecting and Using Components
- For all identified links check that text of the link describes the purpose of the link.
- For all identified buttons check that the name, value, and state are specified.
Section 508/WCAG 2.0 Failure Conditions
- The destination, function, and/or purpose of a link is not contained in the link text, an applicable aria-attribute, or ALT-text attribute (if image link)
- Fails 1194.31(a): Use without vision.
- Fails 1194.31(b): Use with low vision.
- Fails 2.4.9 Link Purpose (Link Only).
- Each link is not uniquely identified.
- Fails 1194.31(a): Use without vision.
- Fails 1194.31(b): Use with low vision.
- Fails 2.4.4 Link Purpose (In Context).
- The destination, function, and/or purpose of a control is not contained in the screen text, an applicable aria-attribute, or ALT-text attribute (if image control).
- Fails 1194.31(a): Use without vision.
- Fails 1194.31(b): Use with low vision.
- Fails 4.1.2 Name, Role, Value.
Reporting Test Results
- Any failure in Section 508 Failure Conditions results in: Fails Baseline Requirement #16.
- All links and controls describe their purpose, destination, or function and all controls then: Passes Baseline Requirement #16.
See Also |