Level AA · WCAG 2.0
3.2.4 Consistent Identification
Components that do the same thing are identified the same way wherever they appear — the same label, the same icon, the same accessible name.
Manual only No automated check says anything useful.
How it fails in practice
A search button called “Search” in the header and “Go” in the help centre. The same download icon named “PDF” on one page and “Get file” on the next. A screen-reader user cannot tell they are the same control.
How to fix it
Name a repeated function once, in the component, and reuse the component. Where the wording has to differ, keep it consistent in meaning, not just close.
At a glance
- Level
- Level AA — the level EN 301 549 requires, and therefore the level the BFSG and the EAA are measured against.
- Principle
- Understandable
- Guideline
- 3.2 Predictable
- Added in
- WCAG 2.0
- EN 301 549
- 9.3.2.4
- Automated check
- Manual only
How to test it by hand
- List the controls and icons that repeat across the site: search, basket, download, print, share, close.
- For each, compare the visible label and icon on several pages.
- Compare the accessible names too, in the browser’s Accessibility pane: the same function has the same name everywhere.
In code
<!-- Header -->
<button type="submit" aria-label="Search">
<svg viewBox="0 0 24 24" aria-hidden="true"><path d="…"/></svg>
</button>
<!-- Help centre -->
<button type="submit" aria-label="Go">
<svg viewBox="0 0 24 24" aria-hidden="true"><path d="…"/></svg>
</button><!-- Both places render the same component -->
<button type="submit" aria-label="Search">
<svg viewBox="0 0 24 24" aria-hidden="true"><path d="…"/></svg>
</button>Manual only
How far an automated check gets
Nothing automatic decides this. A scanner that reports it as passing is reporting that it did not look. It stays untested until a person tests it and records what they did — which is exactly how we treat it: as untested, not as passed.
Related criteria
Other criteria under the same guideline.
Find out which criteria your site fails
We scan up to 100 pages against WCAG 2.2 AA, send the keyboard agent through the page you name and email you the report — free, once, no strings.