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

A11y_Windows Terminal_PowerShell_Screen reader: Single focus is provided to both 'Opening New Tab' and 'Dropdown' control and screen reader is reading as Split button which does not give much information about the control #7503

New Issue
Open
opened 2026-01-31 01:05:33 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 01:05:33 +00:00
Owner
Copy Link

Originally created by @Amulya-95 on GitHub (Apr 20, 2020).

GitHubTags: #A11y_WindowsTerminal; #WindowsTerminal; #A11yTCS; #A11yMAS; #Win10; #DesktopApp; #ScreenReader; #Narrator; #NVDA; #MAS1.3.1; #C+E-H; #A11ySev2;

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier

Environment Details:
Windows Terminal
Version: 0.10.781.0
OS: Windows 10 (Version 1909, Build: 18363.778)

Repro Steps:
1.Turn on the screen reader
2.Hit the URL "aka.ms/terminal" and install "Windows terminal (Preview)" application
3.Open "Windows terminal (Preview)" application
4.Tab to '+' control present beside the tab
5.Verify whether every control is getting individual focus and screen reader is reading it as 'Open New tab' button and 'dropdown'

Actual Result:
Single focus is provided to both 'Opening New Tab' and 'Dropdown' control and screen reader is reading as Split button which does not give much information about the control

Expected Result:
Different focus should be provided to the '+' symbol (Open New Tab) and 'Dropdown' and screen reader should read it as 'Open New Tab button' when focus is on '+' control and 'Dropdown' when focus is on dropdown control.

User Impact:
Visually disabled users will find difficulty, if the focus single focus is provided to two control and screen reader is reading as split button, user will get confused.

MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}

Attachment:
Bug 5423_Two controls getting single focus and screen reader is not clear information about the controls.pptx

Bug 5423_NVDA_Reading it as Split button

Originally created by @Amulya-95 on GitHub (Apr 20, 2020). GitHubTags: #A11y_WindowsTerminal; #WindowsTerminal; #A11yTCS; #A11yMAS; #Win10; #DesktopApp; #ScreenReader; #Narrator; #NVDA; #MAS1.3.1; #C+E-H; #A11ySev2; [Check out Accessibility Insights!](https://nam06.safelinks.protection.outlook.com/?url=https://accessibilityinsights.io/&data=02%7c01%7cv-tagott%40microsoft.com%7cb67b2c4b646d4f9561a208d6f4b5c39b%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636965458847261333&sdata=PJMiKjb64uwhBN98LZpctnBiAVeOvw%2BLBrnxBtrjl2M%3D&reserved=0) - Identify accessibility bugs before check-in and make bug fixing faster and easier **Environment Details:** Windows Terminal Version: 0.10.781.0 OS: Windows 10 (Version 1909, Build: 18363.778) **Repro Steps:** 1.Turn on the screen reader 2.Hit the URL "aka.ms/terminal" and install "Windows terminal (Preview)" application 3.Open "Windows terminal (Preview)" application 4.Tab to '+' control present beside the tab 5.Verify whether every control is getting individual focus and screen reader is reading it as 'Open New tab' button and 'dropdown' **Actual Result:** Single focus is provided to both 'Opening New Tab' and 'Dropdown' control and screen reader is reading as Split button which does not give much information about the control **Expected Result:** Different focus should be provided to the '+' symbol (Open New Tab) and 'Dropdown' and screen reader should read it as 'Open New Tab button' when focus is on '+' control and 'Dropdown' when focus is on dropdown control. **User Impact:** Visually disabled users will find difficulty, if the focus single focus is provided to two control and screen reader is reading as split button, user will get confused. **MAS Reference:** https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4} **Attachment:** [Bug 5423_Two controls getting single focus and screen reader is not clear information about the controls.pptx](https://github.com/microsoft/terminal/files/4503673/Bug.5423_Two.controls.getting.single.focus.and.screen.reader.is.not.clear.information.about.the.controls.pptx) ![Bug 5423_NVDA_Reading it as Split button](https://user-images.githubusercontent.com/51435266/79757617-f8df9c00-8339-11ea-8c03-3d14e607072e.png)
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-Accessibility Area-UserInterface Issue-Bug Needs-Tag-Fix 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#7503
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?