- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Wed, 14 Sep 2005 22:20:54 -0500
- To: <w3c-wai-gl@w3.org>
- Message-Id: <20050915031856.67AA360C1A9@eq1.spamarrest.com>
>From another group I am working with - we did a variation on our Level 1 timing guideline. It says the same thing as ours but puts the exceptions up front rather than as alternatives for timing adjusting It looks like Unless limits placed on the timing of user responses are essential to maintaining the integrity of the task or activity or are based on real life time constraints (e.g. an auction), users should be able to adjust each content-specified user response time parameter (i.e., timeout) in one or more of the following ways: o the user is allowed to deactivate the time-out or; o the user is allowed to adjust the time-out over a wide range which is at least ten times the length of the default setting or; o the user is warned before time expires, allowed to extend the time-out with a simple action (for example, "hit any key") and given at least 20 seconds to respond Gregg ------------------------ Gregg C Vanderheiden Ph.D. Professor - Depts of Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison < <http://trace.wisc.edu/> http://trace.wisc.edu/> FAX 608/262-8848 For a list of our list discussions http://trace.wisc.edu/lists/ <http://trace.wisc.edu:8080/mailman/listinfo/>
Received on Thursday, 15 September 2005 03:21:10 UTC