Skip to content

3.2.4

Jump to bottom
Anika Henke edited this page Jun 16, 2022 · 9 revisions

3.2.4 Consistent Identification

WCAG says:

Components that have the same functionality within a set of Web pages are identified consistently.

When this is applicable

Always.

Check recurring components

Browse through each set of web pages to identify recurring components, but only check on the pages that are in scope for your testing.

Check recurring components and features are consistently named among all pages (for both visible and accessible names). Keep in mind:

  • you should only compare components on a like-for-like basis - for example, all show/hide controls within accordions should be consistently named with each other, but they don't need to be consistently named with other show/hide controls

  • if all the visible and non-visible names are consistent across the site but different from each other, then it passes here but fails 2.5.3 Label in Name. For example, all search buttons are visibly labelled "Search" and all have an accessible name of "Find"

  • this is not just about text but also includes visible identifiers like icons and images

  • consistently named does not mean it needs to be the exact same words (or symbols, such as icons) - for example, a right arrow on one page might have an accessible name of "go to page 3" but on the next page it would say "go to page 4"

Best practice

  • Use different icons if the meaning is different - for example, using a check mark icon for different things (approved, completed, included) and labelling it as such would not be a fail, but it would be better usability to use a different icon
  • Make visible and non-visible names the same (to make it pass 2.5.3 Label in Name)

Clone this wiki locally