RatedWithAI

RatedWithAI

Accessibility scanner

Free Scan

WCAG 2.1

4.1.2 Name, Role, Value

Level A success criterion

UI components must expose their name, role, and value to assistive technologies.

Why it matters

Custom controls without proper ARIA cannot be understood or operated by screen readers.

Common violations

  • Custom buttons without role or label
  • Sliders missing aria-valuenow
  • Modals without aria-labelledby

Code examples

Bad

<div class="btn">Save</div>

Good

<button type="button">Save</button>

How to fix

Use native HTML controls whenever possible, and add ARIA roles and labels to custom widgets.

Related criteria

2.5.3 Label in Name2.1.1 Keyboard1.1.1 Non-text Content

Related resources

Google accessibility scoreYouTube accessibility scoreSpotify accessibility scoreWordPress accessibility guideShopify accessibility guideSquarespace accessibility guide

Test & fix this criterion

Use these free tools and guides to check and fix 4.1.2 Name, Role, Value violations:

Free accessibility checker — find WCAG violations automaticallyColor contrast checker — test contrast ratiosHow to fix common WCAG failuresTop 10 most common WCAG failures

Scan your site

Check your WCAG coverage in minutes

Start a free scan