Return to list of success criteria
4.1.2 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. (Level A)Understanding Success Criterion 4.1.2
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.
Note: Other techniques may also be sufficient if they meet the success criterion.
ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used (ARIA)
ARIA16: Using aria-labelledby to provide a name for user interface controls (ARIA)
G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes using technology-specific techniques below:
Exposing the names and roles, allowing user-settable properties to be directly set, and providing notification of changes using one of the following techniques:
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 using technology-specific techniques below:
FLASH32: Using auto labeling to associate text labels with form controls (Flash)
FLASH29: Setting the label property for form components (Flash)
FLASH30: Specifying accessible names for image buttons (Flash)
PDF10: Providing labels for interactive form controls in PDF documents (PDF)
PDF12: Providing name, role, value information for form fields in PDF documents (PDF)
SL26: Using LabeledBy to Associate Labels and Targets in Silverlight (Silverlight)
SL32: Using Silverlight Text Elements for Appropriate Accessibility Role (Silverlight)
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 using technology-specific techniques below:
ARIA4: Using a WAI-ARIA role to expose the role of a user interface component (ARIA)
ARIA16: Using aria-labelledby to provide a name for user interface controls (ARIA)
SL6: Defining a UI Automation Peer for a Custom Silverlight Control (Silverlight)
SL18: Providing Text Equivalent for Nontext Silverlight Controls With AutomationProperties.Name (Silverlight)
SL20: Relying on Silverlight AutomationPeer Behavior to Set AutomationProperties.Name (Silverlight)
SL30: Using Silverlight Control Compositing and AutomationProperties.Name (Silverlight)
Providing labels for all form controls that do not have implicit labels (future link)
Note: This failure may be solved in the future using DHTML roadmap techniques.