Skip to content
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.

Sign up for GitHub

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

Jump to bottom

KeyBoard navigation for xOS #413

Closed
jivanova opened this issue Jul 5, 2017 · 1 comment
Closed

KeyBoard navigation for xOS #413

jivanova opened this issue Jul 5, 2017 · 1 comment
Assignees
@mcking65
Labels
Feedback Issue raised by or for collecting input from people outside APG task force question Issue asking a question
Milestone
1.1 APG Release 1

Comments

@jivanova
Copy link

jivanova commented Jul 5, 2017

Currently, my team is working to improve the keyboard navigation for our web component based on w3c standards. I have a question regarding a note we saw in your documentation:

https://www.w3.org/TR/wai-aria-practices-1.1/#aria_ex

The note is about the usage of Control key instead of Cmd under Mac OS. However, our products have shortcuts like Control + ArrowRight which in MAC is reserved shortcut for switching between desktops. According to your guidelines, should we use Cmd key for this scenario or Control and modify our shortcuts? So, what's your advice about how to proceed with such scenarios?
@mcking65 mcking65 added documentation Feedback Issue raised by or for collecting input from people outside APG task force question Issue asking a question labels Jul 27, 2017
@mcking65 mcking65 added this to the 3Q17 Working Draft milestone Jul 27, 2017
mcking65 added a commit that referenced this issue Oct 16, 2017
@mcking65
Combobox Pattern: Remove Windows Specific Keyboard Interactions for T…
d2fc78d 
…extbox

For issue #413, Modified the combobox pattern in aria-practices.html:

1. Delete all the Windows-specific key assignments from the textbox subsection of the keyboard interaction section.
2. Add a note recommending reliance on browser for text editing functionality.

Also related to issue #464.
mcking65 added a commit that referenced this issue Oct 16, 2017
@mcking65
Design Patterns: Remove Mac Command Key Note
f8bca2c 
For issue #413, remove the following note from the introduction of Design Patterns:

> Although users of Mac OS X are familiar with using the Command key instead of the Control key,
> the Command key is typically reserved for desktop applications and OS-level integration.
> Until device and platform independence can be addressed in WAI-ARIA 2.0,
> the primary Control modifier key for WAI-ARIA widget interaction is specified as Control on all platforms, including Mac OS X.
mcking65 added a commit that referenced this issue Oct 17, 2017
@mcking65
Developing Keyboard Interface Section: Move Global KB Guidance from D…
0d38f27 
…esign Patterns and Add Mac OS Conventions

For issue #413, modified Design Patterns section and Keyboard Interface Development sections of aria-practices.html:

1. Move "3.1 Generally Applicable Keyboard Recommendations " to "5.8 Key Assignment Conventions for Common Functions".
2. Add information and guidance about Mac OS assignments for the listed functions.
3. Fix links to the new section, which has id "kbd_common_conventions" instead of "aria_ex_widget".
mcking65 added a commit that referenced this issue Oct 17, 2017
@mcking65
Spin Button and Combobox Patterns: Sync Guidance About Platform Speci…
ed8cb59 
…fic Editing Keys

For issue #413, modified the Combobox and Spin Button design patterns in aria-practices.html:

1. In key assignment lists  of both patterns, use the same wording to make it more clear that the pattern requires platform appropriate editing key assignments.
2. Revise the notes in  both patterns to use list format and more succinctly  describe guidance.
@mcking65 mcking65 mentioned this issue Oct 17, 2017
Closed
2 tasks
@mcking65 mcking65 self-assigned this Oct 17, 2017
@mcking65
Copy link
Contributor

@jivanova, in the above listed commits, I have made several changes that I hope adequately address this issue.

I am closing as resolved. Please feel free to reopen if you do not see the resolution as adequate. You may also provide feedback in issue 484.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mcking65 mcking65

Labels
Feedback Issue raised by or for collecting input from people outside APG task force question Issue asking a question
Projects
None yet
Milestone
1.1 APG Release 1
Development

No branches or pull requests
2 participants
@jivanova @mcking65