Success criterion 4.1.2
Name, Role, Value
For all user interface components, the name, role, and value can be programmatically determined.
- Level A
- Principle 4: Robust
- Guideline 4.1: Compatible
In a user’s words
“'Button1'? 'Button2'? What do these buttons even do? Give 'em proper names!”
What each role can do
- Product manager
- Ensure that all UI elements are labeled in a way that makes their purpose clear.
- Designer
- Design buttons and other UI components with clear labels and roles.
- Developer
- Implement ARIA roles and proper tagging for interactive elements.
- Tester
- Test the website with screen readers and other assistive technologies to ensure all elements are properly labeled.
Once it is fixed
“With these new labels, I feel like I've got the control panel of a spaceship, not a mystery box. Thanks!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 4.1.2 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.