- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Mon, 30 Jan 2006 17:39:55 -0600
- To: <Sofia.Celic@nils.org.au>, <public-wcag-teamc@w3.org>
Interesting. That is a good example. Thanks. Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison -----Original Message----- From: public-wcag-teamc-request@w3.org [mailto:public-wcag-teamc-request@w3.org] On Behalf Of Sofia.Celic@nils.org.au Sent: Monday, January 30, 2006 4:13 PM To: public-wcag-teamc@w3.org Cc: gv@trace.wisc.edu Subject: RE: SC 2.2.1 - User warning for timeout script example Hi Gregg, <quote> Can you elaborate on the usability problem you (or the other person) identified? </quote> I believe the concern is with the particular type of situation described in the example: "A page of stock market quotes uses script to refresh the page every five minutes in order to ensure the latest statistics remain available. 20 seconds before the five minute period expires, a confirm dialog appears asking if the user needs more time before the page refreshes. This allows the user to be aware of the impending refresh and to avoid it if desired." The example is not a situation where the user is expected to fill in a form and then continue, but instead it is a type of page where the user could conceivably remain - watching changes in stock prices - and thus have a confirmation box presented every 5 minutes. Thanks, Sofia
Received on Monday, 30 January 2006 23:40:03 UTC