- Success Criterion 4.1.2
- Conformance level A
Nested Interactive Elements Causing a Double Role Announcement
4.1.2 — Name, Role, Value
Scenario
Setting
A survey tool's question builder
What’s wrong
Nested or redundant interactive semantics causing double role announcements (button inside a link, duplicate role attributes on wrapper and child).
Example
Here's a real case from a survey tool's question builder: nested or redundant interactive semantics causing double role announcements (button inside a link, duplicate role attributes on wrapper and child).
Why it matters
Screen-reader and voice-control users who can operate only what the accessibility tree exposes. On a survey tool's question builder, this barrier means they are excluded from part of the experience.
How to test
Inspect nested interactive elements in DevTools (e.g., a button inside a link, or duplicate role attributes): if a screen reader announces two roles for one control, it fails.
How to fix
Un-nest interactive elements and remove duplicate roles so one control announces one role.
Outcome
Corrected, a survey tool's question builder now lets a visitor complete the task without extra help.
Who is affected
Screen-reader and voice-control users who can operate only what the accessibility tree exposes.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Custom Dropdown or Slider With No Accessibility API Support
- Content Changes That Never Update Their Accessible Name
- Scripted Link or Button With No Real Role or Keyboard Support
- Clickable Div Turned Into a Control but Given No ARIA Role
- Form Field With No Programmatic Label at All
- Assistive Technology Never Told Which Element Currently Has Focus