Robust

4.1.2 Name, Role, Value

Level AWCAG 2.2Automated checks exist

Every control needs a name and role that assistive technology can read, and its state, such as checked, expanded or selected, must be exposed and kept current.

Who it helps

Screen reader and speech input users.

Failures we see most

  • Custom toggles that never announce on or off
  • Buttons built from divs with no role
  • Menus that do not report whether they are open

How it gets tested

Our scanner runs these 29 axe-core checks for 4.1.2:

Automated checks for 4.1.2
CheckWhat it looks for
area-altActive <area> elements must have alternative text
aria-allowed-attrElements must only use supported ARIA attributes
aria-braille-equivalentaria-braille attributes must have a non-braille equivalent
aria-command-nameARIA commands must have an accessible name
aria-conditional-attrARIA attributes must be used as specified for the element's role
aria-deprecated-roleDeprecated ARIA roles must not be used
aria-hidden-bodyaria-hidden="true" must not be present on the document body
aria-hidden-focusARIA hidden element must not be focusable or contain focusable elements
aria-input-field-nameARIA input fields must have an accessible name
aria-prohibited-attrElements must only use permitted ARIA attributes
aria-required-attrRequired ARIA attributes must be provided
aria-roledescriptionaria-roledescription must be on elements with a semantic role
aria-rolesARIA roles used must conform to valid values
aria-tab-nameARIA tab nodes must have an accessible name
aria-toggle-field-nameARIA toggle fields must have an accessible name
aria-tooltip-nameARIA tooltip nodes must have an accessible name
aria-valid-attrARIA attributes must conform to valid names
aria-valid-attr-valueARIA attributes must conform to valid values
button-nameButtons must have discernible text
duplicate-id-ariaIDs used in ARIA and labels must be unique
frame-titleFrames must have an accessible name
frame-title-uniqueFrames must have a unique title attribute
input-button-nameInput buttons must have discernible text
input-image-altImage buttons must have alternative text
labelForm elements must have labels
link-nameLinks must have discernible text
nested-interactiveInteractive controls must not be nested
select-nameSelect element must have an accessible name
summary-nameSummary elements must have discernible text

Automated checks can find failures of 4.1.2, but they cannot confirm that a page passes. A specialist still reviews it by hand.

How we fix it

Our tools add accessible names to icon-only buttons and unlabeled fields. Roles and states on custom widgets are fixed by a specialist.

Official text: W3C, Understanding 4.1.2 Name, Role, Value. Checks listed from axe-core 4.14.0.

Related criteria

Does your site fail 4.1.2?

Our free scan checks up to 50 of your pages and tells you which criteria fail and where.

Get a free scan