‘Status messages’ requires website to alert users to changes in content that aren’t given focus.

Introduction

Users with visual impairments and low vision can benefit from status messages to inform them of changes, results or processes that aren’t clear from a change of context. Adding clear messages can help these users understand and gain further context about

Status Messages (4.1.3 – Level AA)Read more

‘Redundant Entry’ requires websites to auto-fill or provide information that’s required more than once in the same process.

Introduction

When a user is following a multi-step process, they may need help if information is asked for on more than one step of the process.

Requiring users to remember, re-type or replicate information within a process may be difficult

Redundant Entry (3.3.7 – Level A )Read more

‘Accessible Authentication (Enhanced)’ must avoid authenticating users through memory, transcription or cognitive tests.

Introduction

Although it can be important to authenticate users, those with cognitive impairments may have difficulty with remembering passwords or typing in one-time codes.

Some users will be unable to recall a password or series of gestures to access their accounts and require help or

Accessible Authentication (Enhanced) (3.3.9 – Level AAA)Read more

‘Accessible Authentication’ must avoid authenticating users through memory, transcription or cognitive tests without alternatives.

Introduction

Although it can be important to authenticate users, those with cognitive impairments may have difficulty with remembering passwords or typing in one-time codes.

Some users will be unable to recall a password or series of gestures to access their accounts and require help

Accessible Authentication (Level AA – 3.3.8)Read more

‘Visible Controls’ requires websites to give users a way to identify controls without mouse hover or keyboard focus.

Introduction

Users with cognitive impairments, visual disabilities, mobility or motor issues may have difficulty using components if they are hidden until hovered over by a mouse pointer or focused on through keyboard navigation.

Controls that are hidden or displayed on

Visible Controls (Level AA – 3.2.7)Read more

‘Consistent Help’ requires that help and support options are presented in the same order.

Introduction

Offering help options is great for all users, whether the help is human contact or self-service. Users with disabilities may use help options more than other users and will benefit from consistent presentation of their choices.

A simple way to achieve this is

Consistent Help (Level A – 3.2.6)Read more

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