Focus not visible occurs when a keyboard-focusable element receives keyboard
focus but shows no visible indication of that focus state. Sighted keyboard
users — including people who cannot use a mouse due to motor disabilities —
have no way of knowing which element is currently active, making the interface
effectively unusable by keyboard alone.
[1]
Visible focus indicators are essential for:
The single most common cause is a global CSS reset containing:
outline: none or outline: 0
This removes the browser's default focus ring from every focusable element
simultaneously. It is frequently added by developers who find the default
blue ring visually unappealing, without providing any replacement.
Removing the default focus indicator without replacing it is a WCAG failure
and in many jurisdictions a legal compliance issue.
WCAG 2.4.7 (AA) requires that keyboard focus is visible. WCAG 2.2 introduced
an enhanced criterion:
2.4.11 Focus Appearance (AA) requires that the focus indicator:
To test manually:
Automated scanners can detect outline: none in CSS but cannot assess
whether alternative focus styles meet the visual requirement.
Remove any global outline: none rules that are not paired with a replacement
focus style. Provide a consistent, high-contrast focus indicator for all
interactive elements:
Never sacrifice keyboard usability for visual design preferences.
[1]
Last edited Apr 5, 2026, 7:28 PM · P**** J****