W3C home > Mailing lists > Public > w3c-wai-au@w3.org > July to September 2010

AUWG Action: Proposal to harmonize path exceptions

From: Richards, Jan <jrichards@ocad.ca>
Date: Mon, 20 Sep 2010 14:28:16 -0400
To: AUWG <w3c-wai-au@w3.org>
Message-ID: <F2C77FB59A1A4840A01EF5F59B1826E20A220C02E6@ocadmail.ocad.ca>
Hi all,

Here is an attempt to use as much of the WCAG 2.0 wording as possible. The only addition is the third sentence in Note 1.

Attempt to harmonize wording:
=============================
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 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. *The path exception encompasses other input variables that are continuously sampled from pointing devices, including pressure, speed, and angle.*

Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.


WCAG 2.0 wording:
=================

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 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.

Existing ATAG 2.0 wording:
==========================

A.3.1.1 Keyboard Access (Minimum): All functionality of the authoring tool is operable through a keyboard interface, except where editing web content properties that encode continuous input. (Level A) 

Note 1: This exception relates to the nature of web content, not the usual input technique. For example, setting the path of a freehand curve is exempt, while setting the endpoints of a straight line is not.  

Note 2: This should not be interpreted as discouraging mouse input or other input methods in addition to the keyboard interface.





Cheers,
Jan


-- 
(Mr) Jan Richards, M.Sc.
jrichards@ocad.ca | 416-977-6000 ext. 3957 | fax: 416-977-9844
Inclusive Design Research Centre (IDRC) | http://inclusivedesign.ca/
Faculty of Design | OCAD University
Received on Monday, 20 September 2010 18:28:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:39:59 UTC