WCAG Guideline 4.1.2: Name, Role, Value Explained

Estimated read time: 6–7 minutes

Guideline 4: Robust

The Robust principle ensures that web content is compatible with current and future user agents, including assistive technologies.

Guideline 4.1: Compatible

Guideline 4.1 focuses on making sure content can be reliably interpreted by a wide range of technologies.

What Is Guideline 4.1.2 Name, Role, Value?

"For all user interface components, 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 is available to user agents."

Guideline 4.1.2 requires that all interactive elements are accessible to assistive technologies by exposing their name, role, and value.

Ensures UI components are usable with screen readers and other assistive tech
Essential for accessible forms, buttons, and custom widgets
Applies to all interactive elements, including those generated by scripts

For more, see AFB: The Most Frequent Accessibility Issue .

Why Does It Matter?

Inclusivity: Name, role, and value help assistive technologies interpret UI components.
Legal Compliance: Name, Role, Value is a Level A requirement in WCAG 2.1 and 2.2.
Usability: Prevents errors and improves accessibility for all users.

For more, see W3C’s guidance on Name, Role, Value .

What Needs Name, Role, Value?

Buttons and forms
Widgets and custom controls
Any interactive component

How to Ensure Name, Role, Value Accessibility

Use ARIA attributes correctly
Document ARIA usage
Test with screen readers and assistive technologies

For more, see the W3C's Name, Role, Value Techniques .

Common Mistakes to Avoid

Missing or incorrect ARIA attributes
Not documenting ARIA usage
Not testing with screen readers or assistive technologies

Differences Between A, AA, and AAA for Guideline 4.1.2 in WCAG 2.2

Level A: Requires name, role, and value can be programmatically determined. This is the core requirement for 4.1.2 and is mandatory for basic accessibility.
Level AA: For Guideline 4.1.2, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AA.
Level AAA: For Guideline 4.1.2, there are no additional requirements beyond Level A in WCAG 2.2. Meeting Level A for this guideline also satisfies Level AAA.

For more, see the W3C’s official documentation for 4.1.2 Name, Role, Value .

Quick Checklist

All UI components have name, role, and value
ARIA usage is documented
Tested with screen readers and assistive technologies

Guideline 4.1.2 is essential for helping users interact with your site. By ensuring name, role, and value are programmatically determined, you support users with disabilities, improve usability, and meet legal requirements. Test your site regularly and make ARIA accessibility a core part of your development process.

Accessibility means clarity—help assistive technologies interpret your UI!

AccessiTech LLC