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: Sat, 10 Mar 2007 19:18:26 -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: <000c01c7637b$2c608a00$0f6fa8c0@NC84301>

Well I think we are getting things confused a bit.

2.2 does allow games and other things that have time limits that are
necessary for like competition. Else they can't have time limits and still
be called accessible.

The time 2.1 is not about game time requirements so much as a LIMITATION on
what has to be keyboard accessible.    Competitive games

 -- ------------------------------
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 Sunday, 11 March 2007 01:18:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:02 UTC