4.1.2 Name, Role, Value – Level A – accessibility @ perpendicular angel design

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.

Understanding Success Criterion 4.1.2: Name, Role, Value

Not all components are represented here yet.

Checklist – System Foundations

Coding Standards

Test	Priority	Automated test?
Do all components that need ARIA roles have them?	High	None

Checklist – Components

Accordions

Test	Priority	Automated test?
Do the accordions identify both their roles and their states?	High	None

Alerts and Messaging

Test	Priority	Automated test?
Do all components that identify state have the proper aria states?	High	None

Breadcrumbs

Test	Priority	Automated test?
Is the breadcrumb wrapped in a <nav> element with an aria-label attribute?	High	None
If the current page is a link, is it marked with aria-current=”page”?	High	None

Dialogs

Test	Priority	Automated test?
Is the dialog associated with the control that opens it?	High	None

Test	Priority	Automated test?
Do the navigational menus include the correct aria-attribributes, tabindex, aria-expanded, and aria-selected	High	None

Tabsets

Test	Priority	Automated test?
Do the tabs identify both their roles and their states?	High	None

Checklist – Special Testing Scenarios

Test	Priority	Automated test?
Can I identify the name of every actionable element?	High	None

4.1.2 Name, Role, Value – Level A