starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Access keys for new tab drop down menu items #8613

New Issue
Open
opened 2026-01-31 01:33:48 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 01:33:48 +00:00
Owner
Copy Link

Originally created by @zackste on GitHub (May 26, 2020).

Description of the new feature/enhancement

Currently, bringing up the new tab drop down requires using arrow keys to move to each option. It would make accessibility easier if users could press access keys that correlate with each entry to jump to that entry or cycle through similarly identified entries.

Proposed technical implementation details (optional)

One possible solution:
If the menu looks like the following,

  • PowerShell
  • Command Prompt
  • PSCore
  • Settings
  • Feedback
  • About

It would be helpful if a user could press p twice to select "PSCore" or c once to select "Command Prompt". This may be doable simply by setting AccessKey for each MenuFlyoutItem in TerminalPage::_CreateNewTabFlyout.

Another possible solution would be to support _ syntax, mirroring WPF's implementation in the config JSON's profile names.

Originally created by @zackste on GitHub (May 26, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Currently, bringing up the new tab drop down requires using arrow keys to move to each option. It would make accessibility easier if users could press access keys that correlate with each entry to jump to that entry or cycle through similarly identified entries. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. --> One possible solution: If the menu looks like the following, * **P**owerShell * **C**ommand Prompt * **P**SCore * <hr> * **S**ettings * **F**eedback * **A**bout It would be helpful if a user could press `p` twice to select "PSCore" or `c` once to select "Command Prompt". This may be doable simply by setting `AccessKey` for each `MenuFlyoutItem` in `TerminalPage::_CreateNewTabFlyout`. Another possible solution would be to support `_` syntax, mirroring WPF's implementation in the config JSON's profile names.
claunia added the Issue-FeatureHelp WantedProduct-TerminalArea-UserInterface labels 2026-01-31 01:33:49 +00:00
claunia commented 2026-01-31 01:33:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 24, 2022):

This one's tricky, cause everyone's menu is gonna be different. Maybe we could assign keys based off the first unassigned character in the entry's name?

#9268 also just suggested adding numbers to activate an entry, which didn't seem like a bad idea. I'm thinking now maybe we can reveal those numbers only if the user activated the "show new tab dropdown" action specifically, rather than clicking on the button. Then we could be reasonably sure the user actually opened the menu with the keyboard.

@zadjii-msft commented on GitHub (Aug 24, 2022): This one's tricky, cause everyone's menu is gonna be different. Maybe we could assign keys based off the first unassigned character in the entry's name? #9268 also just suggested adding numbers to activate an entry, which didn't seem like a bad idea. I'm thinking now maybe we can reveal those numbers only if the user activated the "show new tab dropdown" action specifically, rather than clicking on the button. Then we could be _reasonably_ sure the user actually opened the menu with the keyboard.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-UserInterface Help Wanted Issue-Feature Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8613
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?