Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Overview

Make it easier for users to operate functionality through various inputs beyond keyboard.

All functionality should be accessible via pointer input devices, for example, via a mouse pointer, a finger interacting with a touch screen, an electronic pencil/stylus, or a laser pointer.

People operating pointer input devices may not be able to carry out timed or complex gestures. Examples are drag-and-drop gestures and on touch screens, swiping gestures, split taps, or long presses.

Often, people use devices that offer several input methods, for example, mouse input, touch input, keyboard input, and speech input.

These should be supported concurrently as users may at any time switch preferred input methods due to situational circumstances, for example, the availability of a flat support for mouse operation, or situational impediments through motion or changes of ambient light.

A common requirement for pointer interaction is the ability of users to position the pointer over the target. With touch input, the pointer (the finger) is larger and less precise than a mouse cursor. For people with motor impairments, a larger target makes it easier to successfully position the pointer and activate the target.

Pointer Gestures

Not everyone can perform complex and multi-touch gestures.

Let users operate touch screens with one finger and reduced gestures.

Provide single-point operation for all functions.

Please see more detailed information on how to comply with this guideline.

Pointer Cancellation

Make it easier for users to prevent accidental or erroneous pointer input.

People with various disabilities can inadvertently initiate touch or mouse events with unwanted results.

Make pointer cancellation predictable and consistent.

Reduce accidental activation of controls by mouse or touch.

Make it easier for anyone to recover from something they didn’t mean to do.

General Requirements

For functionality that can be operated using a single pointer, at least one of the following should apply:

No Down-Event

The down-event of the pointer is not used to execute any part of the function;

Abort or Undo

Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;

Up Reversal

The up-event reverses any outcome of the preceding down-event;

Essential

Completing the function on the down-event is essential.

Please see more detailed information on how to comply with this guideline.

Make the Control Text Label and Name the Same

Ensure that the words which visually label a component are also the words associated with the component programmatically.

This helps ensure that people with disabilities can rely on visible labels as a means to interact with the components.

People who operate with voice interaction use the visible labels in their commands.

Please see more detailed information on how to comply with this guideline.

Content Should Not Be Dependent On a User's Ability to Move a Device.

Content should not be dependent on a user's ability to move a device.

Some people cannot hold or move a device steadily.

Ensure that functions triggered by moving a device (for example, shaking or tilting) or by gesturing towards the device can also be operated by more conventional user interface components.

Please see more detailed information on how to comply with this guideline.

WCAG Related References

2.5.1 Pointer Gestures (Level A)

2.5.2 Pointer Cancellation (Level A)

2.5.3 Label in Name (Level A)

2.5.4 Motion Actuation (Level A)

  • No labels