Consistent Identification: Same Function, Same Name
Also called: Consistent labels, Consistent naming, Consistent icons
Definition
Consistent Identification is WCAG success criterion 3.2.4. Components that have the same functionality within a set of web pages must be identified consistently – with the same labels, names and text alternatives.
Consistent Identification is the WCAG rule that a function keeps its name across your website. If the search button says "Search" on the homepage, it should not say "Find" in the shop and show a different icon on the blog. Visitors learn what a control does once and recognize it on every other page.
What it means
WCAG 3.2.4 Consistent Identification is a Level AA criterion of WCAG 2.2. It reads: "Components that have the same functionality within a set of web pages are identified consistently."
"Identified" covers everything people and assistive technology use to recognize a component: the visible label, the icon, the accessible name and the text alternative of an image. The criterion focuses on components that recur across pages – global navigation, search, account controls, cart, footer links.
Consistent does not mean identical. W3C's example: the link "Page 4" on page 3 of a result list becomes "Previous page" on page 5. The function is the same, the label reflects the context – that passes.
| Situation | Passes 3.2.4? |
|---|---|
| The search button is labeled "Search" on every page | Yes |
| The same save icon with the same text alternative everywhere | Yes |
| "Search" on desktop, a magnifying glass named "Search" on mobile | Yes |
| "Search" on some pages, "Find" on others | No (failure F31) |
| Two printer icons with different functions | Not in scope – different functions |
Screen reader users often look for controls by their name, for example through a list of buttons. If the name changes from page to page, they have to explore again. People with cognitive or learning disabilities rely on recognizing familiar labels and icons.
Examples
<!-- Good: header and footer search use the same label -->
<form role="search" action="/search">
<input type="search" name="q" aria-label="Search the site">
<button type="submit">Search</button>
</form>
<!-- Good: an icon button with the same name on every page -->
<button type="button" class="cart" aria-label="Shopping cart">
<svg aria-hidden="true" focusable="false">…</svg>
</button>
<!-- Bad: the same function, another name on the next page -->
<button type="submit">Find</button>Define one label per function in your design system and reuse the component everywhere. Give every icon button the same accessible name wherever it does the same thing. Keep link texts to the same target the same, such as "Contact" in header and footer.
Call the same action "Submit", "Send" and "Go" on different pages. Don't use one icon for "cart" in the header and another in the product page. Don't let a translation plugin or page builder produce different names for the same button.
How to check Consistent Identification
Questions
Do labels have to be exactly the same on every page?
No. W3C says consistent does not mean identical. A label may change to reflect its context, as long as the same function is identified in a consistent way – for example "Page 4" becoming "Previous page".
Does consistent identification apply to icons?
Yes. An icon that performs the same function on several pages should look the same and have the same text alternative. One icon may serve different functions in different places; its text alternative then matches the function it has there.
What is the difference between consistent identification and consistent navigation?
Consistent navigation (3.2.3) is about the order of repeated menus. Consistent identification (3.2.4) is about the names, labels and icons of components with the same function.
Does consistent identification apply to text that is not a control?
The criterion applies to functional components such as buttons, links and form controls. Identifying other content consistently is good practice, but not required by 3.2.4.
Related terms
Consistent Navigation: Same Menus, Same Order
Consistent Navigation is WCAG success criterion 3.2.3. Navigational mechanisms that are repeated on multiple web pages within a set of web pages must occur in the same relative order each time they are repeated, unless a change is initiated by the user.
Read definition: Consistent Navigation: Same Menus, Same OrderAccessible Name: What It Is and How It Is Computed
The accessible name is the text that browsers pass to assistive technology to identify an element – for example the words a screen reader announces for a button, link or form field. WCAG 4.1.2 requires a programmatically determinable name for every user interface component.
Read definition: Accessible Name: What It Is and How It Is ComputedLabel in Name: Visible Text in the Accessible Name
Label in Name is WCAG success criterion 2.5.3 (Level A). For user interface components with labels that include text or images of text, the accessible name contains the text that is presented visually.
Read definition: Label in Name: Visible Text in the Accessible NameIcon Button: How to Give It an Accessible Name
An icon button is a button that shows only a symbol – a magnifier, a cross, three lines – and no visible text. To be accessible it needs an accessible name in code that tells assistive technology what the button does.
Read definition: Icon Button: How to Give It an Accessible Name