Goal
Identify components consistently across pages.
Success Criterion · WCAG 3.2.4
Consistent Identification
Components that have the same functionality within a set of Web pages are identified consistently.
Level AAWCAG 2.0Understandable3.2 · Predictable
Copy button ready
What to do
Use the same labels/names for components that have the same functionality (e.g., “Search” always means search).
Why it matters
Consistent identification reduces confusion and improves learnability.
Success criterion
What WCAG 3.2.4 requires
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
Components that have the same functionality within a set of Web pages are identified consistently.
Intent
Why WCAG created this requirement
- Consistent names help users learn interfaces.
- Inconsistent labeling increases cognitive load and errors.
- Applies to labels, icons, and accessible names.
Benefits
Who gains when you pass
- Users with cognitive disabilities benefit from predictable language.
- Screen reader and speech users benefit from consistent accessible names.
- All users avoid confusion and misinterpretation.
Why it matters
User impact when this criterion fails
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Users may not recognize that two controls do the same thing when labeled differently.
Voice users may fail to activate controls if names vary unexpectedly.
Overview
If multiple pages use the same type of control (e.g., a search feature), label and identify it consistently. Don’t call it “Find” on one page and “Search” on another if it’s the same function.
- Standardize labels and icons for common actions across the design system.
- Ensure accessible names align with visible labels (see 2.5.3).
- Keep icon meaning consistent and avoid reusing icons for different actions.
Reference: All summaries and highlights originate from Understanding WCAG 3.2.4 and the W3C quick reference.
Fast facts
- Conformance level
- Level AA
- WCAG version introduced
- WCAG 2.0
- Principle
- Understandable
- Guideline
- 3.2 · Predictable
Examples
Make success tangible for teams
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Search
Pass
Search is consistently labeled “Search” across the site.
Fail
Same search feature is labeled “Find” on some pages and “Lookup” on others.
Settings icon
Pass
Gear icon always means “Settings”.
Fail
Gear icon means “Filters” on one page and “Settings” on another.
Evidence to keep
Document conformance decisions
Capture artifacts for VPATs, procurement reviews, and regression testing.
- Document a label/icon glossary for the design system.
- List common components and their standard names (visible and accessible).
Official resources
Deep dives and supporting material
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Capture progress and blockers
- Create a canonical list of labels for common actions (Search, Save, Delete, Settings).
- Update components to use consistent visible labels and accessible names.
- Standardize icons used for common actions.
- Audit across pages to ensure consistency.
Testing ideas
Prove conformance with evidence
- Review repeated components across pages and verify consistent labels/names.
- Use a screen reader to confirm accessible names are consistent across contexts.
- Test voice control activation with consistent labels.
Related success criteria