Robust / 4.1 Compatible
4.1.2Name, Role, Value
Level AEvery UI component must expose its name, role, and current state or value programmatically to assistive technology -- and any later change to that state or value must also be announced. Standard HTML elements like button and input already satisfy this natively, so the real work is adding the right ARIA attributes to custom widgets built from generic elements like div or span.
Note
A detailed commentary for this success criterion is not yet available. In the meantime, this page lists related patterns, techniques, and links to the normative sources.
Related Techniques
Specific implementation techniques for meeting this success criterion. This site doesn't include the full text, so follow the links to the original W3C documents.
Sufficient Techniques(14)
Show all (14)
- ARIA4: Using a WAI-ARIA role to expose the role of a user interface component(opens in a new tab)waic.jp(opens in a new tab)
- ARIA5: Using WAI-ARIA state and property attributes to expose the state of a user interface component(opens in a new tab)waic.jp(opens in a new tab)
- ARIA14: Using aria-label to provide an accessible name where a visible label cannot be used(opens in a new tab)waic.jp(opens in a new tab)
- ARIA16: Using aria-labelledby to provide a name for user interface controls(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
- G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
- H44: Using label elements to associate text labels with form controls(opens in a new tab)waic.jp(opens in a new tab)
- H64: Using the title attribute of the iframe element(opens in a new tab)waic.jp(opens in a new tab)
- H65: Using the title attribute to identify form controls when the label element cannot be used(opens in a new tab)waic.jp(opens in a new tab)
- H88: Using HTML according to spec(opens in a new tab)waic.jp(opens in a new tab)
- H91: Using HTML form controls and links(opens in a new tab)waic.jp(opens in a new tab)
- PDF10: Providing labels for interactive form controls in PDF documents(opens in a new tab)waic.jp(opens in a new tab)
- PDF12: Providing name, role, value information for form fields in PDF documents(opens in a new tab)waic.jp(opens in a new tab)
Failures(9)
Show all (9)
- 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(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
- F42: Failure of Success Criteria 1.3.1, 2.1.1, 2.1.3, or 4.1.2 when emulating links(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
- F68: Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
- 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(opens in a new tab)waic.jp(opens in a new tab)
Normative References
- Success Criterion 4.1.2 Name, Role, Value — WCAG 2.2(opens in a new tab)The normative requirement text.
- Understanding Name, Role, Value — W3C(opens in a new tab)Official guidance on intent, examples, and techniques.