Understanding SC 3.2.4 Consistent Identification

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated : WCAG
3.2.4 Consistent Identification
3.2.4 Consistent Identification

3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA)

The guideline requires that functional components (elements) that appear repeatedly in a set of web pages must have the same name/label. This helps Assistive aid users who heavily rely on these functional elements for quick navigation & understanding the purpose of a particular widget.

For example, if the “search button ” is labelled as either “find or go” in a web page while it is being labelled as “search” on all other pages, then it fails this checkpoint. This checkpoint applies to non-text content, icons and images that appear repeatedly & serve as labels too. In these cases, the alternative text for such labels must be consistent.

Besides being useful to assistive aid users, providing consistent visual non-textual labels for the repeated components reduces the cognitive load of users with cognitive disabilities who learn the repetitive functions of such components. For them, relearning every time when introducing new labels or alternative texts would be difficult.

Points to Ponder

  • Icons & images that are used repeatedly and provide the same function must be provided with same alternative text.
  • Elements with same function are named & labelled consistently.
  • Use icons/images that are consistent. For example print, twitter, Facebook etc.
  • Images will have different meaning in different context, so will need different alternative text depending on the context.

Related WCAG Articles

Useful A11Y Resources on Consistent Identification

References

Read Next: Understanding SC 3.3.1 Error Identification
Explore our WCAG Checklist

Share A11Y Love

Avatar for Raghavendra Satish Peri

Raghavendra Satish Peri is a digital Transformation specialist working with small & large enterprises in the areas of digital accessibility & digital marketing. He authors an Accessibility Blog at DigitalA11Y.com & is galvanizing the adoption of accessibility by inspiring the local tech community with meetups and mentorship. He propelled this thought by founding HelloA11y.com, a community of accessibility professionals, developers, and enthusiasts. When away from his computer, Raghava can be found at local cafes & restaurants sampling cuisines, attending local meetups, listening to audio books, or writing on his Personal Blog at raghava.in.

Similar Posts

Understanding SC 1.4.1 Use of Color

Understanding SC 1.4.1 Use of Color

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
0 Comments

1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A) Note: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation…

Understanding SC 2.1.1 Keyboard

Understanding SC 2.1.1 Keyboard

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
0 Comments

2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints. (Level A) Note 1: This exception relates to the underlying function, not the input…

Understanding SC 2.5.2 Pointer Cancellation

Understanding SC 2.5.2 Pointer Cancellation

Avatar for Sathish KumarAuthored By :Sathish Kumar Last Updated On :
0 Comments

Success Criterion 2.5.2 Pointer Cancellation (Level A): For functionality that can be operated using a single pointer, at least one of the following is true: No Down-EventThe down-event of the pointer is not used to execute any part of the function; Abort or UndoCompletion of the function is on the up-event, and a mechanism is available to abort the function before completion or…

Understanding SC 3.2.2 On Input

Understanding SC 3.2.2 On Input

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
4 Comments

3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) This success criterion conveys that change of context should not occur while user is trying to input data. For example, if…

Understanding SC 2.5.1 Pointer Gestures

Understanding SC 2.5.1 Pointer Gestures

Avatar for Sathish KumarAuthored By :Sathish Kumar Last Updated On :
0 Comments

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive…

Understanding SC 3.3.2 Labels or Instructions

Understanding SC 3.3.2 Labels or Instructions

Avatar for Raghavendra Satish PeriAuthored By :Raghavendra Satish Peri Last Updated On :
0 Comments

Success Criterion 3.3.2 Labels or Instructions (Level A): Labels or instructions are provided when content requires user input. The intention of this success criterion is to provide labels or instructions to form fields and controls which require user input. While the criterion asks for labels or instructions, it is important for the designers and content…

2 Comments

  1. Hi Satish , am looking your blogs it’s very good to understand wcag 2.0 , can you please explain about wcag 2.1 as well

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *