Skip to content

All: Normalize keyboard interaction markup #222

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

Closed
wants to merge 3 commits into from

Conversation

scottgonzalez
Copy link
Member

Follow up to discussion in #218. All key commands are now wrapped in code blocks. Key combos have spaces around + to ease the mental parsing. There were a mix of colons and dashes between the keys and the description; I chose to normalize to the dashes since they provide additional visual spacing to ease the mental parsing.

<li><code>HOME</code>/<code>PAGE UP</code> - Move focus to the first item.</li>
<li><code>ESCAPE</code> - Close the menu.</li>
<li><code>ENTER</code>/<code>SPACE</code> - Select the currently focused item and close the menu.</li>
<li><code>ALT</code> + <code>UP</code>/<code>DOWN</code> - Toggle the visibility of the menu.</li>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ALT / OPTION ?

@tjvantoll
Copy link
Member

An em dash (—) is usually used in lists like this rather than a hyphen (-). I don't think there's a hard and fast rule though, so feel free to ignore that.

This looks good.

@scottgonzalez
Copy link
Member Author

Added OPTION everywhere we have ALT. I tried using em dashes, but it didn't provide the same visual break since they're not used with spaces, so I switched back to colons.

@tjvantoll
Copy link
Member

I like colons. This looks good. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants