Interactive controls must not be nested inside each other

keyboard-accessible/nested-interactive · WCAG 4.1.2 · Level A

Interactive controls must not be nested inside each other.

Nesting interactive elements (like a button inside a link, or a link inside a button) creates unpredictable behavior and confuses assistive technologies. The browser may remove the inner element from the accessibility tree. Restructure the HTML so interactive elements are siblings, not nested. If you need a clickable card, use CSS and JavaScript rather than nesting.

Scan a page or repo for issues like this · All rules

Introduced in @accesslint/core v0.8.0