For all user interface components, the name and role can be programmatically determined.
ADA Relevance: Level A is the minimum baseline. Failing this criterion is a clear ADA violation and one of the easiest violations for plaintiff attorneys to identify.
Assistive technology needs to know what each component is (role), what it's called (name), and its current state (value) to present it to users.
Use a screen reader to navigate all interactive elements. Verify each announces its name, role, and state correctly. Check custom widgets have proper ARIA roles and labels.
Use native HTML elements which have built-in roles. For custom components, add appropriate ARIA: role, aria-label, aria-expanded, aria-selected, aria-checked, etc.
Different platforms have different levels of built-in support for WCAG 4.1.2:
WCAG 4.1.2 requires that for all user interface components, the name and role can be programmatically determined. This is a Level A criterion under the Robust principle, meaning it is a minimum baseline requirement.
Use a screen reader to navigate all interactive elements. Verify each announces its name, role, and state correctly. Check custom widgets have proper ARIA roles and labels.
Yes. WCAG 4.1.2 is a Level A criterion, and courts consistently reference WCAG 2.1 AA as the standard for ADA compliance. Failing to meet this criterion creates legal exposure for ADA lawsuits, which typically settle for $10,000 to $75,000+.
Failing WCAG 4.1.2 Name, Role, Value means assistive technology needs to know what each component is (role), what it's called (name), and its current state (value) to present it to users. This violation is detectable by automated scanning tools that ADA plaintiff attorneys use to identify lawsuit targets. ADA CodeFix can scan your site for this specific violation and provide AI-generated code fixes.
ADA CodeFix automatically scans for Name, Role, Value violations and provides AI-generated code fixes — not overlay widgets.
Scan Your Site Free