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

Re: Add Character Key Shortcuts to Editor's Draft

From: John Foliot <john.foliot@deque.com>
Date: Wed, 7 Jun 2017 08:40:54 -0500
Message-ID: <CAKdCpxxdJDMdO_J9L55sw4Nf6k-S8ke-FRUFRE05o+uFOZMXrw@mail.gmail.com>
To: Alastair Campbell <acampbell@nomensa.com>
Cc: WCAG <w3c-wai-gl@w3.org>
> The discussion got a bit confused towards the end, it wasn’t clear if the
issue being addressed was specific to a user agent?

+1
​ to Alastairs point.​


Perhaps I too misunderstood. The current draft states:

​"​
...turn it off or to remap it to a shortcut that uses at least one
non-character key.
​"


yet I thought we discussed the need for a modifier key in the mix. (I know
I mentioned it, and Jeanne Spellman agreed too)

There are a limited number of​ "non-character" keys available
(consistently) on standard keyboards (less so on portable or smaller
keyboards), and so a simple "map "H" to "F12"" likely isn't going to solve
the problem.

With keyboard shortcuts, as Kim explains it, the scripted feature is
grabbing the keystroke function out of context - it is not the *intent* of
the end-user to fire the shortcut, but it is happening anyway. Insisting on
the ability to insert or re-map the shortcut to a keystroke combination *that
includes a specific modifier-key* essentially solves the problem - the
addition of the modifier-key is what signals the intent to switch from
'standard' keystroke to 'shortcut' keystroke.

I recognize that this current Draft language needs to move forward, and so
I won't oppose the current language AT THIS TIME, but I think we will
likely hear similar feedback from the greater public comments.

Is it too late to fix this?

JF

On Wed, Jun 7, 2017 at 4:21 AM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> +1
>
>
>
> The discussion got a bit confused towards the end, it wasn’t clear if the
> issue being addressed was specific to a user agent?
>
>
>
> However, given that it is only for content implementing a particular
> feature, and it isn’t difficult to do (compared to creating that feature in
> the first place), I’m happy to see it in the draft for public comment.
> Hopefully the description/understanding can be fleshed out to cover that
> better.
>
>
>
> Cheers,
>
>
>
> -Alastair
>
>
>
>
>
> *From: *Andrew Kirkpatrick <akirkpat@adobe.com>
> *Date: *Wednesday, 7 June 2017 at 04:07
> *To: *WCAG <w3c-wai-gl@w3.org>
> *Subject: *CFC: Add Character Key Shortcuts to Editor's Draft
> *Resent-From: *WCAG <w3c-wai-gl@w3.org>
> *Resent-Date: *Wednesday, 7 June 2017 at 04:07
>
>
>
> Call For Consensus — ends Thursday June 8 at 11:00pm Boston time.
>
>
>
> The Working Group has reviewed and approved a new Success Criterion for
> inclusion in the Editor’s Draft: Character Key Shortcuts, at level AA, with
> the goal of obtaining additional input external to the working group.
>
>
>
> Survey results: https://www.w3.org/2002/09/wbs/35422/character-
> key-issue69/results
>
> Call minutes: https://www.w3.org/2017/06/06-ag-minutes.html (after
> resolution on approval process for understanding documents)
>
>
>
> The new SC can be reviewed here, in the context of the full draft:
>
> https://rawgit.com/w3c/wcag21/single-key-shortcuts_ISSUE-69/
> guidelines/#character-key-shortcuts
>
>
>
> 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, Standards and Accessibility
>
> Adobe
>
>
>
> akirkpat@adobe.com
>
> http://twitter.com/awkawk
>
>
>



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

Advancing the mission of digital accessibility and inclusion
Received on Wednesday, 7 June 2017 13:41:29 UTC

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