Interactive controls are nested inside each other
Automated check nested-interactive, run with axe-core
- WCAG
- 4.1.2 Name, Role, Value (Level A)
- Severity
- Serious: completable, but painful
- Typical effort
- Moderate, 1 to 4 hours
- Category
- Forms and controls
Who this affects
Screen reader and keyboard users.
Why it matters
A button inside a link (or similar) produces unpredictable focus behaviour and ambiguous announcements — the user cannot tell which action they are about to trigger. Card layouts that make the whole card a link are the usual source.
How to fix it
Flatten the markup so controls are siblings rather than nested.
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.
Related checks: Forms and controls
- Custom buttons, links or menu items have no accessible name
- Dialogs have no accessible name
- Custom input widgets have no accessible name
- Custom checkboxes, switches or radio buttons have no accessible name
- Form fields use invalid autocomplete values
- Buttons have no discernible text
- Form field has more than one label
- Form buttons have no accessible name