WCAG 2.0 · Level AA · Operable
2.4.7 Focus Visible
When a component can be operated through a keyboard, there must be a mode of operation where the keyboard focus indicator is visible. This is a Level AA criterion; it asks whether focus can be seen, not whether the focus indicator meets a particular size or contrast threshold.
Manual verification
How to validate 2.4.7 by hand
Check whether keyboard focus is visibly indicated for every keyboard-operable component.
Start with the extension result
Reopen the reported URL and reproduce the same state (for example, after expanding a menu or submitting a form). Use the result’s Highlight action when available, or its affected-element details and CSS selector, to find the reported content. Apply the checks below to that content and its context. If the element or state has changed, rescan and record that difference before deciding whether the finding still applies.
- Use Tab and Shift+Tab to focus every interactive component, including custom widgets and controls inside overlays.
- Observe the focused component against its actual background and nearby content, including sticky headers and scrolling.
- Repeat in themes and selected/error states to find focus styling that disappears or blends in.
Evidence to record
Record the component and state where focus is not visually distinguishable, with a screenshot or exact reproduction steps.
Scope and exceptions
This criterion asks for a visible mode of focus indication. The specific size and contrast of the indicator are covered by the Level AAA 2.4.13 criterion.
Record the review outcome
- Confirmed: the recorded evidence shows the requirement is not met in the tested page state, and no applicable exception explains it.
- Not reproduced: the reported issue is absent in the current state. Record the URL, state, and affected element you checked; this does not prove other pages or states conform.
- Needs more review: evidence is incomplete, the content requires human judgment, or an exception is uncertain. Record what remains to be checked instead of treating it as a pass.
Why it matters
Sighted keyboard users need to see which control will receive the next keystroke. A visible indicator helps them follow movement through menus, links, forms, and other interactive content.
Examples and distinctions
Visible focus outline
A clear outline or other visible style appears on a link or button when it receives keyboard focus.
Removed browser outline
A CSS rule that removes the outline without providing another visible focus style can leave keyboard users unable to tell which component is active.
Different input modes
Test keyboard operation directly. A mouse hover style does not show whether keyboard focus has a visible indicator.