Understanding Pointer Target Spacing

Status

This understanding document is part of the draft WCAG 2.2 content. It may change or be removed before the final WCAG 2.2 is published.

Pointer Target Spacing Success Criterion text

Pointer Target Spacing

AA

New

Each target has a unique area of at least 24 by 24 CSS pixels, except if:

This criterion is about how targets are arranged on screen, not how the code is nested.

Are there issues with internationalization when describing inline links?

Are there issues with pop-over content overlapping targets triggering failures?

Intent of Pointer Target Spacing

The intent of this Success Criterion is to ensure targets can easily be activated without accidentally activating an adjacent target. When targets are small, it is difficult for users with hand tremors and those who have difficulty with fine motor movement to activate them accurately. Providing spacing between targets will reduce the likelihood of accidentally activating the wrong control.

The requirement is for targets to have at least 24 px offset between them. The offset between targets is the size plus spacing of a target, measured from the nearest point of each adjacent target to the farthest point of the current target. For example, a target of 20 x 20px would meet the requirement if it had a spacing of 2 px on all sides. If the target is 24 x 24px or larger, no spacing between it and adjacent targets would be required.

There are four exceptions:

  1. If the target is inline within a sentence there doesn’t need to be a minimum target size.
  2. If the size or spacing of targets is determined by the user agent and is not modified by the author.
  3. If one target is entirely enclosed within another target, each target needs to provide a unique target area of at least 24 by 24 CSS pixels.
  4. If the spacing of the targets is essential to the information being conveyed there doesn’t need to be a minimum target size.

The requirement is independent of the zoom factor of the page; when users zoom in the CSS pixel size of elements does not change. This means that authors cannot meet it by claiming that the target will have enough spacing or sufficient size if the user zooms into the page.

The requirement is independent of the zoom factor of the page, when users zoom in the CSS pixel size of elements does not change. This means that authors cannot meet it by claiming that the target will have enough spacing or sufficient size if the user zooms into the page.

The requirement does not apply to the spacing of targets inside unstyled native elements. For example, when a default select element is used, the vertical spacing of option elements inside the selects dropdown list is exempt.

While the Success Criterion primarily helps touch users by ensuring that activation with the 'fat finger' will not accidentally trigger adjacent targets, it is also useful for mouse or pen users. It reduces the chances of erroneous activation due to a tremor or some other input imprecision.

As mobile devices generally have internal heuristics to identify which link is closest, spacing can work as effectively as a larger target size.

A series of icons with measures showing they are each 24 by 24 pixels wide and high.
The dimension of each icon target in a row is 24 by 24 CSS pixels, so the targets pass this Success Criterion without additional spacing.
A row of icons with measures showing they are each 20 by 20 pixels wide and high, with 4 pixel spacing between them.
The dimension of each icon target in a row is 20 by 20 CSS pixels, so a spacing of 4 CSS pixels is required to arrive at 24 CSS pixels for the combined width and spacing of the target. No adjacent targets are present above and below, i.e., there is sufficient vertical spacing for the height of 24 CSS pixels to be sufficient.
A row of buttons which are more that 20px wide and 18px high. There are no targets above or below.
The widths of the button with adjacent neighbors is at least 24 CSS pixels, while the height is only 18 CSS pixels. The target height combined with the vertical spacing above and below exceeds 24 CSS pixels, therefore, the targets pass this Success Criterion.
A dropdown menu - a pass example with menu items 24 px high, and a fail example with menu items only 20 px high.
A dropdown menu is shown. The PASS example has menu items which are 24 px high. In the FAIL example, the menu items are only 20 px high.

Where targets are embedded inside other targets, the inner target either needs a size of at least 44 x 44 CSS pixels or must be placed at the edge or corner to make sure that there is sufficient adjacent spacing in each dimension.

Three examples of a target adjacent to, or nested within another target (see legend below)
Three examples of a person's profile image, which is supposed to be a target leading to another page, and a magnifying glass icon, which is supposed to open a lightbox view of the profile image. In the first example, the magnifying icon is outside the picture with sufficient spacing and passes. In the second example, the icon overlaps with the top-left corner of the image, but passes due to sufficient spacing top and left. In the third example, the icon sits inside the linked image. Since it is surrounded by an active click area, the icon target is not large enough to pass the Success Criterion.

Users with different disabilities have different needs for control sizes. It can be beneficial to provide an option to increase the active target area without increasing the visible target size. Another option is to provide a mechanism to control the density of layout and thereby change target size or spacing, or both. This can be beneficial for a wide range of users. For example, users with visual field loss may prefer a more condensed layout with smaller sized controls while users with other forms of low vision may prefer large controls.

Where user-agents control the size of a target, such as the options in a select drop-down, and the author has not changed the size of target with size or padding adjustments, the target is exempted from this criterion. It would be beneficial for users if the minimum size & spacing requirement is met, but where the user-agent has defined the target it is not the authors responsibility.

Benefits of Pointer Target Spacing

Having targets with sufficient target spacing can help all users who may have difficulty in confidently targeting or operating small controls. Users who benefit include, but are not limited to:

Examples of Pointer Target Spacing

Resources

Techniques for Pointer Target Spacing

Sufficient Techniques for Pointer Target Spacing

  1. Using min-height and min-width to ensure sufficient target spacing

Additional Techniques (Advisory) for Pointer Target Spacing

Failures for Pointer Target Spacing