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

[Terminal> Rename Window]: Keyboard users are not able to access 'Window 1' pop-up when they open it using defined shortcut key. #16248

New Issue
Closed
opened 2026-01-31 05:01:41 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:01:41 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Dec 23, 2021).

Windows Terminal version

1.12.3472.0

Windows build number

10.0.22504.1010

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator
Tool: Accessibility Insights for Windows Version 1.1.1741.1

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using 'Ctr+,'.
  3. Navigate to Settings> Action> Add new button.
  4. Add shortcut 'Ctrl + Shift +r' for 'Rename Window' actions.
  5. Save Changes using 'Save' button.
  6. Then press 'Ctrl + Shift + r' to open 'Window 1' pop-up.
  7. Try to access 'Window 1' pop-up using keyboard.

User Experience:
As pop-up control are not accessible with Keyboard as a result, they will not able rename Window name.

Guideline Reference:
https://www.w3.org/WAI/WCAG21/Understanding/focus-order

Attachments:
Keyboard user is not able to access Window 1 Pop-up. (2).zip

Expected Behavior

Keyboard users should directly jump to 'Window 1' edit field when user open 'Window 1' pop-up using defined shortcut key.

Actual Behavior

Keyboard users are not able to access 'Window 1' pop-up when they open it using defined shortcut key.

Note Issue: Screen Reader users are not able to access 'Window 1' pop-up when they open it using defined shortcut key. Screen Reader is announcing 'Press F6 key to access...' but nothing happened on pressing F6.

Originally created by @ghost on GitHub (Dec 23, 2021). ### Windows Terminal version 1.12.3472.0 ### Windows build number 10.0.22504.1010 ### Other Software **Test Environment:** OS: Windows 11 Version Dev (OS Build 22504.1010) App: Windows Terminal Preview Screen Reader: Narrator Tool: Accessibility Insights for Windows Version 1.1.1741.1 ### Steps to reproduce Repro Steps: 1. Open Windows Terminal. 2. Open Settings page using 'Ctr+,'. 3. Navigate to Settings> Action> Add new button. 4. Add shortcut 'Ctrl + Shift +r' for 'Rename Window' actions. 5. Save Changes using 'Save' button. 6. Then press 'Ctrl + Shift + r' to open 'Window 1' pop-up. 7. Try to access 'Window 1' pop-up using keyboard. **User Experience:** As pop-up control are not accessible with Keyboard as a result, they will not able rename Window name. **Guideline Reference:** https://www.w3.org/WAI/WCAG21/Understanding/focus-order **Attachments:** [Keyboard user is not able to access Window 1 Pop-up. (2).zip](https://github.com/microsoft/terminal/files/7769231/Keyboard.user.is.not.able.to.access.Window.1.Pop-up.2.zip) ### Expected Behavior Keyboard users should directly jump to 'Window 1' edit field when user open 'Window 1' pop-up using defined shortcut key. ### Actual Behavior Keyboard users are not able to access 'Window 1' pop-up when they open it using defined shortcut key. **Note Issue:** Screen Reader users are not able to access 'Window 1' pop-up when they open it using defined shortcut key. Screen Reader is announcing 'Press F6 key to access...' but nothing happened on pressing F6.
claunia commented 2026-01-31 05:01:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 3, 2022):

We're already tracking this in #11322, which is blocked on the upstream https://github.com/microsoft/microsoft-ui-xaml/issues/1607 - there's no way for us to reliably focus a TeachingTip when it's opened.

@zadjii-msft commented on GitHub (Jan 3, 2022): We're already tracking this in #11322, which is blocked on the upstream https://github.com/microsoft/microsoft-ui-xaml/issues/1607 - there's no way for us to reliably focus a `TeachingTip` when it's opened.
claunia commented 2026-01-31 05:01:44 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 27, 2022):

@v-rpundir Just want to confirm. Since this is blocked by https://github.com/microsoft/microsoft-ui-xaml/issues/1607, you're marking this as a "tracking external" bug, correct?

@carlos-zamora commented on GitHub (Jan 27, 2022): @v-rpundir Just want to confirm. Since this is blocked by https://github.com/microsoft/microsoft-ui-xaml/issues/1607, you're marking this as a "tracking external" bug, correct?
claunia commented 2026-01-31 05:01:44 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 28, 2022):

Yes @carlos-zamora, we are tracking this external for now.

@ghost commented on GitHub (Jan 28, 2022): Yes @carlos-zamora, we are tracking this external for now.
claunia commented 2026-01-31 05:01:45 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Apr 19, 2022):

@v-rpundir This should now be fixed in https://github.com/microsoft/terminal/releases/tag/v1.13.10983.0

Can you confirm and close the bug please?

@carlos-zamora commented on GitHub (Apr 19, 2022): @v-rpundir This should now be fixed in https://github.com/microsoft/terminal/releases/tag/v1.13.10983.0 Can you confirm and close the bug please?
claunia commented 2026-01-31 05:01:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 20, 2022):

Closing as fixed now on Windows Terminal Preview Version: 1.13.10984.0

@ghost commented on GitHub (Apr 20, 2022): Closing as fixed now on Windows Terminal Preview Version: 1.13.10984.0
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 A11yCO A11ySev1 A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Priority-1 Product-Terminal Resolution-Fix-Available Tracking-External WindowsTerminal_Win32 zAskModeBug
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#16248
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?