About

Version: WCAG 2.0+
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:

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: