2.4.7 Focus Visible: Any keyboard-operable user interface has a mode of operation where the keyboard focus indicator is visible.
SC 2.4.7 Focus Visible supports the principle of Operable because everyone needs to be able to know where the focus is located to be able to operate a user interface. It impacts people with limited vision or with limited cognitive abilities and allows them to discern which interactive element has keyboard focus so they know what element they are interacting with. This SC does not impact users who are without vision because they do not rely on “seeing” the focus, but rely on programmatic focusable properties to be aware of where the focus is located.
This SC allows a keyboard focus indicator to be presented in a variety of ways (e.g., insertion of a caret within an active form field, a dotted line appearing around a button, or highlighting the selected drop-down menu option).
Focus Visible and Focus Order are closely related. Once an element has been placed in the focus order, it needs to have visible focus. The next section of this topic will cover SC 2.4.3 Focus Order.
Impact of Nonconformance with SC 2.4.7 Focus Visible
| Type of Disability | Description of Impact |
|---|---|
| 302.2 With Limited Vision | Users with limited vision may have widely different visual perception. Individuals with limited vision may or may not use assistive technologies. Therefore, in addition to textual and programmatic cues necessary for assistive technologies, ICT must also present content consistently and predictably. Users who view content with magnifiers may not pick up alerts, warnings, or other content if such content is presented outside of a consistent and predictable navigation pattern or if the content is not itself viewable at large magnification. Content that becomes distorted when magnified can also prevent some users with limited vision from being able to understand or interact with the content. |
| 302.7 With Limited Manipulation | Some users may not be able to perform actions that require fine motor control (clicking and dragging), path dependent gestures (pattern-based passcodes), or simultaneous actions (Ctrl + Alt + Del). Providing alternative means to perform the same actions, such as entering the size specifications in an input field to resize an object or allowing sequential key entries, can enable users with limited manipulation to interact with the same content. |
| 302.8 With Limited Reach and Strength | Some users may lack sufficient strength to perform actions such as squeezing, grasping, or depressing a hardware control. Some users, including those in wheelchairs or of shorter stature, may not be able to reach controls that are placed too high or too far away from where a user would access the device controls or interface. ICT designers and developers must consider a broad range of statures, strength and dexterity limitations, and the needs of wheelchair users in order to provide interfaces that are operable with limited reach and/or strength. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Some users require more time than average to process information while others may find complicated instructions difficult to follow. Furthermore, some ICT content can distract or overwhelm users, preventing them from being able to interact with or understand other ICT content. Designers and developers of ICT must consider a broad range of cognitive abilities in order to provide ICT that is simple and easy to use. |
Applicability of Success Criteria 2.4.7 Focus Visible
| Technology | Applicability of SC 2.4.7 Focus Visible |
|---|---|
| Web | All modern Web browsers provide a visible indication of focus be default for all focusable elements. Web developers run into problems when they intentionally remove focus outlines or style them in such a way that makes them impossible to detect. Visible focus problems can also occur when focus moves to an item that might be positioned off screen, is hidden from view, or is otherwise visually obscured. Web developers must therefore ensure that focusable, interactive elements are not simply made invisible. |
| Software | All modern Operating Systems and platforms provide a visible indication of focus be default for focusable elements. As with Web content, Software developers can run into problems when they intentionally remove focus outlines or style them in such a way that makes them impossible to detect. Visible focus problems can also occur when focus moves to an item that might be positioned off screen, is hidden from view, or is otherwise visually obscured. Software developers must therefore ensure that focusable, interactive elements are not simply made invisible. |
| Office documents | Most documents do not have interactive elements that can receive focus. In such cases, keyboard users typically use the system caret or text curser to navigate the document. Screen reader and other AT users similarly use the system caret or a “virtual cursor” to navigate a document. When a document does have interactive elements, such as form controls or custom controls and custom code, then the same considerations apply as for Software, as described above. |
| PDF documents | Many PDF documents do not have interactive elements that can receive focus. Keyboard users may use document landmarks, such as headings, to keep track of their position in a document, just as with a physical document. Screen reader and other AT users use the system caret or a “virtual cursor” to navigate a document. When a document does have interactive elements, such as form controls or custom controls and custom code, then the same considerations apply as for Software, as described above. |
| Mobile Native | All modern mobile Operating Systems and platforms provide a visible indication of focus be default for focusable elements. As with Web content, mobile-native software developers can run into problems when they intentionally remove focus outlines or style them in such a way that makes them impossible to detect. Visible focus problems can also occur when focus moves to an item that might be positioned off screen, is hidden from view, or is otherwise visually obscured. Developers must therefore ensure that focusable, interactive elements are not simply made invisible. |