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 [http://www.twitter.com/dboudreau]


On 2017-08-18 5:28:40 AM, Alastair Campbell <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://rawgit.com/w3c/wcag21/timeouts_ISSUE-14/guidelines/#timeouts] 
 
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 [http://twitter.com/awkawk]