- From: Greg Lowney <gcl-0039@access-research.org>
- Date: Thu, 03 Dec 2009 10:04:19 -0800
- CC: UAWG list <w3c-wai-ua@w3.org>
Sounds good, except the Intent paragraph didn't really explain the benefit, as in *why* the user needs to be able to do these things, and it took the concrete example to make it clear. You might address this by adding to the Intent paragraph something like: "Although it should not do so, some Web content is designed to work only with certain input devices, such as a mouse, and make functionality available only through event handlers for those devices. Some users..." -------- Original Message -------- Subject: 4.2.2 From: Simon Harper <simon.harper@manchester.ac.uk> To: UAWG list <w3c-wai-ua@w3.org> Date: Thu, 3 Dec 2009 09:37:29 +0000 Kim and I had this action - here is our attempt Intent of Success Criterion 4.2.2: Users interacting with a web browser may be doing so by voice, keyboard, mouse or another input technology or a combination of any of these. No matter how the user is controlling the user agent, he or she must be able to activate any of the event handlers regardless of the interaction technology being used. Examples of Success Criterion 4.2.2: A user who cannot use a mouse needs to activate a flyout menu that normally appears OnMouseOver. The user should be able to navigate to a link and activate it using keyboard shortcuts. Related Resources for Success Criterion 4.2.2: N/A Best Kim and Si.
Received on Thursday, 3 December 2009 18:05:38 UTC