# WCAG 2.2 – 4.1.2 Name, Role, Value

- Level: A
- Principle: 4 Robust
- Guideline: 4.1 Compatible
- Introduced in: WCAG 2.0

## What the rule requires

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

- Blind people
- People who use voice control
- People with motor disabilities

## Sources

- [This rule on wcag.dehl.net](https://wcag.dehl.net/en/wcag/4-1-2/)
- [Interactive demo](https://wcag.dehl.net/en/demos/#alt-text)
- [Official W3C explanation](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value)
- [Techniques (WCAG Quick Reference)](https://www.w3.org/WAI/WCAG22/quickref/#name-role-value)

_Plain-language explanation. Only the original W3C text is normative._
