Re: CFC - Device Sensors

+1 to Katie's point.

JF

On Mon, Aug 28, 2017 at 9:36 AM, Katie Haritos-Shea GMAIL <ryladog@gmail.com
> wrote:

> While updating 2.1.1 *seems* like a good idea, I have to caution against
> changing any 2.0 SC in a dot release. Documentation and tools worldwide
> will need to be updated as opposed to just adding a new requirement.
>
> ​​​​​** katie **
>
>
>
> *Katie Haritos-Shea*
> *Principal ICT Accessibility Architect**,* *IAAP **CPACC*
> <http://www.accessibilityassociation.org/recentlycertified>*
> (WCAG/Section 508/ADA/AODA)*
>
>
>
> *Cell: 703-371-5545 <(703)%20371-5545> **|* *ryladog@gmail.com*
> <ryladog@gmail.com> *|* *Oakton, VA **|* *LinkedIn Profile*
> <http://www.linkedin.com/in/katieharitosshea/> *|* *Office: 703-371-5545
> <(703)%20371-5545> **|* *@ryladog* <https://twitter.com/Ryladog>
>
> NOTE: The content of this email should be construed to always be an
> expression of my own personal independent opinion, unless I identify that I
> am speaking on behalf of Knowbility, as their AC Rep at the W3C - and -
> that my personal email never expresses the opinion of my employer, Deque
> Systems.
>
>
>
> *From:* Joshue O Connor [mailto:josh@interaccess.ie]
> *Sent:* Monday, August 28, 2017 9:58 AM
> *To:* White, Jason J <jjwhite@ets.org>
> *Cc:* David MacDonald <david100@sympatico.ca>; Patrick H. Lauke <
> redux@splintered.co.uk>; w3c-wai-gl@w3.org
>
> *Subject:* Re: CFC - Device Sensors
>
>
>
> White, Jason J wrote:
>
> I share David’s concerns. I think that not filtering the list of SCs more
> effectively at this stage is just postponing the hard decisions and
> creating a lot of work for us as we move toward Candidate Recommendation.
>
> That is something we want to avoid. If I'm reading this all correctly, I'm
> keen on your idea of an exception to 2.1.1 that covers sensors - or at
> least some of the current use cases (thanks Kim).
>
> My problem/reservation with that is the approach is an implicit way of
> dealing with these use cases and not a more 'visible' SC that is future
> proof when it comes to more 'sensor aware' technologies. Hence my bringing
> this whole thing up again.
>
> I'm quite torn on this one tbh.
>
> Thanks
>
> Josh
>
>
>
> *From:* David MacDonald [mailto:david100@sympatico.ca
> <david100@sympatico.ca>]
> *Sent:* Saturday, August 26, 2017 9:35 AM
> *To:* Joshue O Connor <josh@interaccess.ie> <josh@interaccess.ie>;
> Patrick H. Lauke <redux@splintered.co.uk> <redux@splintered.co.uk>;
> w3c-wai-gl@w3.org
> *Subject:* Re: CFC - Device Sensors
>
>
>
> I had objected to the SC on survey... citing redundancy with 2.1.1
>
>
>
> However, I reluctantly provided consensus. I still hold to that. However
> my big concern is that we only have a couple of months the vet 23 success
> criteria and put them in the shape that is ready for a formal
> consideration. We also have to write techniques and the understanding
>  sections. There are several success criteria I didn't have strong
> consensus and I am concerned about the amount of bandwidth they will take
> up once we get into the thick of finalization.
>
>
>
>  So my hope is that this concern will be respected and that we will not
> lose too much bandwidth on the success criteria that we let pass-through.
> If so I would strongly object proceeding with this one.
>
>
>
> On Sat, Aug 26, 2017 at 7:55 AM Joshue O Connor <josh@interaccess.ie>
> wrote:
>
> Thanks Patrick, yes, I'd be happy to see that. Do others agree to this
> approach?
>
>
>
> Thanks
>
>
>
> Josh
>
>
>
> InterAccess - Accessible UX
>
>
>
> -------- Original message --------
>
> From: "Patrick H. Lauke" <redux@splintered.co.uk>
>
> Date: 26/08/2017 12:27 (GMT+00:00)
>
> To: w3c-wai-gl@w3.org
>
> Subject: Re: CFC - Device Sensors
>
>
>
> On 26/08/2017 10:44, Joshue O Connor wrote:
> [...]
> > So, I'm concerned that if we do not now get wider review we risk
> > throwing the baby out with the bathwater. I'm actually not comfortable
> > taking the opportunity for wider review when what seems like an
> > interesting/progressive SC is on the table.
>
> Any chance of adding a prominent editorial note in the draft pointing
> out that the exact wording is under review due to potential scope issues?
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.splintered.co.uk&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=sSG6u8Hf53Q8GaY31T8cnX7hPINwhrj9tpR1gLyEy2c%3D&reserved=0>
> | https://github.com/patrickhlauke
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpatrickhlauke&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=EK9xbI0MkIqs1MNj7XXFByXYOkf6kWE8%2FZLHifqQWC8%3D&reserved=0>
> http://flickr.com/photos/redux/
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fflickr.com%2Fphotos%2Fredux%2F&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=YKcmP5xYGUjg%2BvVxayT4FYZ9uakXFmmZ%2BG5Rpc8uDzY%3D&reserved=0>
> | http://redux.deviantart.com
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fredux.deviantart.com&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=BaVForXb7ZJ8Tj94ZcUOzf9S9t%2BcECUGc9oWRWbliu0%3D&reserved=0>
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
> --
>
> Cheers,
> David MacDonald
>
>
>
> *Can**Adapt* *Solutions Inc.*
>
> Tel:  613.235.4902 <(613)%20235-4902>
>
> LinkedIn
>
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fdavidmacdonald100&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=BEmffR3fanUAszNRNy6enllf2HoQLQ%2BRgTSZ9u1x6PY%3D&reserved=0>
>
> twitter.com/davidmacd
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fdavidmacd&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=Xmpegt0vrW%2BEic1TizzrokwnEC%2BzD%2FgX6vfnabSZ3Xk%3D&reserved=0>
>
> GitHub
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDavidMacDonald&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=kYx6VbenhhJOT1JKcPHXHbLbrvpEucMmjsW4pMUNUic%3D&reserved=0>
>
> www.Can-Adapt.com
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.can-adapt.com%2F&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=Py%2Fa1SOPj%2FIV5R4JkYgSVTp30EegAy13p%2BcSlzyqXXQ%3D&reserved=0>
>
>
>
> *  Adapting the web to all users*
>
> *            Including those with disabilities*
>
>
>
> If you are not the intended recipient, please review our privacy policy
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.davidmacd.com%2Fdisclaimer.html&data=02%7C01%7Cjjwhite%40ets.org%7Ca1e9482570f1413ea1cc08d4ec8763ec%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C636393513638044677&sdata=vLcc0RRERhFToOxmZZRjA5%2Fe06RYtXsjXyQ2uNqq2z4%3D&reserved=0>
>
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
>
>
> Thank you for your compliance.
> ------------------------------
>
>
>
> --
> Joshue O Connor
> Director *| InterAccess.ie *
>



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

Advancing the mission of digital accessibility and inclusion