Interface Lab
Login
Back to knowledge
Typography Color Accessibility

Visible Focus States

Keyboard and assistive technology users need to know where focus is; focus states must not be reset away.

focuskeyboardaccessibility

Design Principle

Focus state is part of the interaction path, not a browser default flaw.

Principle

Focus state is part of the interaction path, not a browser default flaw.

Design action

Design high-contrast focus-visible states for all interactive elements; focus rings should not be clipped and keyboard order should follow visual order.

Examples

Positive example: Buttons, links, inputs, tabs, menus, and card entries. Counterexample: outline: none has no replacement.

Apply when

Buttons, links, inputs, tabs, menus, and card entries. Pages include complex navigation or admin operations.

Source notes

Source note: Synthesized from W3C WCAG 2.2, Apple Accessibility, IBM Carbon Accessibility, and accessibility practices in major design systems. WCAG 2.2: https://www.w3.org/TR/WCAG22/ WCAG Contrast Minimum: https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html WCAG Non-text Contrast: https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html Apple HIG Accessibility: https://developer.apple.com/design/human-interface-guidelines/accessibility Carbon Accessibility Overview: https://carbondesignsystem.com/guidelines/accessibility/overview/

Agent Directive

Design high-contrast focus-visible states for all interactive elements; focus rings should not be clipped and keyboard order should follow visual order.