# Toolbar

A toolbar groups frequently used controls for the current view or object into a compact, consistently placed command surface.

- Type: artifact
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-10-06
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/toolbar/>)

## What it means

A toolbar is a labeled group of controls such as buttons, menu buttons, toggles, and inputs that act on or navigate within the current view. Toolbars can reduce keyboard tab stops by managing focus within the group. They differ from tab bars, whose primary purpose is switching top-level application sections.

## Why it matters

A deliberate toolbar keeps common commands discoverable and close to their target while giving related controls a shared structure. Overcrowded or inconsistently ordered toolbars increase search time and hide the relative importance of actions.

## When to use it

Use a toolbar when a view has several related, frequently used controls that benefit from stable grouping. Leave isolated actions ungrouped, move infrequent commands to a labeled menu, and avoid a toolbar when its density exceeds the value of immediate access.

## How it works

1. Identify commands that share a target and are used often enough to remain visible.
2. Order and group controls by task sequence, frequency, and consequence.
3. Use clear text or familiar icons with accessible names and visible states.
4. Define overflow behavior and, for an application-style toolbar, arrow-key focus movement.
5. Test resizing, customization, disabled states, keyboard operation, zoom, and long labels.

## A practical example

A document editor groups Undo, Redo, text style, alignment, and an overflow menu in a formatting toolbar. Tab enters the toolbar once, arrow keys move among controls, and less-used paragraph commands remain available from the overflow menu at narrow widths.

## Where it breaks

Toolbars consume persistent space and icon-heavy versions depend on learned conventions. Focus management becomes complex when the group mixes controls with conflicting arrow-key behavior, and responsive overflow can reduce discoverability.

## Common mistakes

- Putting every available command in the toolbar.
- Using ambiguous icons without labels, tooltips, or accessible names.
- Changing control order or availability unpredictably between similar views.
- Applying toolbar semantics without implementing its expected focus model.

## Sources

1. [Toolbar Pattern](<https://www.w3.org/WAI/ARIA/apg/patterns/toolbar/>) — W3C Web Accessibility Initiative · Technical guidance
2. [Toolbars](<https://developer.apple.com/design/human-interface-guidelines/toolbars>) — Apple · Institutional guideline

## Related topics

- [Menu and Menu Button](<https://wiki.soroush.uk/topic/menu-and-menu-button/>)
- [Button and Link](<https://wiki.soroush.uk/topic/button-and-link/>)
- [Keyboard Accessibility](<https://wiki.soroush.uk/topic/keyboard-accessibility/>)
