liveBook · Manning

Consistent identification

As explained in Architecting Accessibility

Consistent identification is a WCAG success criterion requiring components with the same function to be identified consistently.

Consistent identification means giving components with the same function the same names, order, grouping, and interaction patterns. Predictability reduces cognitive load and helps people using screen magnifiers, screen readers, or memory supports. section 5.1.4

Apply the principle by:

  • Keeping repeated navigation in the same location and order across pages. section 5.1.4
  • Using stable names and interaction patterns so users do not have to relearn controls. section 5.1.4
  • Checking whether zoomed or assistive-technology users can find familiar controls without searching again. section 5.1.4

A predictable header

Keep the navigation menu first, the shopping cart icon next, and the search bar after it throughout the application. Moving or renaming these controls forces users to rediscover the interface. section 5.1.4

How Architecting Accessibility covers it

How deep it goes
Explains consistent names, order, grouping, and interaction patterns with navigation examples, without detailing implementation code.
Examples
Uses a stable menu, shopping-cart icon, and search-bar order, plus screen-magnifier and changing-navigation scenarios.
What it assumes
Assumes familiarity with digital interfaces and explains the accessibility impact through concrete navigation and assistive-technology scenarios.
What you can do after
Apply consistent names, placement, grouping, and interaction patterns across repeated interface components.
How it connects
Connects consistent identification with consistent navigation, cognitive load, screen magnifiers, screen readers, and recognition.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecting Accessibility. The section links point to the parts of the book it draws on.