Keyboard · WCAG 2.1 Level A
Frames with focusable content must not have tabindex=-1
Ensure <frame> and <iframe> elements with focusable content do not have tabindex=-1.
What it means
The frame-focusable-content rule flags elements that fail this check. It maps to WCAG success criterion 2.1.1.
Who it affects
People who use a keyboard, switch device or other non-mouse input.
How to fix it
Make sure everything that can be scrolled or operated can be reached with Tab and used with the keyboard.
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: frame-focusable-content.
Quick answers
What does the axe rule "frame-focusable-content" check?
Ensure <frame> and <iframe> elements with focusable content do not have tabindex=-1.
How do I fix "Frames with focusable content must not have tabindex=-1"?
Make sure everything that can be scrolled or operated can be reached with Tab and used with the keyboard.
Who is affected by frame-focusable-content 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.