Issues

Accessibility: WCAG 2.0 A – Frames With Focusable Content Must Not Use tabindex=-1

back to issues overview

WCAG 2.0 A – Frames With Focusable Content Must Not Use tabindex=-1

<frame> and <iframe>; elements with focusable content must not have tabindex=”-1″.

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 ‘Frames With Focusable Content Must Not Use tabindex=-1’ 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 <frame> and <iframe> elements with focusable content do not have tabindex=-1

Further Reading

Back to top