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

[Settings> Open/Close Navigation]: Neither name is descriptive nor changing name is announced by Screen reader for 'Open/Close Navigation' button. #15241

New Issue
Closed
opened 2026-01-31 04:32:33 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 04:32:33 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Sep 16, 2021).

Windows Terminal version (or Windows build number)

1.10.2383.0

Other Software

Test Environment:
OS: Windows 11 Version 21H2 (OS Build 22000.168)
Screen Reader: Narrator
Tool: Accessibility Insight for Windows

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using "Ctrl + ',' ".
  3. Open Narrator using 'Win + Ctrl + Enter' key.
  4. Navigate to 'Open/Close Navigation', Observe the issue.
  5. Then activate 'Open/Close Navigation' button and observe the issue.

User Experience:
Screen Reader user are impacted here as they will not be able to know whether navigation is open or close as changing name is not announced to them in addition to that name of the control is confusing when compared to visual view.

Guideline Reference:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships

Attachments:
Neither name is descriptive nor changing name.zip

Expected Behavior

Screen Reader should announce 'Expand/Collapse Navigation View' as name for control and when user activate it Screen Reader should announce the changing name of the button.

Actual Behavior

Neither name is descriptive nor changing name is announced by Screen reader for 'Open/Close Navigation' button. Screen Reader is announcing 'Open/Close Navigation' which is incorrect and When user activate 'Open/Close navigation' button Screen Reader remain Silent.

Observation: Same issue repro with NVDA Screen Reader.

Originally created by @ghost on GitHub (Sep 16, 2021). ### Windows Terminal version (or Windows build number) 1.10.2383.0 ### Other Software **Test Environment:** OS: Windows 11 Version 21H2 (OS Build 22000.168) Screen Reader: Narrator Tool: Accessibility Insight for Windows ### Steps to reproduce **Repro Steps:** 1. Open Windows Terminal. 2. Open Settings page using "Ctrl + ',' ". 3. Open Narrator using 'Win + Ctrl + Enter' key. 3. Navigate to 'Open/Close Navigation', Observe the issue. 4. Then activate 'Open/Close Navigation' button and observe the issue. **User Experience:** Screen Reader user are impacted here as they will not be able to know whether navigation is open or close as changing name is not announced to them in addition to that name of the control is confusing when compared to visual view. **Guideline Reference:** https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships **Attachments:** [Neither name is descriptive nor changing name.zip](https://github.com/microsoft/terminal/files/7177269/Neither.name.is.descriptive.nor.changing.name.zip) ### Expected Behavior Screen Reader should announce 'Expand/Collapse Navigation View' as name for control and when user activate it Screen Reader should announce the changing name of the button. ### Actual Behavior Neither name is descriptive nor changing name is announced by Screen reader for 'Open/Close Navigation' button. Screen Reader is announcing 'Open/Close Navigation' which is incorrect and When user activate 'Open/Close navigation' button Screen Reader remain Silent. Observation: Same issue repro with NVDA Screen Reader.
claunia commented 2026-01-31 04:32:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 16, 2021):

This looks like the upstream issue https://github.com/microsoft/microsoft-ui-xaml/issues/3494, which they have accepted into their backlog.

@DHowett commented on GitHub (Sep 16, 2021): This looks like the upstream issue https://github.com/microsoft/microsoft-ui-xaml/issues/3494, which they have accepted into their backlog.
claunia commented 2026-01-31 04:32:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 21, 2021):

We are tracking this bug here https://github.com/microsoft/microsoft-ui-xaml/issues/3494 so closing this bug as External

@ghost commented on GitHub (Sep 21, 2021): We are tracking this bug here https://github.com/microsoft/microsoft-ui-xaml/issues/3494 so closing this bug as External
claunia commented 2026-01-31 04:32:36 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 3, 2022):

Issue is still repro on below environment.

