Frames with interactive content cannot be reached by keyboard
Automated check frame-focusable-content, run with axe-core
- WCAG
- 2.1.1 Keyboard (Level A)
- Severity
- Serious: completable, but painful
- Typical effort
- Quick win, under 1 hour
- Category
- Keyboard
Who this affects
Keyboard-only users.
Why it matters
An iframe with tabindex="-1" that contains buttons or form fields, such as a payment or booking widget, is skipped entirely when tabbing through the page.
How to fix it
Remove tabindex="-1" from iframes that contain focusable content.
Check your own website
The free scan tests 3 pages against WCAG 2.2 A and AA in about 30 seconds. No sign-up.
Related checks: Keyboard
- Duplicate access keys
- Hidden elements can still receive keyboard focus
- Elements with role="text" contain focusable content
- No way to skip repeated navigation
- Focusable elements have no suitable role
- Scrollable areas cannot be reached by keyboard
- Skip links point to nothing
- Positive tabindex values disrupt focus order