W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2007

RE: Not described in words

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Wed, 14 Mar 2007 10:37:37 -0500
To: <w3c-wai-gl@w3.org>
Message-ID: <004301c7664e$b321fda0$bb14c74b@NC84301>
Bruce you asked for some examples of 'time dependent key input"

 

One examples might be

 

-          A lesson on ballistics where you hold the key down to move the
cannon up and release it when you have the right angle.  Then you hold a key
down while it builds up charge, firing the cannon when you release the key.


-           

 

others

-          A drawing applet where the per rotates when you  hold a key down
and the draws (in whichever direction it is pointing) when it is released.
Pressing the key down stops it and starts it spinning again. 

-          Holding a key down to adjust something on an on-screen physics
experiment

 

All of these can be done without the time aspect.   It is NOT bad to do the
above.   It is only bad if that is the ONLY way to do those things when the
underlying task does not require timing (as none of these examples do)

 

 

 


Gregg
 -- ------------------------------ 
Gregg C Vanderheiden Ph.D. 

 

 


  _____  


From: w3c-wai-gl-request@w3.org [mailto:w3c-wai-gl-request@w3.org] On Behalf
Of Loretta Guarino Reid
Sent: Wednesday, March 14, 2007 9:27 AM
To: Bailey, Bruce
Cc: Gregg Vanderheiden; w3c-wai-gl@w3.org
Subject: Re: Not described in words

OK, consider autorepeat functionality on a keyboard key, where the amount of
time that the key is held down controls the function (insert one character
vs multiple characters).

Loretta

On 3/14/07, Bailey, Bruce <Bruce.Bailey@ed.gov> wrote: 

> I'm not sure why you think this isn't such an example. A mouse button is
just another key. 

Because unlike 508, WCAG does not have hardware standards, so equivocating
buttons on mouse with buttons on a keyboard is just wrong.  We already know
that a mouse provides "time-dependent analog input" for positioning
movement, so pointing out that the mouse buttons cans can also be used in a
time-dependent fashion I just don't think is all that helpful (sorry).

Here's the current wording for 2.1.1 again:

<q>All functionality of the content is operable through a keyboard interface
without requiring specific timings for individual keystrokes, except where
the underlying task requires time-dependent analog input.</q>

It is quite obvious that the "specific timings for individual keystrokes"
bit applies to the keyboard interface (not "other" keys).  Aside from games,
what are some examples of content that, in violation of 2.1.1, would require
specific timings for individual keystrokes?

If we cannot think of any, why have that clause? 

 




Received on Wednesday, 14 March 2007 15:38:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:49 GMT