Skip to main content
Understandable WCAG 3.2.4

3.2.4 Consistent Identification

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

Level AA Moderate WCAG 2.0 (new) WCAG 2.1 WCAG 2.2

What this rule means

WCAG 3.2.4 requires that components with the same function use the same labels, icons, and text across a website. A search function should always be labeled "Search" — not "Search" on one page and "Find" on another.

This extends to icons, button labels, link text, and any other identifying mechanism. Consistency in labeling helps users recognize and operate components reliably.

Why it matters

Users with cognitive disabilities rely on consistent labeling to understand functionality. If a print icon means "Print" on one page and "Download PDF" on another, it creates confusion.

Screen reader users navigate by element labels. Inconsistent labels force them to re-identify components on each page, significantly slowing interaction.

Related axe-core rules

There are no automated axe-core rules for this criterion. Cross-page label consistency requires manual review.

How to test

  • Identify components that appear on multiple pages (search, login, share, print, etc.).
  • Verify that each component uses the same label, icon, and accessible name across all pages.
  • Check that icons paired with text are used consistently.
  • Review screen reader output for consistent naming.

How to fix

  • Create a design system or component library that enforces consistent naming.
  • Document standard labels for common actions in your style guide.
  • Use the same alt text for icons that serve the same purpose across pages.
<!-- Consistent search across all pages -->
<!-- Page 1 -->
<label for="search">Search</label>
<input type="search" id="search" name="q" />
<button type="submit">Search</button>

<!-- Page 2 — same labeling -->
<label for="search">Search</label>
<input type="search" id="search" name="q" />
<button type="submit">Search</button>

<!-- WRONG: Different label on page 2 -->
<label for="find">Find content</label>
<input type="search" id="find" name="q" />
<button type="submit">Go</button>

Common mistakes

  • Using "Log in" on some pages and "Sign in" on others for the same function.
  • Changing button labels between pages (e.g., "Submit" vs "Send" vs "Go").
  • Using different icons for the same action across pages.
  • Inconsistent accessible names on components that look identical visually.

Resources