- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Fri, 18 Aug 2017 15:38:08 +0100
- To: w3c-wai-gl@w3.org
Also note that this 24 hour window is only 4 hours more than the 20 hour exception from 2.2.1 Timing Adjustable which is already in 2.0...so from a testing point of view it's just a few hours more *grin* P On 18/08/2017 15:06, Denis Boudreau (Deque) wrote: > Thanks Alistair, that makes sense. Y'all have my +1 on this one. :) > > /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> > >> On 2017-08-18 10:02:29 AM, Alastair Campbell <acampbell@nomensa.com> >> wrote: >> >> 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> >> -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Friday, 18 August 2017 14:38:35 UTC