Level ASince WCAG 2.0
4.1.2 Name, Role, Value
Guideline 4.1: Compatible – Controls expose name, role and state to assistive technology.
What does the rule require?
Every control tells assistive technology what it is called (name), what it is (role) and what state it is in (value) – for example “Menu, button, expanded”.
How to get it right
Reach for native HTML first: <button>, <input type="checkbox">. For custom components add ARIA correctly, such as aria-expanded="true".
Who benefits most?
- Blind people
- People who use voice control
- People with motor disabilities
Official wording
This page explains the rule in simple words. Only the original W3C text is normative.
- “Understanding Name, Role, Value” at W3C (external site)
- Techniques in the WCAG Quick Reference (external site)