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: Fri, 9 Mar 2007 00:40:37 -0600
To: "'Bailey, Bruce'" <Bruce.Bailey@ed.gov>, "'Slatin, John M'" <john_slatin@austin.utexas.edu>
Cc: "'WCAG'" <w3c-wai-gl@w3.org>
Message-ID: <00c601c76215$d9554d70$0f6fa8c0@NC84301>

Hmmm

This got reworded and that has introduced a problem.   I'll find the old
wording.




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



> -----Original Message-----
> From: w3c-wai-gl-request@w3.org
> [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Bailey, Bruce
> Sent: Thursday, March 08, 2007 12:40 PM
> To: Slatin, John M
> Cc: WCAG
> Subject: RE: Not described in words
>
>
> > About putting all the timing issues under 2.2
>
> I am not sure 2.2 needs additional timing related SC.  But
> let me repeat my other concern with the current wording of SC
> 2.1.1 (and 2.1.2):
>
> <q>All functionality of the content is operable in a
> non-time-dependent manner through a keyboard interface</q>
>
> >> seems to exclude *all* keyboard accessible games that have
> timing as
> >> [a] play element
>
> It is possible for games like Pong or Frogger to satisfy SC 2.2.1 if:
> <q>the user is allowed to adjust the time-out over a wide
> range that is at least ten times the length of the default setting</q>
>
> But this does not help with SC 2.1.1 (and 2.1.2) and
> *recreational* games because, even if all functionality is
> operable via a keyboard interface, the functionality is *not*
> operable in a "non-time-dependent manner".
>
>
Received on Friday, 9 March 2007 06:40:51 GMT

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