Test Environment:
OS: Windows 11 Version 21H2 (OS Build 22598.200)
Application: Window Terminal Preview
App Version: 1.13.10984.0
Screen Reader: Narrator

@ghost commented on GitHub (May 3, 2022): Issue is still repro on below environment. **Test Environment:** **OS:** Windows 11 Version 21H2 (OS Build 22598.200) **Application:** Window Terminal Preview **App Version:** 1.13.10984.0 **Screen Reader:** Narrator
claunia commented 2026-01-31 04:32:36 +00:00
Author
Owner
Copy Link

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

@v-rpundir
I'm a bit confused here. The bug is caused by https://github.com/microsoft/microsoft-ui-xaml/issues/3494.
Since the XAML team has accepted the bug, can't we close this bug?

@carlos-zamora commented on GitHub (Oct 19, 2022): @v-rpundir I'm a bit confused here. The bug is caused by https://github.com/microsoft/microsoft-ui-xaml/issues/3494. Since the XAML team has accepted the bug, can't we close this bug?
claunia commented 2026-01-31 04:32:36 +00:00
Author
Owner
Copy Link

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

@carlos-zamora Here is summary of our current External process we follow in this case:

  1. Your team can Resolve/Close the bug if the bug has external dependency by mentioning the External team's name or contact.
  2. Then we will contact the external testing team to get Tracking bug ID (we prefer VSO Tracking ID instead of GitHub as it has Proper Tracking and External team should have to fix it to maintain its Product Compliance) which is XAML in this case.
  3. After we get Tracking ID, we will mention it in this bug.
  4. When External bug gets closed with A11yTTValidated, we will check this bug and in case it repro's we will reactivate/reopen it and if external bug closed with reason By Design/Won't Fix, we will close this bug.

A11yTTValidated: When the bug has this tag it means it is closed now from Testing team and no further action is needed in the bug so even if the Product team close the bug for their reference, it will not be considered as closed from testing team side.

I hope this helps in clearing the bug external Process.

Thanks :):

@ghost commented on GitHub (Oct 20, 2022): @carlos-zamora Here is summary of our current External process we follow in this case: 1. Your team can Resolve/Close the bug if the bug has external dependency by mentioning the External team's name or contact. 2. Then we will contact the external testing team to get Tracking bug ID (we prefer VSO Tracking ID instead of GitHub as it has Proper Tracking and External team should have to fix it to maintain its Product Compliance) which is XAML in this case. 3. After we get Tracking ID, we will mention it in this bug. 4. When External bug gets closed with A11yTTValidated, we will check this bug and in case it repro's we will reactivate/reopen it and if external bug closed with reason By Design/Won't Fix, we will close this bug. A11yTTValidated: When the bug has this tag it means it is closed now from Testing team and no further action is needed in the bug so even if the Product team close the bug for their reference, it will not be considered as closed from testing team side. I hope this helps in clearing the bug external Process. Thanks :):
claunia commented 2026-01-31 04:32:37 +00:00
Author
Owner
Copy Link

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

As now XAML team is tracking bugs in VSO we will get VSO tracking ID for this bug.

@ghost commented on GitHub (Oct 20, 2022): As now XAML team is tracking bugs in VSO we will get VSO tracking ID for this bug.
claunia commented 2026-01-31 04:32:37 +00:00
Author
Owner
Copy Link

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

XAML VSO Tracking ID: Bug 41570653: [WinUI Accessibility-> Left Navigation Pane]: No success information announced by screen reader, when user invokes open/close navigation button.

@ghost commented on GitHub (Oct 20, 2022): XAML VSO Tracking ID: [Bug 41570653](https://microsoft.visualstudio.com/DefaultCollection/OS/_workitems/edit/41570653): [WinUI Accessibility-> Left Navigation Pane]: No success information announced by screen reader, when user invokes open/close navigation button.
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 A11ySev3 A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Priority-3 Product-Terminal Resolution-External Tracking-External WindowsTerminal_Win32
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#15241
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?