WCAG 4.1.2: Name, Role, Value
For all user interface components, the name and role must be programmatically determinable; states, properties, and values must be settable.
Check if your website passes WCAG 4.1.2
Common Failures
Custom controls without ARIA roles, toggle buttons without state information, dynamic content changes not announced.
How to Fix
Use native HTML elements where possible. Add ARIA roles, states, and properties to custom components. Ensure dynamic changes are announced to assistive technologies.
How EAAPass Tests WCAG 4.1.2
EAAPass automatically tests WCAG 4.1.2 (Name, Role, Value) using three engines simultaneously:
- axe-core — Checks DOM elements against the 4.1.2 rule set
- Google Lighthouse — Validates accessibility in the context of overall page quality
- Pa11y — HTML_CodeSniffer integration for WCAG-specific testing
- AI Validation — Claude AI reviews ambiguous results to eliminate false positives
Results are mapped to the Robust POUR principle and scored based on severity and frequency.
Industries Most Affected by WCAG 4.1.2
Other WCAG 2.1 AA Criteria
Test WCAG 4.1.2 on your website
Free WCAG 2.1 AA audit covering all 50 success criteria. No signup required.
Run free audit