Robust → Compatible → 4.1.2

Name, Role, Value

Level APartially Automatable

WCAG Requirement

For all UI components, the name and role can be programmatically determined; states, properties, and values can be set by the user and change notifications are available to assistive technologies.

Experience Builder Notes

Critical for EB apps. Custom widgets often lack proper ARIA roles. axe-core catches many instances. Check toolbar buttons, toggles, and expandable panels.

Sufficient Techniques

✓Use semantic HTML elements with implicit roles
✓Add ARIA roles only when HTML semantics are insufficient
✓Ensure state changes (expanded, selected) are communicated

Common Failures in EB Apps

✗Toggle buttons without aria-pressed
✗Expandable panels without aria-expanded
✗Custom controls without proper role
✗State changes not announced to screen readers

Full specification: WCAG 2.1 — 4.1.2 Name, Role, Value

Have questions about 4.1.2?

Ask our AI assistant about this criterion, remediation strategies, or how it applies to your EB app.

Ask About 4.1.2