WebsiteDesignOutsource.com research

Focus Appearance Evidence for Outsourced Design Review

A standards-led review of visible keyboard focus, contrast, obscuration, component states, and test limitations.

September 7, 2026 Focus Appearance Evidence for Outsourced Design Review editorial illustration

**Published: September 7, 2026**

Keyboard focus can technically exist while being too faint, clipped, or covered to guide a person through a page. This WebsiteDesignOutsource.com note reviews WCAG 2.2 and platform guidance relevant to outsourced component acceptance. Sources were reviewed September 7, 2026.

Research question

What evidence supports a reviewable claim that focus remains visible across website components and page states?

Evidence synthesis

WCAG 2.2 includes Focus Visible at Level AA, Focus Not Obscured at Level AA and AAA variants, and Focus Appearance at Level AAA. The criteria address distinct outcomes. W3C understanding documents explain intent and examples, while CSS specifications and browser references describe author styling mechanisms such as `:focus-visible` and outlines.

Component screenshots alone omit traversal order, sticky overlays, scroll changes, validation, and transient states. Browser defaults can be useful, but resets or theme tokens may suppress them. Custom indicators need review against adjacent colors and component shapes.

Practical interpretation

Inference: acceptance should combine systematic keyboard traversal with state and viewport coverage. Teams should document which criterion and conformance level they are evaluating rather than using a vague “focus compliant” label.

Verification approach

Traverse every operable element in a meaningful task order.

Check default, selected, expanded, invalid, disabled, and modal states.

Test sticky headers, cookie layers, drawers, and virtual keyboards.

Inspect indicators in light, dark, image, and high-contrast contexts.

Repeat at zoom and narrow widths without using a pointer.

Record browser, operating system, input, build, and observed exception.

Evidence scope and limitations

This synthesis does not certify WCAG conformance or cover every assistive technology. Focus visibility is only one keyboard concern; operation, order, semantics, target size, and error recovery require separate evidence.