Category: WCAG Principles and Conformance

Consistent Identification

Also known as: WCAG SC 3.2.4, Success Criterion 3.2.4

Simply put

Consistent Identification means that components which do the same thing across a website are labeled and identified the same way each time they appear. For example, a search button or a print icon that repeats on multiple pages should be named and described consistently. This predictability makes a site easier to learn and use, particularly for people who use screen readers or who benefit from reduced cognitive load.

Formal definition

Consistent Identification is WCAG Success Criterion 3.2.4, a Level AA criterion under the Predictable guideline. It requires that functional components appearing repeatedly within a set of web pages be identified consistently. The criterion applies only to consistency across a set of web pages where a component is repeated on more than one page; it does not mandate that identical labels be used for components with differing functions. Consistent text alternatives, labels, and identifiers for repeated functional components support users who rely on screen readers and reduce cognitive load. Note that meeting this criterion is one part of broader WCAG conformance and does not by itself guarantee an accessible experience or legal compliance; manual and assistive technology testing are generally required. This entry is informational and not legal advice.

Why it matters

Consistency is one of the most direct ways to make a website easier to learn and operate. When a component that performs the same function, such as a search button or a print icon, is labeled and described the same way each time it appears across a set of pages, users can build a reliable mental model of how the site works. This predictability especially benefits people who use screen readers, who navigate by hearing labels and identifiers announced, and users who benefit from reduced cognitive load. When the same function is named differently from page to page, users may be forced to relearn the interface repeatedly or may not recognize that two differently labeled controls actually do the same thing.

Consistent Identification is WCAG Success Criterion 3.2.4, a Level AA criterion under the Predictable guideline, and AA is the level most commonly cited as a conformance target. It is worth emphasizing that the criterion addresses consistency only across a set of web pages where a component is repeated on more than one page; it does not require identical labels for components that perform different functions. Meeting this single criterion is one part of broader WCAG conformance and does not by itself guarantee an accessible experience or legal compliance.

As with other WCAG success criteria, automated testing detects only a portion of relevant issues, and manual and assistive technology testing are generally required to confirm that repeated functional components are genuinely identified in a consistent way. This entry is informational and not legal advice; organizations should consult qualified legal counsel and current agency guidance for questions about their specific obligations.

Who it's relevant to

Screen Reader Users

People who use screen readers navigate by hearing labels, text alternatives, and identifiers announced. Consistent identification of repeated functional components helps these users recognize controls they have encountered before and operate the site more efficiently across pages.

Users Who Benefit from Reduced Cognitive Load

Predictable, consistent labeling reduces the effort required to learn and understand an interface. When the same function is identified the same way each time it appears, users do not have to repeatedly interpret or relearn how components behave.

Designers and UX Practitioners

Designers and content authors are responsible for defining accessible names, labels, and text alternatives for icons and controls. Establishing consistent labeling conventions for repeated components across a set of pages helps satisfy WCAG SC 3.2.4 at Level AA.

Developers and QA Testers

Developers implement the labels and identifiers that assistive technologies expose, and QA testers verify them. Because automated checks detect only a portion of issues, manual review and assistive technology testing are generally needed to confirm that repeated functional components are identified consistently.

Accessibility and Compliance Officers

Those responsible for accessibility programs may track SC 3.2.4 as part of broader WCAG conformance efforts. Meeting this criterion is one component of conformance and does not by itself guarantee an accessible experience or legal compliance; qualified legal counsel should be consulted on specific obligations.

Inside Consistent Identification

WCAG 3.2.4 Consistent Identification

A WCAG success criterion at Level AA, introduced in WCAG 2.0, which requires that components with the same functionality within a set of web pages be identified consistently.

Functional Components

Interactive or informational elements such as buttons, icons, links, form controls, and search fields that perform a particular function; the criterion concerns how these are labeled and identified across a site.

Consistent Labeling

Using the same text alternatives, accessible names, and labels for components that share the same function, so that users can predict and recognize repeated functionality.

Set of Web Pages

