Level
AA
Since
WCAG 2.0
/ WCAG criterion

3.2.4 Consistent Identification

Components that do the same thing across a site, such as a search button or a download link, must be named and marked the same way each time.

/ What it requires

When a component does the same job on several pages, people should recognise it as the same thing every time. A search button labelled Search on one page and Find on the next, or a print icon drawn differently in two places, makes users wonder whether the two do different things. Screen reader users recognise controls by the name they hear, and people with cognitive disabilities rely on a familiar label or icon instead of working the control out again on every page. Consistent identification lets them carry what they learned on one page to the next.

Same functionality means the same result when used. The criterion covers functional components that repeat within a set of web pages, on different pages, several times on one page, or both. Identification can be a visible label, an accessible name, a text alternative or an icon. It does not have to be identical: W3C accepts wording that adapts to the context while the function stays recognisable, such as a link called Page 4 that reads Previous page when seen from page 5. Components that do different things are outside the criterion even when they look alike, and so is content that is not functional.

/ How pages fail it

  • The search button is labelled Search in the header of most pages and Go on the results page.
  • A download icon has the alt text Download on one page and PDF on another, for the same action.
  • The cart link is a basket icon on product pages and a trolley icon in the checkout.
  • Two buttons that both send the newsletter form have the accessible names Subscribe and Send, because aria-label was written separately in each template.
  • The close button of dialogs is named Close in some of them and Dismiss or a bare x in others, across the same site.

/ How to check it yourself

  1. List the components that repeat across the site: search, sign in, cart, language switcher, print, share, download, close buttons and pagination.
  2. Visit several pages that carry each one and note its visible label, its icon and its alt text.
  3. Read the accessible name of each in the developer tools: the Accessibility pane of the Elements panel in Chrome or Edge, or the Accessibility Inspector in Firefox.
  4. Compare across pages. The same function should show the same label or icon and the same name, or a variation that only reflects the context, such as Next and Previous in pagination.
  5. Listen to the repeated controls with a screen reader such as NVDA to hear the names the way a blind user does.

/ How to fix it

  • Build repeated controls from one component, with the label taken from one string, not retyped in each template.
  • Keep labels, aria-label values and alt texts for shared icons in one copy or translation file, keyed by function.
  • Use one icon set across the site, and one icon for each function.
  • Where an aria-label is needed, make it match the visible label, so that the name people hear and the name they see agree.
  • Agree on a short list of names for common actions, such as Search, Sign in, Cart, Close and Download, and check new templates against it.

/ What our scanner checks

There is no automated check for this criterion in our scan. It computes the accessible name of every control on a page and reports controls with no name under 4.1.2, but it never sets the name of a control on one page against its twin on another, and it cannot tell which components share a function. HTML_CodeSniffer only issues a reminder here, which our pipeline drops. Whether labels stay consistent across the site is reviewed by a person in a manual audit.

/ Who fails it, in our own measurements

The weekly index has no figures for this criterion, because none of the checks the site scan runs can test it. A person judges it, which is what a manual audit is for.

One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.

/ Questions about this criterion

Do repeated buttons need identical labels?

Not always. W3C asks that users can recognise the same function, and accepts labels that adapt to the context, such as Previous page instead of Page 4. Using the same label for the same function is still the safest choice. Different words for the same action, such as Search on one page and Find on another, are the usual failure.

Does 3.2.4 apply to icons and alt text?

Yes. Identification can be a visible label, an accessible name, a text alternative or an icon. A repeated icon that does the same job should look the same and carry the same alt text or accessible name each time it appears. An icon swapped for another one, or a text alternative that changes from page to page, breaks the recognition the criterion protects.

What level is 3.2.4, and does it cover a single page?

Level AA, part of WCAG since 2.0. It applies within a set of web pages, and W3C notes that repeated components can appear on different pages, several times on the same page, or both. Two buttons on one page that close the same kind of dialog and carry different names are within scope.