Identify Purpose
In content implemented using markup languages, the purpose of user interface components, icons, and regions can be programmatically determined.
In plain language
Icons, controls, and regions of a page should be marked in the code with what they actually are — not just a picture that only makes sense visually.
Why it matters
People with cognitive disabilities sometimes benefit from replacing icons with a symbol set they personally understand better, or simplifying a page by hiding non-essential regions. Assistive tools can only do that if the code says what each icon or region actually is.
In practice
Fails this criterion
A page has navigation icons for home, search, and settings, but nothing in the code identifies what each icon represents — just images with no semantic meaning.
Meets this criterion
The same icons and page regions are marked with proper roles and semantic attributes, letting assistive technology identify and potentially substitute or simplify them for the user.
Test it yourself
Check the site's icons and major regions (navigation, main content, search) using browser dev tools. Are they marked with meaningful roles or attributes describing their purpose, or are they just unlabeled images and generic containers?