RE: aria-kbdshortcuts feedback

Hi Rich,

 

I do agree with your comments, however I think as well that as the ARIA WG addresses aria-keyboardshortcuts [sic] that any solution be in step with, and not counter to, work that is happening around @accesskey 

 

JF

 

From: Richard Schwerdtfeger [mailto:richschwer@gmail.com] 
Sent: Wednesday, February 24, 2016 10:27 AM
To: John Foliot <john.foliot@deque.com>
Cc: Dominic Mazzoni <dmazzoni@google.com>; ARIA Working Group <public-aria@w3.org>; James Craig <jcraig@apple.com>; Charles McCathie Nevile <chaals@yandex-team.ru>
Subject: Re: aria-kbdshortcuts feedback

 

The accesskey Charles is proposing suffers from similar issues regarding knowing the keyboard type. 

 

How are the accesskeys exposed to ATs?

This implementation of accesskeys requires they be visible but if the author does not want to show them all the time will the be active? … What if the accesskeys are such that:

 

<nav hidden>

…

</nav>

 

 

Rich

 

On Feb 24, 2016, at 10:02 AM, John Foliot <john.foliot@deque.com <mailto:john.foliot@deque.com> > wrote:

 

Hi All,

 

I suspect that there will be an intersection between this topic and Chaals’ current Draft Proposal on @accesskey, found here:  <http://chaals.github.io/accesskey/index.src.html> http://chaals.github.io/accesskey/index.src.html

 

Specifically to one of James’ concerns, there is a consideration for i18n in there.

 

(Note to Chaals: the Contents link to “ <http://chaals.github.io/accesskey/assigning-keyboard-shortcuts> 5.5 Assigning Keyboard Shortcuts” in the current draft is broken)

 

JF

 

From: Richard Schwerdtfeger [mailto:richschwer@gmail.com] 
Sent: Wednesday, February 24, 2016 9:32 AM
To: Dominic Mazzoni <dmazzoni@google.com <mailto:dmazzoni@google.com> >
Cc: ARIA Working Group <public-aria@w3.org <mailto:public-aria@w3.org> >; James Craig <jcraig@apple.com <mailto:jcraig@apple.com> >
Subject: Fwd: aria-kbdshortcuts feedback

 

Hi Dominic, 

 

You put the original proposal in for this so I wanted to bring you into this discussion. 

 

I would imagine that anyone implementing keyboard shortcuts would need to know their are limitations beyond knowing what the languages is for the page, regarding the keyboard being used. Given that you know the language you are targeting do you feel it is enough to be able to determine your keyboard shortcuts when authoring a page? 

 

Have you vetted this with the Google i18N experts?

 

I personally don’t have issues with James name change to aria-keyboardshortcuts other than it is very long or the use of the word control (this is spelled out on Mac keyboards). 

 

We are working toward locking ARIA 1.1 down so that we can move on to ARIA 2.0, web component support, etc. 

 

Rich






Begin forwarded message:

 

From: James Craig < <mailto:jcraig@apple.com> jcraig@apple.com>

Subject: aria-kbdshortcuts feedback

Date: February 24, 2016 at 3:33:06 AM CST

To: ARIA Working Group < <mailto:public-aria@w3.org> public-aria@w3.org>

Resent-From:  <mailto:public-aria@w3.org> public-aria@w3.org

 

Issue #1: Name: kbdshortcuts. With the notable exception/oversight of the "img" role, ARIA doesn't use abbreviations like "kbd" in role or attribute names. This one should be changed to aria-keyboardshortcuts or something shorter like aria-hotkeys.

Issue #2: Spec examples make it seem as if both "Control" and "Ctrl" are valid values. My interpretation of the KeyboardEvent spec is that only "Control" is valid.

Issue #3: This prose:





When specifying a key on the keyboard that changes when you hold down a modifier key other than an alphabetic key, you must specify the unmodified key name. For example, on most U.S. English keyboards, the percent sign "%" can be printed by pressing Shift+5. The correct way to specify this shortcut is "Shift+5". It is incorrect to specify "%" or "Shift+%". However, note that on some international keyboards the percent sign may be an unmodified key, in which case "%" and "Shift+%" would be correct on those keyboards.



If I recall correctly, I raised this specific example on the list last year as a reason for not including the property in ARIA 1.1. It is not possible for the web application to know which keyboard is being used and therefore not possibly to implement this feature in a i18n-friendly manner. Simply stating in prose that there is a problem does not resolve the problem. 

Please don't publish this feature without consulting some of the W3C i18n experts.

Issue #4: Editorial: Spec does not list [ARIA 1.1] on this property.