Re: timeouts

Can we just go back to the TPAC version? ... it was almost there... I don't
see any movement forward with this new language.

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Fri, Dec 1, 2017 at 12:36 PM, Jonathan Avila <jon.avila@levelaccess.com>
wrote:

>
>    - As I understand it, the problem is that multiple notifications
>    creates problems. Another interpretation of this is that there can only be
>    one warning in a process covering a series of pages, but that runs into
>    problems with the conformance model.
>
>
>
> It also seems to indicate that a countdown timer would fail.  While I
> understand this could cause stress timers are needed on some sites.
>
>
>
> In other places the timer is reset each time you type something.  So
> perhaps we could differentiate or allow the user to hide the countdown
> timer.
>
>
>
> Jonathan
>
>
>
> *From:* Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
> *Sent:* Friday, December 1, 2017 12:24 PM
> *To:* Michael Gower <michael.gower@ca.ibm.com>
> *Cc:* W3c-Wai-Gl-Request@W3. Org <w3c-wai-gl@w3.org>
> *Subject:* Re: timeouts
>
>
>
> As I understand it, the problem is that multiple notifications creates
> problems. Another interpretation of this is that there can only be one
> warning in a process covering a series of pages, but that runs into
> problems with the conformance model.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>
> *From: *Michael Gower <michael.gower@ca.ibm.com>
> *Date: *Friday, December 1, 2017 at 12:20
> *To: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Cc: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *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
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
>  V8T 5C3
> <https://maps.google.com/?q=1803+Douglas+Street,+Victoria,+BC+%C2%A0V8T+5C3&entry=gmail&source=g>
> 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
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7Cakirkpat%40adobe.com%7C378d77fc8a964101760508d538dfdb85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477456467953915&sdata=32KymBMMErT4tZ5R9gD9hixkX9mOIbBf3Ej%2Bwy%2B2%2BaQ%3D&reserved=0>
>
>
>
> *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
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fil.linkedin.com-252Fin-252Flisaseeman-252F-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C4cc65966f9ce44ef1d6a08d538c907d1-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636477358425177460-26sdata-3Dh9TYyQc9NVdodbVxUmIAVuSviDwAI38HcflS91w98rI-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DKDmkdqR6ul2gWtGasZHFT7Xr7NdL1o5ii4KK0QLchuM%26s%3DATUbvTH4TPf9xBV06j10vQ0FfX6OEA-rsENeAAnB_d0%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C378d77fc8a964101760508d538dfdb85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477456467953915&sdata=%2B9YKqC2xmqiXjORS0YMrEHRiN3l5JuBDn%2FecQjz7618%3D&reserved=0>,
> Twitter
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Ftwitter.com-252FSeemanLisa-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C4cc65966f9ce44ef1d6a08d538c907d1-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636477358425177460-26sdata-3Da9VFXTMDhGY3i-252BdDpvY0Sw1jgmjYfCfGHp-252FT5pXsSsk-253D-26reserved-3D0%26d%3DDwMGaQ%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3D_9rqR3xSCWQUlv9VpOcJwkP7H0XWQXmxeMmqQl6Fikc%26m%3DKDmkdqR6ul2gWtGasZHFT7Xr7NdL1o5ii4KK0QLchuM%26s%3DQY7QMzaLfjW0kPr7i-w8lwBxd7sRYqU5wxR7iO_OcFg%26e%3D&data=02%7C01%7Cakirkpat%40adobe.com%7C378d77fc8a964101760508d538dfdb85%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636477456467953915&sdata=RlQVqjcV7BfYs8IE%2FET%2FQqiIwJ6D4UQfHBURHQSx5ho%3D&reserved=0>
>
>
>
>
>
> --
>
> John Foliot
>
> Principal Accessibility Strategist
>
> Deque Systems Inc.
>
> john.foliot@deque.com
>
>
>
> Advancing the mission of digital accessibility and inclusion
>
>
>
>
>