The scope over which consistency is evaluated, generally referring to a collection of related pages sharing a common purpose, such as pages within a single website or web application.

Predictability for Users

The underlying goal of helping users, including those who rely on assistive technologies or have cognitive disabilities, encounter familiar functionality identified in a consistent way throughout a site.

Common questions

Answers to the questions practitioners most commonly ask about Consistent Identification.

Does Consistent Identification require that identical components look exactly the same on every page?

No. Consistent Identification, defined as WCAG Success Criterion 3.2.4 at Level AA, addresses the consistent labeling and identification of components that have the same functionality, not their visual appearance. The criterion focuses on functional identity conveyed through text alternatives, accessible names, and labels so that users can recognize recurring functionality. Visual styling may vary as long as the functional identification remains consistent.

Is Consistent Identification the same requirement as Consistent Navigation?

No, these are distinct success criteria, though both fall under WCAG Guideline 3.2 (Predictable) at Level AA. Consistent Navigation (3.2.3) addresses the consistent ordering of navigational mechanisms that repeat across pages. Consistent Identification (3.2.4) addresses the consistent identification of components that have the same functionality. They are related in purpose but are evaluated separately, and meeting one does not satisfy the other.

How should icons that perform the same function be identified consistently?

Components with the same functionality should be given consistent accessible names and text alternatives wherever they appear. For example, an icon used to trigger a search function should be identified consistently across pages so that assistive technology users encounter the same label for the same action. Manual and assistive technology testing are generally needed to confirm that the accessible names are applied consistently, since automated tools detect only a portion of such issues.

Does consistent labeling need to apply across an entire multi-page site or only within a single page?

Consistent Identification applies to components that repeat across a set of web pages, so consistency is generally evaluated across the pages within a given scope rather than within a single page alone. The goal is that a user who learns to identify a component on one page can recognize the same functionality when it recurs elsewhere in that set of pages.

Can text alternatives differ if the underlying function is the same?

Where two components have the same functionality, their identifying text should generally be consistent so users can recognize them as performing the same action. Minor differences may be acceptable when the components do not have identical functionality, but consistency is expected for components that do the same thing. Reviewers commonly document each recurring component and its intended accessible name to support consistent implementation.

How can teams verify Consistent Identification during testing?

Verification typically combines manual review with assistive technology testing, since consistency of accessible names is not fully captured by automated checks. Testers may catalog recurring functional components, review their accessible names and text alternatives across pages, and confirm alignment. As with all WCAG conformance work, meeting this criterion supports usability but does not by itself guarantee an accessible experience for all users or immunity from legal claims; this guidance is not legal advice, and organizations should consult qualified counsel on compliance questions.

Common misconceptions

Consistent Identification requires that identical components look visually identical on every page.

The criterion focuses on consistent identification of functionality, particularly through accessible names and labels, rather than mandating identical visual appearance. Components with the same function should be labeled consistently so users can recognize them.

Meeting Consistent Identification guarantees an accessible and usable experience for all users.

Conformance with this single success criterion does not by itself ensure overall accessibility or legal compliance. It addresses one aspect of predictability, and manual testing, assistive technology testing, and evaluation against other criteria remain necessary.

Automated tools can fully verify Consistent Identification.

Automated testing detects only a portion of accessibility issues and generally cannot reliably judge whether components with the same function are identified consistently. Manual review and human judgment are commonly required to evaluate this criterion.

Best practices

Use consistent accessible names and labels for components that perform the same function across the set of pages, such as using the same label for a repeated search field.

Provide consistent text alternatives for icons or images that serve the same purpose in different locations.

Establish and document naming conventions for common interactive components so that teams apply identification consistently as the site evolves.

Include manual and assistive technology testing to verify that repeated functionality is recognizably identified, since automated tools capture only part of this criterion.

Review templates, design systems, and shared components to ensure consistency is maintained as new pages are added.

Treat this criterion as one part of broader WCAG conformance, and consult qualified legal counsel and current agency guidance for compliance questions, as this guidance is not legal advice.