Success Criteria

WCAG 3.2.4 Consistent Identification

Success Criterion 3.2.4 requires that components serving the same function within a set of pages are identified consistently. It's a Level AA criterion under Guideline 3.2 (Predictable) — closely related to Consistent Navigation, but focused on component identity rather than positional order.

What "identified consistently" means

If a site has a search feature, it should be labeled and iconified the same way everywhere it appears — always a magnifying glass icon labeled "Search," never a magnifying glass on one page and a text link reading "Find" on another for the identical function. The same discipline applies to any repeated functional element: a "download" action, a "share" button, a "print" control — pick one consistent name and icon, and use it everywhere that function appears.

Why inconsistent naming genuinely confuses users

A user who's learned that the magnifying glass icon means "search" on one page has no reliable way to know that a different icon or label elsewhere in the same site means the identical thing, unless they experiment to find out. For screen reader users navigating primarily by name/label rather than visual icon recognition, an inconsistently-named control is effectively a completely different, unfamiliar control every time its label changes — even though it does exactly the same thing.

A concrete example of the failure

A site where the shopping cart icon is labeled "Cart" in the header but "Your Bag" on the checkout page, with no other distinguishing visual cue tying them together — a returning user (or a screen reader user relying on the accessible name to recognize familiar functionality) has no reliable signal that these are the same feature.

Why this, like Consistent Navigation, needs cross-page checking

Verifying this criterion means comparing the same type of control across multiple pages of a site — a single-page audit in isolation can't confirm whether a "Search" button elsewhere on the same site is labeled consistently, since that comparison point doesn't exist on just one page. This is exactly the kind of multi-page consistency check that differentiates a full-site accessibility audit from a single-URL scan.

Practical guidance

Maintain a small, deliberate glossary of names and icons for recurring functional elements as part of a design system — search, cart, download, share, filter, sort — and apply it uniformly across every page and every team building against that design system, rather than letting individual pages or components drift independently over time.

Common questions

What is WCAG 3.2.4?

A Level AA criterion requiring consistent labels and names for functionally identical components across pages — for example, a search button labeled the same way everywhere.

Why does consistent identification matter?

Screen reader users rely on names to recognize controls; inconsistent labels for the same function force them to relearn the interface on each page.

What is an example violation?

A print control labeled 'Print' on one page and 'Print this document' with a different icon on another, when both do the same thing.