Back to WCAG Database
Level AWCAG 2.0
4.1.2 Name, Role, Value
For all user interface components, the name and role can be programmatically determined; states, properties, and values can be set and notification of changes is available to assistive technologies.
Last reviewed: September 9, 2026
Understanding 4.1.2
The intent of this Success Criterion is to ensure that Assistive Technologies (AT) can gather information about, activate(or set) and keep up to date on the status of user interface controls in the content.
How to Meet It
Use native HTML elements (like `<button>`, `<input>`, `<select>`) whenever possible, as they provide Name, Role, and Value inherently. If creating custom widgets, you must use ARIA attributes (like `role="button"`, `aria-expanded="true"`, `aria-valuenow="50"`) to expose this information to the accessibility tree.
Code Examples
INCORRECT
<div class="checkbox" onclick="toggle()">Agree to terms</div> <!-- Screen reader sees generic text, not a checkbox --> CORRECT
<input type="checkbox" id="terms" /><label for="terms">Agree to terms</label> <!-- Native semantic HTML -->Frequently Asked Questions
What is an Accessible Name?
The accessible name is the string of text that a screen reader announces for an element. It can come from the element's inner text, a linked <label>, or ARIA attributes like aria-label or aria-labelledby.
Related Success Criteria
Quick Facts
- Criterion4.1.2
- LevelA
- IntroducedWCAG 2.0
Automate Compliance
AccessiSight automatically scans and identifies 4.1.2 issues in your codebase.
Try Scanner Free