Robust · Level A · Introduced in WCAG 2.0
WCAG 4.1.2: Name, Role, Value
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
User-interface components need programmatically determinable names and roles, and their user-settable states, properties and values must be available to software. Assistive technology must be informed when those values change.
A practical example
A custom disclosure visually opens a panel but exposes neither a button role nor its expanded state. Use a native button with a useful name and update aria-expanded in sync with the visible panel.
How to check it
- Inspect the computed role, name and relevant states of each native or custom control.
- Operate the control and watch the accessibility tree for accurate value and state changes.
- Use a screen reader to check that a person can identify the control and understand its current state during the task.
What can be missed
ARIA does not implement keyboard behavior. A control can expose a plausible role while remaining unusable, and a stale expanded or selected value can contradict the actual interface.
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.