microsoft / microsoft/calculator

Show next set of access key shortcuts immediately

Open
#378 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Area: Accessibility Bug Pri: 2 triage approved
Dominant language
C#
Stars
31.1k
Forks
5.8k
PR merge metrics
No merged PRs in 30d

Description

When a menu is opened with the keyboard, the choices for the next menu keys should be shown immediately. For example, when you press Alt+H, you should see the choices for next keys you can press. Currently, you don't see anything.

There is a workaround. If you press Alt+H and then press Alt again, you see the next key choices. The extra key press shouldn't be necessary. If the user presses Alt+H, he's going to want to press another key to do something next. Immediately showing the next menu choices goes way back. It's in the Office Ribbon, It's in the standard Windows pull-down menu. It was in pull-down menus in DOS apps like Quick Basic in the 1980s. I image if you dug out a old copy of Lotus 1-2-3, and pressed "/" (it's menu key), it would show you what you could type next there, too. :-)

Device and Application Information:

  • OS Build: 10.0.17763.0
  • Architecture: X64
  • Application Version: 10.1812.10048.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Alt+H sequence in the Calculator application on the reported Windows build, then compare it with pressing Alt again. Trace the keyboard access-key handling and menu display entry points involved. Done means the next available menu keys appear immediately after Alt+H without the extra Alt press, while normal menu navigation still works.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
accessibility, desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.