Skip to content

Include keyboard accelerators in tooltips #3511

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

Merged
merged 1 commit into from
Jan 18, 2022

Conversation

mcooley
Copy link
Contributor

@mcooley mcooley commented Nov 23, 2021

The keyboard accelerators documentation includes a section on tooltips, but the tooltips documentation doesn't say anything about keyboard accelerators. Add a suggestion that when you override the default behavior, you should probably include information about keyboard accelerators so that users can discover them.

Also, the first tooltip in the article ("Click to submit") doesn't follow our recommendation: "Don't make it obvious or just repeat what is already on the screen.". I changed this to "Create a new document", which is a more realistic example where a tooltip might be needed to provide supplemental information.

Recommend including keyboard accelerators in tooltips, and use a more realistic example
@PRMerger20
Copy link
Contributor

@mcooley : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver
Copy link
Contributor

#label:"aq-pr-triaged"

@PRMerger14 PRMerger14 added the aq-pr-triaged tracking label for the PR review team label Nov 23, 2021
@jwmsft
Copy link
Contributor

jwmsft commented Jan 18, 2022

#sign-off

@ktoliver ktoliver merged commit d732a4f into MicrosoftDocs:docs Jan 18, 2022
learn-build-service-prod bot added a commit that referenced this pull request Apr 6, 2023
…c_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants