Re: CFC - Timeouts SC

Jake,
During a CFC we aren’t making changes. Can you live with it as it is?
Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com
http://twitter.com/awkawk


From: "Abma, J.D. (Jake)" <Jake.Abma@ing.nl<mailto:Jake.Abma@ing.nl>>
Date: Sunday, August 20, 2017 at 06:26
To: Denis Boudreau <denis.boudreau@deque.com<mailto:denis.boudreau@deque.com>>, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>, WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: Re: CFC - Timeouts SC
Resent-From: WCAG <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Resent-Date: Sunday, August 20, 2017 at 06:27


As the proposed Level is AAA and thus the security objections of extending the message for the respond time will not be applicable anymore I would suggest to still look if we can add this here.

Informing about the Timeouts (and possibly the time you’ll have to extend this / 20 seconds…) but not providing a way to extend this if you’re not able to respond in limited time would be a missed opportunity.

If (20 seconds) security is not the issue and if the default is 20 seconds to respond BUT 40 or 60 or … would also be an option to choose from we solve one of the core issues this SC is about anyway.


________________________________
From: Denis Boudreau (Deque) <denis.boudreau@deque.com<mailto:denis.boudreau@deque.com>>
Sent: Friday, August 18, 2017 3:14 PM
To: Alastair Campbell; w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>
Subject: Re: CFC - Timeouts SC

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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.twitter.com%2Fdboudreau&data=02%7C01%7C%7Cd40c56780f7e47113e3208d4e7b63a69%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636388217290275620&sdata=fmyA%2FLdP34Jr1uF3XRntI3MvTJ9EQEer%2Fe9wLBHsLdI%3D&reserved=0>


On 2017-08-18 5:28:40 AM, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
+1

From: Andrew Kirkpatrick

Call For Consensus — ends Monday August 21st at 7:00pm Boston time.

The Working Group has reviewed and approved a new Success Criteria for inclusion in the Editor’s Draft: Timeouts, at AA, with the goal of obtaining additional input external to the working group.

Call minutes: https://www.w3.org/2017/08/15-ag-minutes.html


The new SC can be reviewed here, in the context of the full draft:
https://rawgit.com/w3c/wcag21/timeouts_ISSUE-14/guidelines/#timeouts<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Ftimeouts_ISSUE-14%2Fguidelines%2F%23timeouts&data=02%7C01%7C%7Cd40c56780f7e47113e3208d4e7b63a69%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636388217290275620&sdata=yG3WN8HQI%2B5ZvTzoYa2iJ1dAEKwwE%2B%2B4ao6oT9arod0%3D&reserved=0>

If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com<mailto:akirkpat@adobe.com>
http://twitter.com/awkawk<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7Cd40c56780f7e47113e3208d4e7b63a69%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636388217290275620&sdata=DAn7MdqvKtiKkVlOG9kutP0rZfq1dX%2FueDC9MWUpzQ4%3D&reserved=0>


----
ATTENTION: The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.

Received on Monday, 21 August 2017 01:44:29 UTC