- From: Katie Haritos-Shea <ryladog@gmail.com>
- Date: Tue, 9 Jan 2018 23:44:36 -0500
- To: "Repsher, Stephen J" <stephen.j.repsher@boeing.com>
- Cc: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAEy-OxHhzaFdT6FogPMV40TTd-YG2=gMbvu-EMB3gNRY6H2R8w@mail.gmail.com>
Steve, I actually agree with you and prefer your suggestion. On Jan 9, 2018 11:40 PM, "Repsher, Stephen J" <stephen.j.repsher@boeing.com> wrote: > I don’t think using words like “appropriate” provides much of a guideline, > so I’m not a fan of either of these. I think Andrew’s roughly captures the > point, but I’d suggest going instead down a path similar to GL 2.3, > Seizures, and stating what we know not to do. Maybe something like: > > > > “Sensors: Do not use device sensors in ways that presume physical > capabilities of the user.” > > > > Note I dropped “additional” and “input”. Neither of these helps the > handle at all. > > > > Katie, your version I think is not the right message. That is, the > guideline should not be to use sensors because there’s no accessibility > reason for that. > > > > Steve > > > > *From:* Katie Haritos-Shea [mailto:ryladog@gmail.com] > *Sent:* Tuesday, January 09, 2018 10:52 PM > *To:* Andrew Kirkpatrick <akirkpat@adobe.com> > *Cc:* WCAG <w3c-wai-gl@w3.org> > *Subject:* Re: Guideline 2.6 text > > > > Weak. > > > > Suggest: Guideline: Sensor Inputs > > > > Provide additional optional functionality using device sensors when > appropriate > > > > > > > > > > On Jan 9, 2018 10:42 PM, "Andrew Kirkpatrick" <akirkpat@adobe.com> wrote: > > Thoughts on this? > > http://rawgit.com/w3c/wcag21/2.6GL/guidelines/index.html# > additional-sensor-inputs > > > > Thanks, > > AWK > > > > Andrew Kirkpatrick > > Group Product Manager, Accessibility > > Adobe > > > > akirkpat@adobe.com > > http://twitter.com/awkawk > > >
Received on Wednesday, 10 January 2018 04:45:04 UTC