# Focus Appearance

Focus appearance makes the currently keyboard-focused control visually distinguishable across its states and surrounding backgrounds.

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

## What it means

Focus appearance is the visual presentation of keyboard focus, distinct from the order of navigation or programmatic focus movement. WCAG 2.2 separates visible focus at Level AA from the more specific Focus Appearance criterion at Level AAA, which sets minimum area and focused-versus-unfocused contrast conditions with stated exceptions.

## Why it matters

Without a visible indicator, keyboard users cannot reliably tell which control will receive an action. A focus treatment that disappears on a selected button or dark surface can interrupt navigation even when the underlying controls are operable.

## When to use it

Design and test focus appearance for every interactive component and theme. Use native indicators when suitable, and check any replacement in context. Do not assume a subtle hover style is also a sufficient focus indication.

## How it works

1. Define a consistent focus treatment for controls and links.
2. Check it against adjacent surfaces and all relevant component states.
3. Evaluate the criteria required by the chosen conformance target, including AAA area and contrast rules if claimed.
4. Check clipping, overlays, zoom, and high-contrast or forced-colors behavior.
5. Navigate complete tasks by keyboard to verify the indicator remains understandable.

## A practical example

A design system’s single-color outline disappears on a similarly colored purchase button. The team introduces a contrasting two-layer treatment and checks it in both themes. It also removes an overflow rule that clips the outline inside a card.

## Where it breaks

A visible indicator does not fix keyboard traps, incorrect order, or focus hidden behind overlays. Meeting one criterion does not imply overall WCAG conformance. Platform rendering and user styles can change the final appearance.

## Common mistakes

- Removing native outlines without an effective replacement.
- Calling the AAA Focus Appearance criterion a universal AA requirement.
- Checking a component on one background and assuming it works everywhere.

## Sources

1. [Understanding Success Criterion 2.4.13: Focus Appearance](<https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html>) — W3C Web Accessibility Initiative · Standards guidance
2. [Understanding Success Criterion 2.4.7: Focus Visible](<https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html>) — W3C Web Accessibility Initiative · Standards guidance

## Related topics

- [Focus Management](<https://wiki.soroush.uk/topic/focus-management/>)
- [Keyboard Accessibility](<https://wiki.soroush.uk/topic/keyboard-accessibility/>)
- [Color Contrast](<https://wiki.soroush.uk/topic/color-contrast/>)
