Re: Response to Issue #761

Agreed. That is why I said “consider” rather than “we will” – I’m not sure that they apply either but am willing to commit to thinking about it more.

Thanks,
AWK

Andrew Kirkpatrick
Group Product Manager, Accessibility
Adobe

akirkpat@adobe.com
http://twitter.com/awkawk


From: Alastair Campbell <acampbell@nomensa.com>
Date: Wednesday, February 7, 2018 at 11:41
To: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
Subject: RE: Response to Issue #761

HI Andrew,

I wonder how relevant the Alexa/other voice assistants are for this one? In which case it might not be possible to provide an example.

Firstly, although I haven’t gotten one (yet), but my understanding is that you are interacting with the provider’s specific API, it is not accessing web content directly.

Secondly, these interfaces may not be working via keyboard access at all. Typical AT would, but the primary interface of these devices is voice, it is more akin to a voice-based command-line than a GUI with keyboard short-cuts.

I’m trying not to get stuck in an accessibility/AT-focused viewpoint, but I’m not seeing how these devices are relevant. Just because it works by voice, doesn’t put it in the same category as something like Dragon NS.

Cheers,

-Alastair


From: Andrew Kirkpatrick

I made a proposed response to 761: https://github.com/w3c/wcag21/issues/761#issuecomment-363815103<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwcag21%2Fissues%2F761%23issuecomment-363815103&data=02%7C01%7Cakirkpat%40adobe.com%7C751b45a3f055456bb82b08d56e49af29%7C71f1da39c0a84d5a8d88a67b23c30bf4%7C0%7C0%7C636536185118952639&sdata=L7O3j3cfMbY9QV34dOP7DUr8g5PWZmgU3zIpB8sxakw%3D&reserved=0>

Thoughts? Changes?

Kim Patch, would be good to get your thoughts on this.

Thanks,
AWK