WCAG 4.1.2: Name Role Value
Success Criterion 4.1.2 — Level A
Quick Answer
All UI components must have accessible names, roles, and states that can be programmatically determined.
Why It Matters
Custom widgets without ARIA roles and names are completely invisible to screen readers.
How to Audit
Run an automated accessibility scan to detect common Name Role Value failures. Then manually verify with: keyboard-only navigation, a screen reader (VoiceOver on Mac, NVDA on Windows), and browser developer tools. Automated tools catch approximately 40% of Name Role Value issues — manual testing is essential.
How to Fix
Use semantic HTML elements. Add aria-label, aria-role, and aria-expanded as needed for custom components.
Frequently Asked Questions
What is WCAG 4.1.2 Name Role Value?
All UI components must have accessible names, roles, and states that can be programmatically determined.
Is WCAG 4.1.2 required for ADA compliance?
WCAG 2.1 Level A is the minimum baseline for ADA website compliance. Courts have upheld WCAG 2.1 AA as the standard for ADA Title III lawsuits.
How do I fix WCAG 4.1.2 violations?
Use semantic HTML elements. Add aria-label, aria-role, and aria-expanded as needed for custom components.
Scan Your Site for WCAG 4.1.2 Issues
Get a free automated accessibility report including all WCAG 2.1 AA violations.
Run Free Accessibility Scan