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.
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.
Checklist – System Foundations
|Do all components that need ARIA roles have them?||High||None|
Checklist – Components
|Do the accordions identify both their roles and their states?||High||None|
Alerts and Messaging
|Do all components that identify state have the proper aria states?||High||None|
|Is the dialog associated with the control that opens it?||High||None|
|Do the navigational menus include the correct aria-attribributes, tabindex, aria-expanded, and aria-selected||High||None|
|Do the tabs identify both their roles and their states?||High||None|
Checklist – Special Testing Scenarios
|Can I identify the name of every actionable element?||High||None|