SC 3.2.4 Consistent Identification
Ensure components with the same functionality are identified consistently across a set of web pages.
- Purpose: Allows users to build a mental model of site functionality, making interaction predictable and efficient.
- Consistency vs. Identity: “Consistent” does not mean “identical.” Identifiers should accurately describe the specific function of a component in its current context (e.g., “Go to page 4” vs. “Go to page 5”). Conversely, if the same icon serves different functions, it must have distinct labels/text alternatives for each context.
- Scope: This success criterion applies exclusively to Web content; it does not apply to non-Web software, mobile native applications, or non-Web documents (e.g., Office/PDF files).
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently.
This SC supports WCAG Principle 3 – Understandable because it requires consistent identification of functionality, making them easier to use, especially for people with disabilities.
The intent of SC 3.2.4 Consistent Identification is to ensure that elements that serve the same purpose across multiple Web pages of a site are identified and labeled consistently across the site. This includes text alternatives of non-text items. Consistent identification allows users to apply their understanding of how to interact with interface elements on one page to the other pages on a site if the same controls or functionality are repeated there.
Note:
“Consistent” identification does not always mean “identical.” For instance, a website might have an arrow at the bottom of a Web page that links to the next Web page. The text alternative might be “Go to page 4” on one page, but the text alternative for the same arrow at the bottom of the next page might be “Go to page 5”. Although these text alternatives would not be identical, they would be consistent, and therefore would satisfy this SC.
The same non-text-item might be used throughout a website to serve different functions in different contexts. In such cases, different text alternatives are necessary and should be used. For example, an “X” symbol or icon might be used to indicate an error in a form field in one section of a website, whereas it could be used in a different context to provide the user the ability to reject an option. Using “X mark” as a text alternative across all pages on the site would not help users understand the function of the icon in these cases. Different text alternatives should be used when the same non-text content serves multiple functions.
This SC differs from consistent navigation in that it applies to repeated functionality rather than repeated navigational elements.
Impact of Nonconformance with SC 3.2.4 Consistent Identification
| Type of Disability | Description of Impact |
|---|---|
| 302.1 Without Vision | Users who are blind cannot use a mouse to interact with electronic content and typically use an assistive technology, such as a screen reader, to get audible or other alternative output for the information represented visually. To be able to navigate the content, understand its structure and relationships, and understand the meaning of content represented in graphics and images, the content must provide textual and programmatic cues in addition to the content presented purely visually. |
| 302.2 With Limited Vision | Users with limited vision may have widely different visual perception. Individuals with limited vision may or may not use assistive technologies. Therefore, in addition to textual and programmatic cues necessary for assistive technologies, ICT must also present content consistently and predictably. Users who view content with magnifiers may not pick up alerts, warnings, or other content if such content is presented outside of a consistent and predictable navigation pattern or if the content is not itself viewable at large magnification. Content that becomes distorted when magnified can also prevent some users with limited vision from being able to understand or interact with the content. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Some users require more time than average to process information while others may find complicated instructions difficult to follow. Furthermore, some ICT content can distract or overwhelm users, preventing them from being able to interact with or understand other ICT content. Designers and developers of ICT must consider a broad range of cognitive abilities in order to provide ICT that is simple and easy to use. |
Applicability of Success Criteria 3.2.4 Consistent Identification
| Technology | Applicability of SC 3.2.4 Consistent Identification |
|---|---|
| Web | Developers can typically re-use code and code templates for interface components to provide consistent icons, images, equivalent text and/or other identifying characteristics. Otherwise, developers must simply be aware of the functionality their interface components provide and ensure that they consistently identify such functionality wherever it occurs across multiple web pages. |
| Software | Per the Revised Section 508 Standards, SC 3.2.4 Consistent Identification DOES NOT APPLY to non-Web software. |
| Office documents | Per the Revised Section 508 Standards, SC 3.2.4 Consistent Identification DOES NOT APPLY to non-Web software. |
| PDF documents | Per the Revised Section 508 Standards, SC 3.2.4 Consistent Identification DOES NOT APPLY to non-Web software. |
| Mobile Native | Per the Revised Section 508 Standards, SC 3.2.4 Consistent Identification DOES NOT APPLY to non-Web software. |