-
Notifications
You must be signed in to change notification settings - Fork 352
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
Review changes to improve compatibility of keyboard guidance with Mac OS conventions #484
Comments
I think there might be some more to change. There are other patterns where we recommend Accordion
Grid Popup, Feed, Data Grids
Data Grids
Listbox (multiple selection) & Multi-select Trees.
|
@jnurthen, I am unsure about some of those. All the Mac keyboards I have around me have home, end, page up, and page down. And, the Mac keyboard help includes those keys: That said, I did consider having a table listing alternatives for some of those and then adding a note to those patterns. But, I was thinking that I was not aware of any circumstances where those specific key assignments would be problematic ... even if they are not ideal. So, I didn't make it a priority. You think we should? |
I have no knowledge of Mac OS keyboard conventions, so will pass on reviewing this. |
@annabbott, you could look over the changed sections just for editorial errors. You have a great eye for that! Especially the keyboard interaction in combo and spinbutton and the new section 5.8. |
@mcking65 Will do! I should have some time later on today... |
3.7 Combo Box > Textbox Keyboard Interaction > Down Arrow > first hollow bullet: |
Didn't spot anything amiss in 5.8 Key Assignment Conventions for Common Functions or Spinbutton. |
Closing as sufficiently reviewed for this release. This topic will get more attention in the next release starting with issue 506. |
Review the following set of changes made to resolve issue #413 and other problems related to appropriateness of APG keyboard guidance for Mac OS.
Note: The 4 commits related to the above changes are all associated with issue #413.
Task Force Reviews requested as of October 16, 2017
The text was updated successfully, but these errors were encountered: