Name, Role, Value
Success Criterion 4.1.2 (Level A)
Does your website/application have any non-standard or customized interface components that may not provide name, role, and value appropriately?
Why is this important
User interface controls used according to standard web specifications are accessible to assistive technologies (AT) such as screen readers, screen magnifiers, and speech recognition software. Custom designed controls however, may not function properly making it difficult or even impossible for users of AT to interact with the content.
Whom does it benefit?
As a person with a mobility impairment using keyboard
I want to know which button or other control on the page has keyboard focus
so that I can more accurately complete online forms
As a person with a visual impairment
I want my screen reader to notify me when a box on a survey has been checked
so that I can be sure my selection is recorded correctly before I submit it.
What should you do?
- Whenever possible, use standard HTML controls that include name, role, state, and value information.
- When a developer includes custom controls or programs elements to have a different role or behavior than standard, ensure that the ability to understand and interact with controls using AT is not lost.
How do you do it?
When using standard controls do not deviate from web specifications.
If customizing controls, be sure to use appropriate WAI-ARIA (Web Accessibility Initiative – Accessible Rich Internet Applications) techniques so that necessary information is made available to assistive technology ensuring that
- every control has a name or label
- role of each control e.g. pulldown menu, link, radio button, etc. is identified
- the state of each control is visible and announced by AT
notifications about changes of focus are made to AT, such as
- whether or not the control has focus.
- whether or not a control option is selected
- which option was selected, such as a checkbox, radio button, or if a collapsible list is expanded or collapsed.
Need technical guidance?
Technical guidance is available for implementing this Success Criterion at
Understanding Success Criterion 4.1.2 - Name, Role, Value
Additional Resources to help you:
Success Criterion 4.1.2: Name, Role, Value
Provide name, role, and value information
Using ARIA for Web Applications
4.1.2 – Name, Role, Value (Level A)