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<mailto: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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fil.linkedin.com%2Fin%2Flisaseeman%2F&data=02%7C01%7Cakirkpat%40adobe.com%7C4cc65966f9ce44ef1d6a08d538c907d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477358425177460&sdata=h9TYyQc9NVdodbVxUmIAVuSviDwAI38HcflS91w98rI%3D&reserved=0>, Twitter<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftwitter.com%2FSeemanLisa&data=02%7C01%7Cakirkpat%40adobe.com%7C4cc65966f9ce44ef1d6a08d538c907d1%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477358425177460&sdata=a9VFXTMDhGY3i%2BdDpvY0Sw1jgmjYfCfGHp%2FT5pXsSsk%3D&reserved=0>




--
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com<mailto:john.foliot@deque.com>

Advancing the mission of digital accessibility and inclusion