W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2017

Re: Issue #69: Character key commands

From: John Foliot <john.foliot@deque.com>
Date: Tue, 16 May 2017 07:20:42 -0500
Message-ID: <CAKdCpxxdT-FfyrTVAsirx3Akg8MJ0aJnTm=ewt8U7Nx6isbs3w@mail.gmail.com>
To: "Patrick H. Lauke" <redux@splintered.co.uk>
Cc: WCAG <w3c-wai-gl@w3.org>
Greg wrote:

> We should standardize on either "character key" or "printing key" rather
than mixing the two terms in the same to mean the same thing. While
"printing key" is the one I'm more used to seeing in the past, I think
"character key" is more intuitive to readers unfamiliar with the concept.

However, as I pointed out recently, even the terms "printing key" and/or
"character key" have some issues elsewhere at the W3C, specifically around
internationalization.

"For example, on the Hindi INSCRIPT keyboard layout on Windows the TRA key
(on number 6) when pressed generates the following Unicode code point
sequence: U+0924 (TA) + U+094D (Virama) + U+0930 (RA).

We suggest the following wording:

If specified, the value must consist of a string representing an available
keystroke. For most languages, this will be a single printable Unicode code
point."
     (source: https://github.com/w3c/html/issues/485)

​At a minimum, our Technical standard should align with other W3C
publications, and while I can live with continued colloquial use​ of
either "printing
key" and/or "character key", I will request that we also include a
definition in our glossary that reflects the fact that what we mean is "single
printable Unicode code point.".

Thanks.

JF


On Tue, May 16, 2017 at 2:48 AM, Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 16/05/2017 06:45, Gregg C Vanderheiden wrote:
> [...]
>
>> But I can’t think of the disadvantage.
>>
>> can someone help me here?
>>
>> [...]
>
>>   * it prevents the user from using the ‘e’ key for anything else — but
>>     (since this only happens if they have focus on the page — and there
>>     is nothing that the ‘e’ key can do on the page when not in edit mode
>>     — I’m missing the problem.
>>
>
> I have made this particular point many times before as well...these
> single-key commands would only trigger accidentally in situations where the
> user is not on a control/element that is editable. However, it seems that
> the main concern is accidental unintended triggering (e.g. by overeager
> speech recognition, or by unintentionally hitting a key on the keyboard).
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>


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

Advancing the mission of digital accessibility and inclusion
Received on Tuesday, 16 May 2017 12:21:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 08:04:10 UTC