The target size minimum for pointer inputs is at least 24 by 24 CSS pixels.

Introduction

Users with mobility impairments may have difficulty using elements if their target area is small. These users may have trouble with aiming or being able to keep a pointer steady. Larger target areas help these users interact with controls and elements.

How

Target Size (Minimum) (2.5.8 – Level AA)Read more

Functionality that uses dragging movements can be achieved with a single pointer without dragging.

Introduction

Some users with mobility impairments may have difficulty using a dragging action precisely, either by mouse pointer or touch. Others may use an accessibly input mechanism, such as eye control, that makes dragging even more difficult or even impossible. 

These users need an

Dragging Movements (2.5.7 – Level AA)Read more

‘Concurrent Input Mechanisms’ requires no restrictions on modes of input.

Introduction

Users may choose to switch between different methods of input when interacting with a website. For example, for some controls a user might prefer to input by keyboard and for others they might favour a mouse.

Users might also prefer to override the primary input mechanism for

Concurrent Input Mechanisms (2.5.6 – Level AAA)Read more

Motion Actuation requires that functions operated by motion can also be operated through an interface and responding to motion can be disabled.

Introduction

Where gestures such as pointing or movements like a shaking or tilting control a function, some users will need to be able to control these through a more standard interface. Users with mobility impairments

Motion Actuation (2.5.4 – Level A)Read more

“Label in Name’ requires that where a component has a text label, the name of the component also contains the text displayed.

Introduction

Some users rely on the programmatic names of components and controls, rather than text that is visually displayed on them. This is especially useful for users relying on assistive technology such as screen readers

Label in Name (2.5.3 – Level A)Read more

Pointer Cancellation requires that functions don’t complete on the down-click of a pointer.

Introduction

Some users may need extra help using a mouse or prefer to use assistive technology in place of a mouse. It’s important to reduce the chances of an accidental click for these users by ensuring that the down-click of a mouse pointer alone

Pointer Cancellation (2.5.2 – Level A)Read more

‘Pointer gestures’ requires that multi-point and path-based gestures can be operated with a single pointer.

Introduction

Some users cannot easily perform gestures in a reliable or precise way, which can make it difficult for them to interact with websites where gestures are required. To overcome this, users might have assistive technology driven by speech or eye movement

Pointer Gestures (2.5.1 – Level A)Read more

‘Focus Appearance (Enhanced)’ requires that focus indicators are more clearly distinguishable when active.

Introduction

Focus indicators help users see which element on a page currently has focus, they are especially useful for people with low-vision, memory or mobility impairments. 

Where a focus indicator is used to show an element has current focus, it must be clearly visible and

Focus Appearance (Enhanced) (2.4.12 – Level AAA)Read more