Provide user interface components that are consistently labelled
no. 142
Make sure call to actions repeated on multiple pages are labelled consistently
Consistency and predictability are some of the most important aspects to factor in when building user interfaces that are intuitive and easy to use. Even to this day, it is not unusual to find various calls to action, such as buttons or links sharing the same functionality (print this page, order this catalog, edit this information, etc.), that are used on multiple pages, but are labelled in ways that are inconsistent from one page to another. This creates potential confusion for users, especially when these users deal with cognitive impairments of any kind, or when assistive technologies such as screen readers are involved. Calls to action that provide the same functionality and are labelled consistently contribute to helping users build confidence into the system, and their own ability to predict how to use this system efficiently.
To do so, simply make sure that user interface components that are repeated across multiple pages are consistently named using the same text labels. Doing so will help users reliably refer to these components as navigation benchmarks when going from one page to another. This is especially important when interface components are reused throughout a sequence of screens, or when users are expected to follow a certain flow. Regardless of disabilities, providing users with components that are consistently labelled when they offer the same functionality will not only provide a more predictable user experience, but will also help everyone better understand how to use the system.
User Story
As a user with or without disability, I want to rely on user interface components that are consistently labelled across pages, so that I can build trust into the system, learn how to efficiently use the site and successfully predict the purpose of each component.
Simple Code Example
Not Applicable
Testing Methodology
Looking at a sequence of pages, check that each component that shares the same function and is repeated across multiple pages is properly identified using an identical label, a name or a text alternative.
Specification Details
WCAG 2.0: Level AA
Principle: Understandable
Guideline: 3.2 Predictable
Success Criterion: 3.2.4 Consistent Identification
Related Technique: G197
Category: General
