nested-interactive

Review all interactive controls to confirm no child element receives focus.

Description

Screen readers should not announce interactive controls nested within each other.

Why is it important?

Nested interactive controls, where interactive elements are contained within one another, pose accessibility challenges. Screen readers may not announce the nested elements, resulting in an empty tab stop. This can create difficulties for users with motor impairments who require precise clicking and may trigger unintended actions.

How to fix?

Nested interactive components such as buttons, checkboxes, links, input fields, etc. should be separated from one another and should be styled as single elements.

References

• WCAG 4.1.2: Name, Role, Value
• WCAG 1.3.1: Info and Relationships
• Accessibility Insights: nested-interactive