Keyboard · WCAG 2.0 Level A
Interactive controls must not be nested
Ensure interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies.
What it means
The nested-interactive rule flags elements that fail this check. It maps to WCAG success criterion 4.1.2.
Who it affects
People who use a keyboard, switch device or other non-mouse input.
How to fix it
Do not put a link or button inside another interactive control. Split them into siblings.
<div class="card">
<a href="/post">Read the post</a>
<button type="button">Save</button>
</div>Check it on your site
Run a free scan. If this rule fails, the results list the affected elements. Deque, which maintains axe-core, also documents this rule in detail: Deque University: nested-interactive.
Quick answers
What does the axe rule "nested-interactive" check?
Ensure interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies.
How do I fix "Interactive controls must not be nested"?
Do not put a link or button inside another interactive control. Split them into siblings.
Who is affected by nested-interactive failures?
People who use a keyboard, switch device or other non-mouse input.
Automated accessibility scan. Results are informational and may not identify every accessibility issue. This service is not legal advice, a compliance certification, or a substitute for comprehensive manual accessibility testing.