Keyboard focus order: catch tab traps before launch

What focus order means for WCAG, how to test with the keyboard alone, and how Shipcheck Pro’s overlay shows missing focus styles and unreachable controls.

By Sumit JhaUpdated November 9, 20268 min readFor: Developers and agencies shipping interactive UIs

Short answer

Keyboard users move with Tab and Shift+Tab. Focus must follow a logical order, stay visible, and reach every control that mouse users can use. Test without a mouse, look for missing focus rings and click-only widgets, and use Shipcheck Pro’s focus-order overlay on the live tab to number tab stops and flag gaps.

Pair this with the WCAG 2.2 checklist and the free color contrast checker. Full axe WCAG audits and focus-order overlay are Pro in the Chrome extension.

Why it matters

Not everyone uses a mouse. Keyboard, switch, and many screen-reader workflows move focus with Tab and Shift+Tab. If focus jumps randomly, disappears, or never reaches a control, the page fails real users and WCAG focus criteria — relevant to ADA and EAA work as an audit aid, not a legal certification.

Manual keyboard pass

  1. Click the address bar, then press Tab into the page (or click the first skip link if you have one).
  2. Tab through the whole page. Note the order: header → main → footer should feel logical.
  3. Confirm a visible focus ring on every stop. If you cannot see where you are, it fails Focus Visible.
  4. Activate buttons and links with Enter or Space. Escape should close dialogs without trapping you.
  5. Open menus and modals: focus should move inside, stay until close, then return sensibly.

Common failures

  • outline: none with no :focus-visible replacement.
  • Custom widgets built from divs without roles, tabindex, or keyboard handlers.
  • Positive tabindex values that scramble DOM order.
  • Sticky headers covering the focused control (Focus Not Obscured).
  • Carousels and cookie banners that trap Tab inside forever.

How Shipcheck Pro helps

On the live tab, Shipcheck Pro’s keyboard focus-order overlay numbers tab stops, highlights missing focus styles, and calls out click-only elements. That is faster than guessing which node broke the sequence — especially on localhost and staging, where paste-URL tools cannot reach.

Free Shipcheck still covers titles, share previews, and other SEO basics on any tab. The overlay, full axe WCAG 2.2 audit, and fix prompts for every open issue are Pro.

What to do next

  1. Run the manual Tab pass on your primary templates (home, pricing, checkout, app shell).
  2. Fix contrast for text and UI with the contrast checker.
  3. Install the extension and unlock Pro to overlay focus order, then paste issues into Cursor with a fix prompt — see Shipcheck fix prompts for Cursor.
  4. Document what you tested in an accessibility statement (only claim methods you actually used).

Questions

Is focus order part of WCAG 2.2?

Yes. Related criteria include Focus Order (2.4.3), Focus Visible (2.4.7), and Focus Not Obscured (2.4.11 in 2.2). Keyboard users must be able to reach and see focused controls.

Can free Shipcheck web tools audit focus order?

No. Free web tools read server HTML and cannot walk your live tab order. Shipcheck Pro’s keyboard focus-order overlay runs in the Chrome extension on the rendered page.

What is a “click-only” control?

A div or span with a click handler but no button/link role and no keyboard handler. Mouse users can activate it; Tab users cannot. Prefer real <button> / <a> elements.

Does a visible outline fail modern design?

You can restyle :focus-visible, but do not remove focus styles entirely. Invisible focus fails WCAG and traps keyboard users.

Tools for this guide