Re: timeouts

> So an airline page or a concert ticket page, where you have a limited
time to complete the entire checkout process before the seat is released to
others, would fail if the remaining time were shown at the top of each page
in the checkout process?


No, because that is already required based on SC 2.2.1 Timing Adjustable
(Extend)
​.

However, warning somebody that their session is about to expire when they
are away from their desk effectively means that the session *WILL* expire
more often than not (because the user has stepped away)​, losing any
unsubmitted data.

This SC wants to inform the user *before* the authentication process that
part of 'participating' is that unsaved data will be lost due to
inactivity, so either a) complete the task, or b) partially submit (if you
can) or otherwise save your data, because the system can't or won't. (Sites
should also be encouraged to offer this partial-save feature.)

The timer for these types of timing-out situations is set at the start of
the session (by the server, when the session is established), however the
*countdown* is initiated due to inactivity, and so session termination only
really starts at:

*[user stops activity] + [hello, you there? (for SC 2.2.1)] + [fixed amount
of inactive time before session termination] = timed out*


I
​ could envision, as a basic & simple Technique, something like this:​

Username: ___________

Password:  ___________

[ ] I understand that after 5 minutes of inactivity while logged-in will
result in being logged out, with loss of all unsubmitted data

*(and somebody can wordsmith all they want - JF)*

[ SUBMIT ]

​Does this help?​

JF


On Fri, Dec 1, 2017 at 11:28 AM, James Nurthen <james.nurthen@oracle.com>
wrote:

> So an airline page or a concert ticket page, where you have a limited time
> to complete the entire checkout process before the seat is released to
> others, would fail if the remaining time were shown at the top of each page
> in the checkout process?
>
> On 12/1/2017 9:24 AM, Andrew Kirkpatrick 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.
>
>
>
> Thanks,
>
> AWK
>
>
>
> Andrew Kirkpatrick
>
> Group Product Manager, Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>
> *From: *Michael Gower <michael.gower@ca.ibm.com>
> <michael.gower@ca.ibm.com>
> *Date: *Friday, December 1, 2017 at 12:20
> *To: *Andrew Kirkpatrick <akirkpat@adobe.com> <akirkpat@adobe.com>
> *Cc: *WCAG <w3c-wai-gl@w3.org> <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  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> <akirkpat@adobe.com>
> To:        "W3c-Wai-Gl-Request@W3. Org" <W3c-Wai-Gl-Request@W3.Org>
> <w3c-wai-gl@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://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Ftwitter.com-252Fawkawk-26data-3D02-257C01-257Cakirkpat-2540adobe.com-257C378d77fc8a964101760508d538dfdb85-257Cfa7b1b5a7b34438794aed2c178decee1-257C0-257C0-257C636477456467953915-26sdata-3D32KymBMMErT4tZ5R9gD9hixkX9mOIbBf3Ej-252Bwy-252B2-252BaQ-253D-26reserved-3D0&d=DwMGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=CIHu8rc_0wRTTC_7DvWtiGNKjpA-3oTgbu_6ve6hP0I&m=d0_Aieiu_NYYc8u8rSjUGuaj649eMway29i6PR7s5gA&s=5bosTRuDMzIZxsfJRUatA_wP4e2-9JYjBNJHFLhGB70&e=>
>
>
>
> *From: *Mike Elledge <melledge@yahoo.com> <melledge@yahoo.com>
> * Reply-To: *Mike Elledge <melledge@yahoo.com> <melledge@yahoo.com>
> * Date: *Friday, December 1, 2017 at 09:37
> * To: *WCAG <w3c-wai-gl@w3.org> <w3c-wai-gl@w3.org>
> * Cc: *"lisa.seeman@zoho.com" <lisa.seeman@zoho.com>
> <lisa.seeman@zoho.com> <lisa.seeman@zoho.com>
> * Subject: *Re: timeouts
> * Resent-From: *WCAG <w3c-wai-gl@w3.org> <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>
> <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
>
>
>
>
>
>
> --
> Regards, James
>
> <http://www.oracle.com> James Nurthen | Principal Engineer, Accessibility
> Phone: +1 650 506 6781 <+1%20650%20506%206781> | Mobile: +1 415 987 1918
> <+1%20415%20987%201918> | Video: james.nurthen@oracle.com
> Oracle Corporate Architecture
> 500 Oracle Parkway | Redwood City, CA 94065
> <https://maps.google.com/?q=500+Oracle+Parkway+%7C+Redwood+City,+CA+94065&entry=gmail&source=g>
> <http://www.oracle.com/commitment> Oracle is committed to developing
> practices and products that help protect the environment
>



-- 
John Foliot
Principal Accessibility Strategist
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion