W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2018

Re: CFC - Updated Response to issues 386, 659, and 660, 669, and 688 on Character Key Shortcuts

From: Kim Patch <kim@redstartsystems.com>
Date: Fri, 19 Jan 2018 17:10:31 -0500
To: John Foliot <john.foliot@deque.com>, "Detlev Fischer (TK)" <detlev.fischer@testkreis.de>
Cc: WCAG <w3c-wai-gl@w3.org>
Message-ID: <5A626CD7.70404@redstartsystems.com>
This still addresses this key pain point for speech input users. Noted 
that the understanding document should make this clear.

On 1/18/2018 10:13 AM, John Foliot wrote:
> +1
>
> I remain slightly concerned that we've, if not lost, certainly 
> 'buried' the idea of "single key" shortcut (only mentioned in the 
> definition), as this appeared to be the actual pain-point for 
> voice-input users. Again, I don't want to block progress of this SC, 
> so I can "live with" the current language, with the hope that the 
> Understanding document can elaborate on this point more.
>
> JF
>
> On Thu, Jan 18, 2018 at 9:03 AM, Detlev Fischer (TK) 
> <detlev.fischer@testkreis.de <mailto:detlev.fischer@testkreis.de>> wrote:
>
>     +1
>     Detlev
>
>     Am 18.01.2018 um 01:14 schrieb Andrew Kirkpatrick:
>
>
>         Call For Consensus — ends Friday January 19th at 7pm Boston time.
>
>         The Working Group has discussed responses to the following issues:
>
>         386: What do 'character key' and 'printable' mean?
>         (https://github.com/w3c/wcag21/issues/386
>         <https://github.com/w3c/wcag21/issues/386>)
>
>         659: Ambiguous definition
>         (https://github.com/w3c/wcag21/issues/659
>         <https://github.com/w3c/wcag21/issues/659>)
>
>         660: Characters (https://github.com/w3c/wcag21/issues/660
>         <https://github.com/w3c/wcag21/issues/660>)
>
>         669: SC 2.4.11 Character Key Shortcuts - Proposal for change
>         of wording (https://github.com/w3c/wcag21/issues/669
>         <https://github.com/w3c/wcag21/issues/669>)
>
>         688: Comment on 2.4.11
>         (https://github.com/w3c/wcag21/issues/688
>         <https://github.com/w3c/wcag21/issues/688>)
>
>         Response to Issue 386:
>         https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#386
>         <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#386>
>
>         Response to Issue 659:
>         https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#659
>         <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#659>
>
>         Response to Issue 660:
>         https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#660
>         <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#660>
>
>         Response to Issue 669:
>         https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#669
>         <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#669>
>
>         Response to Issue 688:
>         https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#688
>         <https://www.w3.org/WAI/GL/wiki/Draft_Responses_to_Dec_WD_Issues#688>
>
>         The changes to the SC are implemented in this pull request:
>         https://github.com/w3c/wcag21/pull/732
>         <https://github.com/w3c/wcag21/pull/732>
>
>         The changed SC can be viewed here:
>         http://rawgit.com/w3c/wcag21/character_changes/guidelines/index.html#character-key-shortcuts
>         <http://rawgit.com/w3c/wcag21/character_changes/guidelines/index.html#character-key-shortcuts>
>
>         Since the original CFC, this has been updated to remove the
>         mention of the shift key, and to remove the mention of space
>         and enter (see specific commit here:
>         https://github.com/w3c/wcag21/pull/732/commits/4f7d83ea030329529ede8f0f577abf51a18745a7
>         <https://github.com/w3c/wcag21/pull/732/commits/4f7d83ea030329529ede8f0f577abf51a18745a7>)
>
>         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 <mailto:akirkpat@adobe.com>
>         <mailto:akirkpat@adobe.com <mailto:akirkpat@adobe.com>>
>
>         http://twitter.com/awkawk
>         <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0
>         <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Ftwitter.com%2Fawkawk&data=02%7C01%7C%7C54093524ef264326424008d51cd66c05%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446629619786436&sdata=c5UP0xiniJIppvd6Esu1XA%2FbX1ykpABkhgCCmBp%2Fht8%3D&reserved=0>>
>
>
>     -- 
>     ---------------------------------------------------------------
>     Detlev Fischer PhD
>     Testkreis
>     http://testkreis.de
>
>     Telefon: +49-40-43 18 75-25 <tel:%2B49-40-43%2018%2075-25>
>     Mobile: +49-157 57 57 57 45 <tel:%2B49-157%2057%2057%2057%2045>
>     Fax: +49-40-43 18 75-45 <tel:%2B49-40-43%2018%2075-45>
>     E-Mail: detlev.fischer@testkreis.de
>     <mailto:detlev.fischer@testkreis.de>
>
>     Anschrift: Werderstr. 34, 20166 Hamburg
>     Amtsgericht Hamburg HRB 58 167
>     ---------------------------------------------------------------
>
>
>
>
>
> -- 
> John Foliot
> Principal Accessibility Strategist
> Deque Systems Inc.
> john.foliot@deque.com <mailto:john.foliot@deque.com>
>
> Advancing the mission of digital accessibility and inclusion

-- 
___________________________________________________

Kimberly Patch
President
Redstart Systems
(617) 325-3966
kim@redstartsystems.com <mailto:kim@redstartsystems.com>

www.redstartsystems.com <http://www.redstartsystems.com>
- making speech fly

Blog: Patch on Speech
+Kim Patch
@RedstartSystems
www.linkedin.com/in/kimpatch <http://www.linkedin.com/in/kimpatch>
___________________________________________________
Received on Friday, 19 January 2018 22:10:55 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:22 UTC