Edit comment LC-922 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-723 Next: LC-744

Comment LC-922: Comment Shortname:; Commenter: Giorgio Brajnik <giorgio@dimi.uniud.it> on behalf of University of Udine, Italy; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
you say â€œunless the task requires analog time dep. inputâ€?. But the task is defined by the designer and is supported by the GUI. By definition, if the task requires some mouse based input that is analog time dependent, then the page succeeds 211.

Proposed Change:

I think you should focus on the concept of â€œgoalâ€? rather than task. A goal is a desired state of things that a user wants to achieve, and tasks are the observable actions to achieve the goal. Thus you might want to say that the goal should be achievable through 1 or more tasks that do not require analog time dependent gestures. Except when for that goal there is no other way (like piloting a plane!).; Related issues: 921
(space separated ids); WG Notes: [TEAMA] Discussed in the 13 July 2006 telecon: Accepted by unanimous consent. http://www.w3.org/2006/07/13-wai-wcag-minutes.html {partial accept} DONE change SC by adding "underlying" to read 2.1.1 All functionality of the content is operable in a non-time-dependent manner through a keyboard interface, except where the underlying task requires analog, time-dependent input. DONE in HOW TO MEET add: "When considering whether analog, time-dependent input is required for the underlying task (what you are trying to do) a key question is, could I achieve the same functionality in a different way using an input device that was not analog, time-dependent." Internal WD updated 11 August. Discussed in the 10 May 2007 telecon: Accepted by Unanimous Consent http://www.w3.org/WAI/GL/2007/05/10-wai-wcag-minutes.html; Resolution: We agree with the concept of your comments but chose to address it with different wording as follows. Changed SC by adding "underlying" to read 2.1.1 Keyboard: 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: 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: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. In Understanding 2.1.1, we added: "The phrase "except where the underlying functionality requires path dependent input" is included to separate those things that cannot reasonably be controlled from a keyboard. Most actions carried out by a pointing device can also be done from the keyboard (for example, clicking, selecting, moving, sizing). However, there is a small class of input that is done with a pointing device that cannot be done from the keyboard in any known fashion without requiring an inordinate number of keystrokes. Free hand drawing, watercolor painting, and flying a helicopter through an obstacle course are all examples of functions that require path dependent input. 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.; (Please make sure the resolution is adapted for public consumption)