Skip to content

Target size and target spacing not mentioned in WCAG 3 #808

Description

@julierawe

The “Control Information” subsection of the Interactive Components section is currently missing provisions about target size and target spacing:

  • Target size is very important for helping people with hand tremors, low vision, limited vision, and other challenges hit the target they want to hit and avoid accidentally hitting the wrong thing.
  • Target spacing is very important for helping users avoid hitting another control that is too close to the one they were aiming for.

The current Interactive Components section does have a "Focus indicator size sufficient" provision, but target size and focus size indicator serve different purposes. Target size ensures that interactive elements are easy to click/tap, while the focus indicator helps keyboard users track their location on the page.

Also, please keep in mind this important WCAG 2.2 note about Target size (minimum):
“This success criterion defines a minimum size and, if this can't be met, a minimum spacing. It is still possible to have very small, and difficult to activate, targets and meet the requirements of this Success Criterion, provided that the targets don't have any adjacent targets that are too close. However, using larger target sizes will help many people use targets more easily. As a best practice it is recommended to at least meet the minimum size requirement of the Success Criterion, regardless of spacing. For important links/controls, consider aiming for the stricter 2.5.5 Target Size (Enhanced).”

COGA user need missing or not adequately addressed -- from Making Content Usable for People with Cognitive and Learning Disabilities:

  • I need the controls to be easy to correctly activate. The interface is designed so that I rarely activate controls by accident. (MCU 3.1.2, bullet 3)

With thanks,
The COGA Task Force

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions