Use of pointing-device-specific only event handlers [F54]

Test info

Test for Success Criterion 2.1.1

About

Checked Elements: all

Using only pointing-device-specific event handlers for a function

Short Description

If an element has attributes among: "onclick", "ondblclick", "onmousedown", "onmousemove", "onmouseover", "onmouseout", "onmouseup" <br> then the element should have one of attributes among "onkeypress", "onkeyup", "onkeydown", "onfocus", "onblur". <br> Otherwise the test would fail.

WCAG 2.0

Principle 2: Operable

User interface components and navigation must be operable.
WCAG 2.0: Principle 2

Guideline 2.1: Keyboard

Make all functionality available from a keyboard.
Understanding Guideline 2.1

Success Criterion 2.1.1: Keyboard (Level A)

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)
Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.
Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.
Understanding: Success Criterion 2.1.1

Technique

F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function

Possible Results

Using only pointing-device-specific event handlers for a function: Pointing-device-specific event handlers are the only means to invoke scripting functions