About

Version: WCAG 2.2 and up
Number: 3.2.7
Level: AA
Applicability:
  • Focusable Elements
Requirement:

Where receiving pointer hover or keyboard focus triggers user interface components to be visible, information needed to identify that user interface components are available is visible, except when:

  • The information needed to identify the user interface components is available through an equivalent component that is visible on the same page or on a different step in a multi-step process without requiring pointer hover or keyboard focus;
  • The component is provided specifically to enhance the experience for keyboard navigation;
  • A mechanism is available to make the information persistently visible;
  • Hiding the information needed to identify the component is essential.
Guidance:
Techniques: Techniques are not yet available for WCAG 2.2 success criteria.

Purpose

The purpose of this success criterion is to ensure that users can easily locate controls.

How to Meet

The use of hidden controls is not common in digital publications because these works are typically read on devices without hover or keyboard interfaces. Controls are typically persistent so that they can work with touch devices.

If authors do create interfaces with hidden controls, however, they need to ensure that users can access persistent versions. This could be by allowing the user to make the hidden controls persistent (e.g., through a toggle) or by providing a persistent version of the control at some stage of interaction (e.g., making the controls persistent once the interface is activated).

Additional Information

The knowledge base does not currently include information on control visibility due to the lack of implementation in publishing formats. Refer to the WCAG guidance documents for additional information.