Marcelo Paiva

4.1.2 Name, Role, Value, 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.

Success criterion 4.1.2 · Level A

Name, Role, Value

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

Success criterion 4.1.2 · Level A

Name, Role, Value

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

Principle 4: Robust · Guideline 4.1: Compatible

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!”

Next criterion: 4.1.3 Status Messages

A success criterion, as slides

This is a slide show on a projector. One slide fills the screen, and the site’s header and footer are out of the way.

From top to bottom

  1. The slide: there are five, for the cover, the quote, the criterion, the tasks for each role, and a thank-you.
  2. Under the slide: Exit slides, Previous, which slide you are on, Next, and Full screen.
  3. A line on the keys. The left and right arrows change slide, and Home and End go to the first and last.

What you can do here

Present the criterion to a room, a slide at a time.