Marcelo Paiva

All criteriaPresent as slides

A woman with a bob, dark glasses and headphones holds a white cane in one hand and a phone in the other, frowning.Meant to show: A blind woman whose screen reader announces every control as just 'button'

Success criterion 4.1.2

Name, Role, Value

For all user interface components, the name, role, and value can be programmatically determined.

  • Level A
  • Principle 4: Robust
  • Guideline 4.1: Compatible

In a user’s words

“'Button1'? 'Button2'? What do these buttons even do? Give 'em proper names!”

Who this helps: Screen reader users, Cognitive Impairments

What each role can do

Product manager
Ensure that all UI elements are labeled in a way that makes their purpose clear.
Designer
Design buttons and other UI components with clear labels and roles.
Developer
Implement ARIA roles and proper tagging for interactive elements.
Tester
Test the website with screen readers and other assistive technologies to ensure all elements are properly labeled.

Once it is fixed

“With these new labels, I feel like I've got the control panel of a spaceship, not a mystery box. Thanks!”

The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 4.1.2 in the W3C quick reference for WCAG 2.2 (opens in a new tab).

Or press the left arrow and the right arrow.

A success criterion

This is one page of a phrase book. It takes one success criterion and tells it from the side of the person it helps.

From top to bottom

  1. At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Settings, where you choose the drawings, light or dark, and movement.
  2. Links back to all the criteria, and to present this one as slides.
  3. A drawing, the criterion’s number and name, what it requires in one sentence, and its level.
  4. In a user’s words: a quote from the person who meets the barrier.
  5. What each role can do: one task each for the product manager, the designer, the developer and the tester.
  6. Once it is fixed: the same person again.
  7. Share this with your team: post to LinkedIn, download the slides as a PDF, or copy a link.
  8. Some criteria then have a t-shirt to order.
  9. Links to the previous and next criterion. The left and right arrow keys go there too.
  10. At the bottom, the footer: a note on how this site is built, links to Illustrations, Pens, Concepts and Accessibility, this Describe this page button, then GitHub, LinkedIn and email.

What you can do here

Learn what this criterion asks, and what your part of the fix is.

Also here

The quotes are written to illustrate the criterion. They are not from real people.