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

New bullet for 2.2.1 to account for session timeouts

From: Gregg Vanderheiden <gv@trace.wisc.edu>
Date: Sat, 21 Jan 2006 11:05:54 -0600
To: <w3c-wai-gl@w3.org>
Message-ID: <003301c61eac$f111ed90$ee8cfea9@NC6000BAK>
A problem was raised where the server would have a session timeout - but
have no way to alter the user.   The point was made that we should have an
exception to it.  

 

We solved that issue by adding "that is a function of the content" in the
lead sentence.  It was pointed out though that just opened up the original
problem of session timeouts - with no solution - just moving it outside the
scope of the requirement. 

 

If there is a technical reason why it is impossible to alert the user and
extend the time - then we still need to make it an exception (because it
isn't possible). 

This problem only really arises I think, if the page itself is not active.
If active the page could be aware that the server was timing out (either
from original downloading of page or by polling the server and getting
information that the page was timing out). 

 

I would like to suggest we 

1) remove "that is a function of the content" in the lead sentence

2) add the following bullet to 2.2.1 to allow it cover the exception but
only where it is really needed. 

 

Bullet to Add.

 

*          the timeout is controlled by the server, the activity requires a
session timeout (for example order processing), and the page does not have
active content capable of querying the server and/or alerting the user of
impending timeout. 

 

 

(all of current 2.2.1 is below for reference.

2.2.1 For each time-out that is a function of the content, at least one of
the following is true: [How
<http://www.w3.org/WAI/GL/WCAG20/WD-UNDERSTANDING-WCAG20-20060117/Overview.h
tml#time-limits-required-behaviors>  to meet 2.2.1] 

*         the user is allowed to deactivate the time-out or; 

*         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;

*         the user is warned before time expires and given at least 20
seconds to extend the time-out with a simple action (for example, "hit any
key") and the user is allowed to extend the timeout at least 10 times or;

*         the time-out is an important part of a real-time event (for
example, an auction), and no alternative to the time-out is possible or;

*         the time-out is part of an activity where timing is essential
<http://www.w3.org/WAI/GL/WCAG20/appendixA.html#activity-timingdef>  (for
example, competitive gaming or time-based testing) and time limits can not
be extended further without invalidating the activity.

 
Received on Saturday, 21 January 2006 17:05:54 GMT

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