Name, Role, Value

About

Version:	WCAG 2.0 and up
Number:	4.1.2
Level:	A
Applicability:	Custom Controls
Requirement:	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.
Guidance:	Understanding Success Criterion 4.1.2 How to meet Success Criterion 4.1.2
Techniques:	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 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 G10: Creating components using a technology that supports the accessibility notification of changes G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes G135: Using the accessibility API features of a technology to expose names and notification of changes H44: Using label elements to associate text labels with form controls H64: Using the title attribute of the frame and iframe elements H65: Using the title attribute to identify form controls when the label element cannot be used H88: Using HTML according to spec H91: Using HTML form controls and links

Purpose

The purpose of this success criterion is to ensure that assistive technologies can identify and maintain the state of custom controls.

How to Meet

If authors create custom controls, they need to ensure that they use the applicable ARIA roles, states, and properties to maintain the state of the controls as users interact with them.

Rather than create their own controls, authors are advised to use the various types of controls that are defined in HTML. When used as defined, these controls are inherently accessible.

Additional Information

The following knowledge base pages provide more information about how to address this success criterion for publishing content: