4.1.2 Name, Role, Value

Level: A
Guideline: 4.1 Compatible
Principle: 4 Robust

What it is

For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

How to test

Check: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
Use the sufficient techniques below as acceptable methods when applicable.
Confirm none of the common failures apply.

Sufficient techniques (W3C)

ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used
ARIA16: Using aria-labelledby to provide a name for user interface controls
G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes
H91: Using HTML form controls and links
H44: Using label elements to associate text labels with form controls
H64: Using the title attribute of the iframe element
H65: Using the title attribute to identify form controls when the label element cannot be used
H88: Using HTML according to spec
G135: Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes
PDF10: Providing labels for interactive form controls in PDF documents
PDF12: Providing name, role, value information for form fields in PDF documents
G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes
ARIA4: Using a WAI-ARIA role to expose the role of a user interface component
ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component

Common failures (W3C)

F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML without providing a role for the control
F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely
F20: Failure of Success Criterion 1.1.1 and 4.1.2 due to not updating text alternatives when changes to non-text content occur
F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links
F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name
F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available
F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number
F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to not providing an accessible name for an image which is the only content in a link
F111: Failure of Success Criteria 1.3.1, 2.5.3, and 4.1.2 due to a control with visible label text but no accessible name

Notes

Note: This success criterion is primarily for web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.

Resources

WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#name-role-value
Understanding: https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html
Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#name-role-value

Back to 4 Robust index

4.2 KiB Raw Blame History