Accessibility: WCAG 2.0 A – Interactive Controls Must Not Be Nested

Nested interactive controls are not announced by screen readers.

How to Analyse in the SEO Spider

To populate this filter ‘Accessibility’ must be enabled via ‘Config > Spider > Extraction’ and ‘JavaScript rendering’ mode via ‘Config > Spider > Rendering’.

View URLs with this issue in the ‘Accessibility’ tab and ‘Interactive Controls Must Not Be Nested’ filter.

Use the lower ‘Accessibility Details’ tab to click on the issue on the left-hand side, and see details of the location on the page of the violation on the right-hand side.

Bulk export the pages and details of the accessibility violations via ‘Bulk Export > Accessibility > All Violations’.

What Triggers This Issue

Please view the Deque University website further reading link below for ruleset triggers.

How To Fix

Ensure interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies.