4.1.2 Name, Role, Value Level A

Browse by Category

Conformance Levels

Description

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.

*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.

[View on W3C.org]

Questions & Answers

Are there multiple ways to build an accessible widget?

I'm trying to build a widget that follows an example in the W3C ARIA Authoring Practices Guide, but I can't quite match it because of the way my site is built. Can my widget still be accessible?

  • aria
  • custom widgets

How should I code elements with similar designs but different roles?

My footer has five buttons and one link, but they all look like buttons. I think users will expect all the elements to be the same type of element (all buttons or all links), and may be confused that they’re different. Which is more important,...

  • aria roles
  • user experience