Re: CFC Add Device Sensors to Editors Draft

​I won't object but this SC does not require anything that is not already
required in 2.1.1. As far as I can see... It requires things work without
sensors, 2.1.1 requires everything work with a keyboard, which is not a
sensor, so if the author passes 2.1.1, they pass this, no?


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 Wed, Jun 21, 2017 at 9:42 AM, Katie Haritos-Shea <ryladog@gmail.com>
wrote:

> +1
>
> Katie Haritos-Shea
> 703-371-5545 <(703)%20371-5545>
>
> On Jun 21, 2017 9:08 AM, "Denis Boudreau" <denis.boudreau@deque.com>
> wrote:
>
> +1
>
>
>
>
>
> /Denis
>
> --
> Denis Boudreau,
> Principal accessibility consultant & trainer
> Deque Systems, Inc.
> Cell: +1-514-730-9168 <(514)%20730-9168>
> Email: denis.boudreau@deque.com
>
> Keep in touch: @dboudreau
>
>
>
> *From: *Chris Loiselle <loiselles@me.com>
> *Sent: *June 21, 2017 8:24 AM
> *To: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *Re: CFC Add Device Sensors to Editors Draft
>
>
>
> +1
>
> Thank you,
>
>
>
> Chris Loiselle
>
> 781-724-4990 <(781)%20724-4990>
>
>
> On Jun 20, 2017, at 6:16 PM, Kathy Wahlbin <kathy@interactiveaccessibilit
> y.com> wrote:
>
> +1
>
>
>
> Kathy
>
> CEO & Founder
>
> Interactive Accessibility
>
>
>
> *T* (978) 443-0798 <(978)%20443-0798>  *F* (978) 560-1251
> <(978)%20560-1251>  *C* (978) 760-0682 <(978)%20760-0682>
> *E* kathyw@ia11y.com
>
> www.InteractiveAccessibility.com
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.interactiveaccessibility.com_&d=CwMGaQ&c=jxhwBfk-KSV6FFIot0PGng&r=UK__SX18Mp9Fb6tIJfzgjkhM1qTux9WksegD3zR-Bss&m=Kyx2xjSikKdohzK4YYjpf6lkpNeSYzbcW2-3BWkmRfM&s=QvEa6SOOfiPYi3edgtQBne9UjZFUHulJz3xqkGwAu7o&e=>
>
>
>
> NOTICE: This communication may contain privileged or other confidential
> information. If you are not the intended recipient, please reply to the
> sender indicating that fact and delete the copy you received. Thank you.
>
>
>
> *From:* Joshue O Connor [mailto:josh@interaccess.ie <josh@interaccess.ie>]
>
> *Sent:* Tuesday, June 20, 2017 1:04 PM
> *To:* WCAG <w3c-wai-gl@w3.org>
> *Subject:* CFC Add Device Sensors to Editors Draft
>
>
>
> Call For Consensus — ends Friday June 23rd at 1:00pm Boston time.
>
>
>
> The Working Group has reviewed and approved a Success Criterion for
> inclusion in the Editor’s Draft: "Device Sensors" with the goal of
> obtaining additional input external to the working group.
>
> NOTE: The resolution  was to Accept this SC into editors draft and
> include a note to say that the preference of the group is to alter an
> existing SC rather than add a new one.
>
> SC TEXT:
>
> "All functionality of the content can be operated without requiring
> specific device sensor information unless the device sensor is essential
> for the function and not using it would invalidate the activity."
>
>
>
> Survey results:
> *https://www.w3.org/2002/09/wbs/35422/Top3_18Apr2017/results
> <https://www.w3.org/2002/09/wbs/35422/Top3_18Apr2017/results> *
> GIT Hub: https://github.com/w3c/wcag21/issues/67
>
> The new SC can be reviewed here:
> https://rawgit.com/w3c/wcag21/device-sensors_ISSUE-67/guidel
> ines/sc/21/device-sensors.html
>
> 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
>
> --
> Joshue O Connor
> Director *| InterAccess.ie <http://InterAccess.ie> *
>
>
>
>
>