Re: timeouts

I read this that if an author notifies a user more than once, the page 
fails. What is the rationale?

Michael Gower
IBM Accessibility
Research

1803 Douglas Street, Victoria, BC  V8T 5C3
gowerm@ca.ibm.com
voice: (250) 220-1146 * cel: (250) 661-0098 *  fax: (250) 220-8034



From:   Andrew Kirkpatrick <akirkpat@adobe.com>
To:     "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>
Date:   2017-12-01 07:36 AM
Subject:        Re: timeouts



For context, at TPAC the language that was nearly agreed to was:
Where data can be lost due to user inactivity, users are warned about the 
estimated length of inactivity that generates the data loss unless the 
data is preserved for a minimum of 20 hours of user inactivity.
 
Lisa is proposing:
Where data can be lost due to user inactivity, users are warned @@once, 
before an activity timer is set,@@ about the estimated length of 
inactivity  that generates the data loss, unless the data is preserved for 
a minimum of 20 hours of user inactivity.
 
So, the main change is the addition of “once, before an activity timer is 
set”. I think that we need to acknowledge that the amount of time before 
the timer is set may be measured in milliseconds, but it is at least ahead 
of time. I’m less sure about the “once” part but can live with it.
 
Thanks,
AWK
 
Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe 
 
akirkpat@adobe.com
http://twitter.com/awkawk

 
From: Mike Elledge <melledge@yahoo.com>
Reply-To: Mike Elledge <melledge@yahoo.com>
Date: Friday, December 1, 2017 at 09:37
To: WCAG <w3c-wai-gl@w3.org>
Cc: "lisa.seeman@zoho.com" <lisa.seeman@zoho.com>
Subject: Re: timeouts
Resent-From: WCAG <w3c-wai-gl@w3.org>
Resent-Date: Friday, December 1, 2017 at 09:36
 
+1
 
On Friday, December 1, 2017 8:47 AM, John Foliot <john.foliot@deque.com> 
wrote:
 
+1
 
JF
 
On Thu, Nov 30, 2017 at 10:00 AM, lisa.seeman <lisa.seeman@zoho.com> 
wrote:
The coga task force can live with the following wording for time outs
 
 Where data can be lost due to user inactivity, users are warned once, 
before an activity timer is set, about the estimated length of inactivity 
that generates the data loss, unless the data is preserved for a minimum 
of 20 hours of user inactivity.
 
however we do object to the  change the hours from 20 to 24 , but we would 
rather it goes in with that change then be left out.
All the best

Lisa Seeman

LinkedIn, Twitter



 
-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com
 
Advancing the mission of digital accessibility and inclusion