Why Repeated Actions Must Be Identified Consistently

Users learn how a website works through repetition. When the same action appears on multiple pages, users expect to recognise it instantly. If identical actions are labelled differently, users must stop and reinterpret what each control does, increasing effort and confusion.

This problem affects everyone, but it has a much stronger impact on users who rely on screen readers, keyboard navigation, memory-based strategies, or predictable patterns to move through content.

WCAG addresses this through consistent identification of repeated functionality.

Why Level AA Matters

WCAG success criteria are grouped under principles and guidelines, and each criterion has a conformance level:

• Level A – basic accessibility support
• Level AA – expected and commonly required
• Level AAA – advanced support

Level AA is the most widely required level in accessibility laws and policies.
Consistent Identification (3.2.4) is part of Guideline 3.2: Predictable, which ensures users can anticipate how interfaces behave across pages.

WCAG Success Criterion

3.2.4 Consistent Identification (Level AA)

Components that have the same functionality within a set of web pages are identified consistently.

This requirement applies only when the same function is repeated across multiple pages.

What Is an Accessible Name?

The accessible name is the text that assistive technologies use to identify a control.

Screen readers announce the accessible name, not the visual styling.

Accessible names usually come from:

• Visible text content
• aria-label
• aria-labelledby
• alt text (for images used as controls)

If two controls look the same visually but have different accessible names, they are not consistently identified for assistive technology users.

Visible Labels vs Programmatic Labels

A visible label is what sighted users see.
A programmatic label is what assistive technologies announce.

Both must be consistent when the function is the same.

Visual consistency alone is not sufficient.

What “Same Functionality” Means

Two components have the same functionality if they:

• Perform the same action
• Produce the same result
• Serve the same user purpose

Examples of functionality include:

• Submitting a search
• Saving a page or form
• Downloading a document
• Printing content
• Navigating between pages

If two components do the same thing, users should be able to recognise them as the same action.

What “Identified Consistently” Means

Consistent identification does not require identical wording or visuals.

It does require that users can reliably recognise the function.

Consistency applies to:

• Visible labels
• Accessible names
• Text alternatives for icons
• ARIA labels, where used

If assistive technologies announce two controls differently, they are not consistently identified, even if they look identical.

Plain-Language Requirements of SC 3.2.4

If the same action appears on more than one page:

• It must be labelled consistently
• It must be announced consistently to assistive technologies
• Users should not have to infer whether two controls do the same thing

Different actions may have different labels.
Same actions must not.

Scope of This Requirement

Consistency is required within a defined set of related web pages, such as:

• Pages within the same website section
• Pages sharing a common navigation or template

It does not require consistency across unrelated products, applications, or domains.

Concrete Example: Accessible Name Failure

Two buttons look identical and use the same icon.

<!-- Page A -->
<button aria-label="Search">🔍</button>

<!-- Page B -->
<button aria-label="Find">🔍</button>

Visually, these controls appear the same.
Functionally, they do the same thing.

For screen reader users, these are announced differently and are therefore not consistently identified.

Corrected Version

<!-- Page A -->
<button aria-label="Search">🔍</button>

<!-- Page B -->
<button aria-label="Search">🔍</button>

Now the same function is identified consistently at the programmatic level.

Examples of Consistent Identification

Repeated document downloads

A document icon is used across a site to download files.
Each instance uses a label beginning with “Download,” followed by the document name.

Different document titles are acceptable because the function is the same.

Pagination controls

“Previous” and “Next” links appear on every page of a multi-page article.

Page numbers may change, but the function remains recognisable.

Related but distinct actions

A printer icon is used to print receipts in one place and invoices in another.

Labels such as “Print receipt” and “Print invoice” are appropriate because the actions differ.

Common Failure Patterns

• Labelling the same action as “Search” on one page and “Find” on another
• Using different aria-label values for visually identical controls
• Changing button text based on page context when the function is unchanged
• Reusing the same icon for different actions without clear differentiation
• CMS templates that rename actions inconsistently across page types

These failures often affect assistive technology users first, but increase cognitive load for everyone.

Assistive Technology Impact

Screen Reader Users

Users often navigate using lists of buttons or links.
If labels differ, users cannot rely on learned patterns.

Keyboard Users

Consistent identification reduces navigation errors and hesitation.

Users with Cognitive Disabilities

Predictable labels reduce memory and interpretation effort.

Low-Vision Users

Partial visibility makes consistent cues critical for recognition.

ARIA and Naming Caution

ARIA can introduce inconsistencies if used carelessly.

• Do not override visible text with different aria-label values unless necessary
• Ensure icons and text alternatives convey the same meaning
• Remember that assistive technologies expose the accessible name, not the styling

Consistency must exist at the programmatic level.

Relationship to Other Criteria

• 3.2.3 Consistent Navigation — focuses on order and placement
• 3.2.1 On Focus — prevents unexpected context changes on focus
• 3.2.2 On Input — prevents unexpected context changes on value change
• 2.4.6 Headings and Labels — focuses on descriptive clarity

Consistent Identification focuses specifically on recognising repeated functionality.

How to Test

• Identify actions that appear on more than one page
• Compare visible labels and accessible names
• Verify that identical functions are announced consistently
• Test using:
  • Screen reader button or link lists
  • Keyboard navigation
  • Accessibility tree inspection tools

If users must interpret whether two controls do the same thing, the criterion is not met.

Rule Description

User interface components that perform the same function across multiple pages must be identified consistently, including their accessible names.

Wrapping Up

Consistent Identification is about recognition, not visual sameness. When users encounter the same action across a site, they should immediately know what it does, whether they see it, hear it, or navigate by memory. WCAG 3.2.4 enforces this predictability at both the visual and programmatic levels.

As a Level AA requirement, this is not optional, and it is one of the most common and preventable accessibility failures.