-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aria-keyshortcuts
needs attention?
#2141
Comments
Discussed briefly at the end of our meeting today: https://www.w3.org/2024/03/14-aria-minutes.html#t02 |
Would it be convenient for us to do a joint call (such as joining your next call) to discuss? On the one hand, the purpose of this seems clear. On the other hand, we found a bunch of questions relating to the keyboard and I18N jargon. I think we could make quick work of this with a higher-bandwidth conversation. |
@aphillips wrote:
I think your point is clear enough. I raised some similar concerns (inc the french keyboard numbers being on the shift plane) when the attribute was proposed. I dropped the objection when @aleventhal agreed that the web app should localize this (as Google Docs and others do), not the engine. But I agree with all the reasons you gave for the prose needing to change. |
@aphillips If you're open to writing (or co-writing a PR) that might be the most efficient way to proceed. @aphillips If you think a small group meeting is necessary, I'd like @aleventhal to attend or assign a member of his team to attend, since Google Docs was the primary driver for this feature. I'd like to attend too (optionally), and the I think the @w3c/aria-editors would attend too. |
Briefly discussed in the working group meeting today, with the conclusion being @cookiecrook comment above: https://www.w3.org/2024/03/21-aria-minutes.html#t06 |
Hi @aphillips Have you had a chance to review [James' comment](#2141 (comment) above? Thanks much. |
@daniel-montalvo @cookiecrook Thanks for the response. I'm open to writing or co-writing a PR. I usually try to make concrete text proposals in comments (rather than just saying "hey, this looks wrong..."). However, in this case, I'd need to understand some things before I could propose text, hence my desire to chat about it before diving in. We don't have to do a super-formal call--we can just jump on Slack or Zoom or such. We're both in Norcal, so it should be easy enough to sync schedules. |
I'm on the W3C Slack, and another contact is firstname at GH username with the most common TLD. (This type of obfuscation won't deter the AI bots for long, will it?) |
aria-keyshortcuts property
https://www.w3.org/TR/wai-aria-1.3/#aria-keyshortcuts
The internationalization (I18N) working group reviewed 1.3 as part of horizontal review. In the course of doing this review, we found the below quoted text about the
aria-shortcuts
property. We aren't sure how shortcuts are used with assistive technology, but the description given provokes a number of concerns for us. We think the best course of action here would be to discuss key shortcuts in more detail.Specific concerns:
key typed
value rather than the key combination used to produce it. For example, one might want the letter "A" to be a hot key, regardless of what key is printed with the letter "A" or what modifiers are needed to produce it. Some modifiers, however, such as Control and Alt/AltGr have additional "short-cut-like" meaning. Understanding the usage here would let us comment more productively.The text was updated successfully, but these errors were encountered: