1.3.6: Identify Purpose

What it means

Icons, regions, and controls that have a clear purpose should expose that purpose programmatically so users can personalise how they are shown. This AAA criterion supports symbol and region identification beyond basic labels.

Think favicons with text alternatives, landmarks, and purpose metadata.

How to fix it

• Use aria-label or visible text to state the purpose of icon-only regions.
• Apply landmark roles (main, nav, search) consistently where they help orientation.
• Where platforms support it, indicate purpose so users can swap icons for text.
• Document custom components so their purpose is exposed to assistive tech.

Quick examples

• Good: The search region is labelled “Site search” and uses role=“search”.
• Bad: An icon toolbar has no names — screen readers announce only “button” five times.
• Good: A weather widget exposes its purpose as “Local forecast” in the accessibility tree.
• Bad: Critical actions are indicated only by custom pictograms with no text or labels.