ATAG 2.0 - A.3.1.1 Keyboard (Minimum) and A.3.1.5 Keyboard (Enhanced)

Hi all,

On today's meeting we resolved to:
(1) We use JR's rewording responding to SN 
(http://lists.w3.org/Archives/Public/w3c-wai-au/2009OctDec/0012.html) ; 
(2) add the line "Drawing straight lines, regular geometric shapes, 
re-sizing windows and dragging objects to a location (when the path to 
that location is not relevant) do not require path dependent input" to 
the intent;
(3) we are going to add A.3.1.X Keyboard (Enhanced) as AAA without the 
exception


Here's (1) and (2)...

In the Guidelines:
===================
A.3.1.1 Keyboard (Minimum): All functionality of the authoring tool is 
operable through a keyboard interface and does not require specific 
timings for individual keystrokes. An exception to keyboard operability 
is allowed where the underlying function requires input that depends on 
the path of the author's movement and not just the endpoints. (Level A)

Note 1: The movement path 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 prohibit or discourage providing mouse input or 
other input methods in addition to keyboard operation.

In "Implementing ATAG 2.0":
===========================

Understanding Success Criterion A.3.1.1 Keyboard (Minimum): All 
functionality of the authoring tool is operable through a keyboard 
interface and does not require specific timings for individual 
keystrokes. An exception to keyboard operability is allowed where the 
underlying function requires input that depends on the path of the 
author's movement and not just the endpoints. (Level A)

Note 1: The movement path 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 prohibit or discourage providing mouse input or 
other input methods in addition to keyboard operation.

* Intent of Success Criterion A.3.1.1:
The intent of this success criterion is to ensure that, wherever 
possible, authoring tools can be operated through a keyboard or keyboard 
interface (so that an alternate keyboard can be used). Examples of 
"specific timings for individual keystrokes" include situations where 
authors would be required to repeat or execute multiple keystrokes 
within a short period of time or where a key must be held down for an 
extended period before the keystroke is registered. The phrase "except 
where the underlying function requires input that depends on the path of 
the author's movement and not just the endpoints" is included to exclude 
those tasks that cannot reasonably be controlled from a keyboard (e.g., 
free hand drawing, watercolor painting). It is important to note that 
tasks such as drawing straight lines, regular geometric shapes, 
re-sizing windows and dragging objects to a location (when the path to 
that location is not relevant) do not require path dependent input and 
must therefore be operable through a keyboard interface.

EXAMPLES AND RELATED RESOURCES ARE UNCHANGED



Here's (3)...

In the Guidelines:
===================
A.3.1.5 Keyboard (Enhanced): All functionality of the authoring tool is 
operable through a keyboard interface and does not require specific 
timings for individual keystrokes. (Level AAA)

Note: This does not prohibit or discourage providing mouse input or 
other input methods in addition to keyboard operation.

In "Implementing ATAG 2.0":
===========================

Understanding Success Criterion A.3.1.5 Keyboard (Enhanced): All 
functionality of the authoring tool is operable through a keyboard 
interface and does not require specific timings for individual 
keystrokes. (Level AAA)

Note: This does not prohibit or discourage providing mouse input or 
other input methods in addition to keyboard operation.

     * See Success Criterion A.3.1.1, without the allowed exception.



Cheers,
Jan

Received on Monday, 19 October 2009 21:21:46 UTC