Re: CFC - Concurrent Input Mechanisms SC

​+1​


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 Tue, Aug 8, 2017 at 12:00 PM, Bradley Montgomery, Rachael L. <
rbradley@mitre.org> wrote:

> +1
>
>
>
> Rachael
>
>
>
> *From:* Andrew Kirkpatrick [mailto:akirkpat@adobe.com]
> *Sent:* Tuesday, August 8, 2017 11:38 AM
> *To:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* CFC - Concurrent Input Mechanisms SC
> *Importance:* High
>
>
>
> Call For Consensus — ends Thursday August 10th at 12:00pm Boston time.
>
>
>
> The Working Group has reviewed and approved a new Success Criteria for
> inclusion in the Editor’s Draft: Concurrent Input Mechanisms, at AA, with
> the goal of obtaining additional input external to the working group.
>
>
>
> Call minutes: https://www.w3.org/2017/08/08-ag-minutes.html
>
>
>
> The new SC can be reviewed here, in the context of the full draft:
>
> https://rawgit.com/w3c/wcag21/concurrent-input-mechanisms_
> ISSUE-64/guidelines/#concurrent-input-mechanisms
> <https://rawgit.com/w3c/wcag21/target-size_ISSUE-60/guidelines/#target-size>
>
>
>
> 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
>
> http://twitter.com/awkawk
>
>
>