# Focus Order

Focus order is the sequence in which keyboard navigation reaches interactive elements, preserving meaning and operability as users move through an interface.

- Type: principle
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/focus-order/>)

## What it means

Focus order describes sequential keyboard navigation, usually produced by document order and native focusability. A logical order follows meaningful reading and task progression without requiring it to match every visual arrangement exactly. It is one part of focus management, not a license to force focus through all content.

## Why it matters

Keyboard and screen-reader users rely on predictable sequence to understand context and operate controls. When visual layout, document order, and programmatic focus diverge, users may encounter actions before labels, jump between regions, or lose the task's structure.

## When to use it

Review focus order for every page and component, especially responsive layouts, CSS reordering, dialogs, menus, error summaries, and dynamically inserted content. Prefer meaningful source order and native navigation over positive tabindex values.

## How it works

1. Arrange source content in a meaningful reading and task order before applying visual layout.
2. Use native interactive elements so ordinary Tab and Shift+Tab behavior emerges naturally.
3. Define arrow-key navigation separately for composite widgets such as tabs or radio groups.
4. Move focus programmatically only when a context change would otherwise leave users lost.
5. Test forward and reverse order at responsive breakpoints, high zoom, errors, and dynamic updates.

## A practical example

At a narrow breakpoint, an order summary moves visually above a checkout form. The DOM remains meaningful, form fields follow their headings, the summary is not inserted into every Tab stop, and an error summary moves focus only after unsuccessful submission.

## Where it breaks

A logical sequence can still be inefficient if too many elements are focusable. Screen readers also provide heading, landmark, and browse navigation beyond Tab order, while composite widgets intentionally manage focus using different keys.

## Common mistakes

- Using positive tabindex values to patch an illogical document structure.
- Assuming CSS visual order automatically changes sequential focus.
- Putting noninteractive text into the Tab sequence unnecessarily.
- Testing forward Tab only and missing reverse or responsive failures.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/focus-order/#visualization-focus-order>)

## Sources

1. [Understanding Success Criterion 2.4.3: Focus Order](<https://www.w3.org/WAI/WCAG22/Understanding/focus-order.html>) — W3C Web Accessibility Initiative · Standards guidance
2. [Developing a Keyboard Interface](<https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/>) — W3C Web Accessibility Initiative · Technical guidance

## Related topics

- [Focus Management](<https://wiki.soroush.uk/topic/focus-management/>)
- [Keyboard Accessibility](<https://wiki.soroush.uk/topic/keyboard-accessibility/>)
- [Semantic HTML](<https://wiki.soroush.uk/topic/semantic-html/>)
