Skip to content
Pandus

WCAG A/AA requirement Priority: Serious

Keyboard users cannot reach some embedded content

An embedded frame (iframe) contains links, buttons or form fields, but the frame itself is set to tabindex="-1", which takes it out of the keyboard order.

This text was translated automatically and has not been reviewed by a native speaker yet.

Why it matters to your customers

People who navigate with the Tab key skip the whole frame. If it holds a card payment form, a delivery map, a booking calendar or a chat widget, they cannot use it at all and may be unable to finish the order.

Who is affected

  • keyboard-only users
  • people with motor impairments
  • screen reader users

How to fix it

Remove tabindex="-1" from any <iframe> or <frame> that contains interactive content, so keyboard focus can move into it. If the frame is purely decorative or duplicated, hide it properly instead (for example with aria-hidden and no focusable content inside). For third-party embeds, check the embed code or ask the vendor.

On Shopify

Usually from embed code or an app that adds tabindex="-1" to its iframe (video, reviews, chat, payment). Remove it from your own embed code; app iframes must be fixed by the app developer.

On Shoptet (CZ)

Usually from embed codes or widgets added through custom code. Remove tabindex="-1" from your embed code; widget providers may need to fix their own frames.

On PrestaShop

Usually from modules that embed video, maps or payment forms in an iframe. Remove tabindex="-1" in the module or theme .tpl templates; report third-party modules to their developer.

On WooCommerce

Usually from page builders, sliders or plugins (video, maps, payment, chat) that add tabindex="-1" to an iframe. Check the widget or plugin settings and report it to the plugin author.

Standards

Standards
StandardClause
WCAG 2.2 2.1.1 (A) Keyboard
WCAG 2.1 2.1.1 (A) Keyboard
WCAG 2.0 2.1.1 (A) Keyboard
EN 301 549 4.1.1 9.2.1.1
EN 301 549 3.2.1 9.2.1.1
Section 508 2017 E205.4
ДСТУ EN 301 549 2022 9.2.1.1

Automated check: axe-core rule frame-focusable-content. dequeuniversity.com, github.com, www.w3.org

All rules we check