For user interface components with labels that include text or images of text, the accessible name contains the text that is presented visually. (Level A)

Rationale

Objective: Make the visual label for controls be a trigger for speech activation

This checkpoint primarily benefits users of speech recognition, but it can also benefit low-vision users who use a screen reader. The requirement is to ensure that a component's visible text label is the same as (or included in) the accessible name for the component.

The accessible name is the text that is programmatically associated with the component -- what an assistive technology will use. A screen reader will announce the accessible name when it lands on a button or an input field, so if users still retain the ability to see the screen, it can be confusing if what is announced doesn't match what they see.

More crucially, when users of speech recognition navigate around a page by voice, they can say the accessible name of the component to perform operations. If the visible label is different from the accessible name, two unwelcome things can happen. The first is the user will not be able to say the visible label to interact with the item. The second is that users may accidentally trigger a component by saying its accessible name; if the accessible name's text is not visible, they will have difficulty understanding the issue.

These problems are avoided by ensuring that the visible label is also the programmatic name of the component -- or that the label's text is included in the accessible name, preferrably at the beginning.

Refer to Understanding 2.5.3 for more information (external link to WCAG).

Development Techniques

This paragraph appears generically in all checkpoints. Review the General techniques as well as other tabs applicable to your technology.  Prioritize the use of technology-specific techniques, and implement the General techniques as needed. You are always required to find, understand and implement accessible code techniques to meet the checkpoint. The documented techniques and supplements are not exhaustive; they illustrate acceptable ways to achieve the spirit of the checkpoint. If numbered, techniques are in order of preference, with recommended techniques listed first. Where used, IBM information that complements the WCAG techniques is indicated as supplemental.

General techniques

Any item in this section represents a technique or combination of techniques deemed sufficient. Ensure you review WCAG Common Failures to avoid development mistakes.

Web (HTML, ARIA, CSS) techniques

In addition to the General techniques, any item in this section represents a technique deemed sufficient.

Mobile Native (iOS) techniques

There are no specific Mobile Native iOS techniques for this checkpoint. Refer to the General techniques section.

Eclipse techniques

There are no specific Eclipse techniques for this checkpoint. Refer to the General techniques section.

Windows-based (MSAA+IA2) techniques

There are no specific Windows-based (MSAA+IA2) techniques for this checkpoint. Refer to the General techniques section.


Many links in this checklist reside outside ibm.com at the Web Content Accessibility Guidelines (WCAG) 2.1. W3C Recommendation 05 June 2018: http://www.w3.org/TR/WCAG21/

Copyright © 1994-2019 World Wide Web Consortium, ( Massachusetts Institute of Technology, European Research Consortium for Informatics and Mathematics, Keio University, Beihang University). All Rights Reserved.

Copyright © 2019 IBM Corporation