Understanding WCAG 2.0

Skip to Content (Press Enter)

This document is a draft, and is designed to show changes from a previous version. It is presently showing added text,changed text,deleted text,[start]/[end] markers,and Issue Numbers.

Hide All Edits   |   Toggle Deletions  |   Toggle Issue Numbers   |   Toggle [start]/[end] Markers   |   Show All Edits

Changes are displayed as follows:


Focus Visible:
Understanding SC 2.4.7

2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)

The intent of this Success Criterion is to ensure that there is at least one mode of operation where the keyboard focus indicator can be visually located.

  • This Success Criterion helps anyone who relies on the keyboard to operate the page, by letting them visually determine the component on which keyboard operations will interact at any point in time.

  • People with attention limitations, short term memory limitations, or limitations in executive processes benefit by being able to discover where the focus is located.

Resources are for information purposes only, no endorsement implied.

Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. The techniques listed only satisfy the Success Criterion if all of the WCAG 2.0 conformance requirements have been met.

Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.

  • Highlighting a link or control when the mouse hovers over it (future link)

  • Providing a highly visible highlighting mechanism for links or controls when they receive keyboard focus (future link)