Re: CFC - Timeouts SC

Hi Denis,

Think of the simple and complex scenarios:


  *   A simple 2 step form: The user is not logged in, there is no AJAX communicating to the server, so if you fill in the first page and leave it 35 minutes until you fill in the second, your data will probably be lost.
Therefore provide a warning at the start to let people know.

NB: I don’t consider a one-step form as a scenario where you could lose data due to “user inactivity”. Closing your window is a user (or user-agent) issue!

  *   An auto-saving spreadsheet: The user is logged in, and the current status is saved every few minutes, or when things are changed.
There are potentially ways that data could be lost due to time-outs, but you wouldn’t want to put in warnings in place as it does try to save the data as you go along.

For testing timeouts (for the current Timing adjustable) we tend to ask the developers at the start of the project if they have any session time outs, and if so what happens. Usually they know the answers to this and a direct test (i.e. waiting) isn’t needed.

Cheers,

-Alastair


From: "Denis Boudreau (Deque)"

I still don't understand the relevancy of the second part of the SC if the condition is technology highly unlikely to be achievable, cannot be efficiently tested for (who has time to wait 24 hours), or even unlikely to be failed due to the warning alternative that's most likely going to be preferred, but since this is a AAA SC, I'll still give it my +1.

/Denis

--
Denis Boudreau,
Principal accessibility consultant & trainer
Deque Systems, Inc.
Cell: +1-514-730-9168
Email: denis.boudreau@deque.com<mailto:denis.boudreau@deque.com>

Keep in touch: @dboudreau<http://www.twitter.com/dboudreau>