Perceivable · Level AAA · Introduced in WCAG 2.1
WCAG 1.3.6: Identify Purpose
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
At Level AAA, the purpose of interface components, icons and regions is programmatically identifiable in markup-based content. This supports adaptations that help people recognize and navigate familiar functions.
A practical example
A support page exposes its main content and navigation as landmarks, uses a real search region, and gives an icon-only print button an identifiable purpose. A customization tool can then work with meaningful components rather than anonymous containers.
How to check it
- List page regions, interface controls and meaningful icons.
- Inspect available semantics and supported purpose annotations for each item.
- Check that the exposed purpose agrees with the visible action and remains meaningful when decorative styling is removed.
What can be missed
Do not invent unsupported ARIA roles to imitate personalization. Use recognized semantics, consult the criterion's techniques, and keep accessible names and input-purpose requirements distinct.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.