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

[Startup: Launch Size]: Screen reader does not announce the sub text defined with 'Launch size' and 'Launch parameters' buttons. #18914

New Issue
Closed
opened 2026-01-31 06:28:12 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:28:12 +00:00
Owner
Copy Link

Originally created by @Shubham786786 on GitHub (Nov 16, 2022).

Originally assigned to: @carlos-zamora on GitHub.

Windows Terminal version

1.17.3052.0

Windows build number

Windows 11 Version 22H2 (OS Build 25206.1000)

Other Software

No response

Steps to reproduce

  1. Open Windows Terminal.
  2. Open 'Settings > Startup' window with 'Ctrl+,' keys.
  3. Turn on Narrator by 'Ctrl+Win+Enter' keys.
  4. Navigate to 'Launch size' button by tab key.
  5. Observe the issue.

User Experience: -
Screen reader users will have to navigate in scan mode to get the subtitle text information defined with the button's text.

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

Attachments:
Screen reader does not announce the sub text defined with 'Launch size' and 'Launch parameters' buttons..zip

Expected Behavior

Screen reader should announce the sub text defined with 'Launch size' and 'Launch parameters' buttons.

It should announce as 'Launch size group collapsed, the number of rows and columns displayed...'.
and also, when navigating in scan mode, focus should move to this sub text which is not happening currently.

Actual Behavior

Screen reader does not announce the sub text defined with 'Launch size' and 'Launch parameters' buttons. It announces as 'Launch size group collapsed'.

Observation:

  1. Issue also reproes with the NVDA screen reader.
  2. This happens throughout the application for similar buttons.
Originally created by @Shubham786786 on GitHub (Nov 16, 2022). Originally assigned to: @carlos-zamora on GitHub. ### Windows Terminal version 1.17.3052.0 ### Windows build number Windows 11 Version 22H2 (OS Build 25206.1000) ### Other Software _No response_ ### Steps to reproduce 1. Open Windows Terminal. 2. Open 'Settings > Startup' window with 'Ctrl+,' keys. 3. Turn on Narrator by 'Ctrl+Win+Enter' keys. 4. Navigate to 'Launch size' button by tab key. 5. Observe the issue. **User Experience: -** Screen reader users will have to navigate in scan mode to get the subtitle text information defined with the button's text. **Guideline Reference:** (https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html) **Attachments:** [Screen reader does not announce the sub text defined with 'Launch size' and 'Launch parameters' buttons..zip](https://github.com/microsoft/terminal/files/10020773/Screen.reader.does.not.announce.the.sub.text.defined.with.Launch.size.and.Launch.parameters.buttons.zip) ### Expected Behavior Screen reader should announce the sub text defined with 'Launch size' and 'Launch parameters' buttons. It should announce as '_Launch size group collapsed, the number of rows and columns displayed..._'. and also, when navigating in scan mode, focus should move to this sub text which is not happening currently. ### Actual Behavior Screen reader does not announce the sub text defined with 'Launch size' and 'Launch parameters' buttons. It announces as '_Launch size group collapsed_'. **Observation:** 1. Issue also reproes with the NVDA screen reader. 2. This happens throughout the application for similar buttons.
claunia commented 2026-01-31 06:28:17 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Dec 7, 2022):

@Shubham786786 I investigated this, and I'm a bit confused about my findings.

The control has the Full Description Automation Property defined like with the other controls in the settings UI. This was verified using Accessibility Insights. However, Narrator doesn't automatically read the full description as it does with other controls.

I don't think that means the bug is on us because we're setting the property. I also don't think that means the bug is on WinUI because the properties are being set and exposed properly.

Additionally, I verified that this does not repro using NVDA 2023.1.0.26827. You said above that the issue repros with NVDA. Which version are you using?

Since the properties are being set and exposed properly, and the bug does not occur in NVDA, I think this is actually a bug on Narrator and should be forwarded to them.

@carlos-zamora commented on GitHub (Dec 7, 2022): @Shubham786786 I investigated this, and I'm a bit confused about my findings. The control has the Full Description Automation Property defined like with the other controls in the settings UI. This was verified using Accessibility Insights. However, Narrator doesn't automatically read the full description as it does with other controls. I don't think that means the bug is on us because we're setting the property. I also don't think that means the bug is on WinUI because the properties are being set and exposed properly. Additionally, I verified that this does not repro using NVDA 2023.1.0.26827. You said above that the issue repros with NVDA. Which version are you using? Since the properties are being set and exposed properly, and the bug does not occur in NVDA, I think this is actually a bug on Narrator and should be forwarded to them.
claunia commented 2026-01-31 06:28:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 4, 2023):

@Shubham786786 @v-rpundir can either of you comment on this re: Carlos's findings?

@zadjii-msft commented on GitHub (Jan 4, 2023): @Shubham786786 @v-rpundir can either of you comment on this re: Carlos's findings?
claunia commented 2026-01-31 06:28:18 +00:00
Author
Owner
Copy Link

@Shubham786786 commented on GitHub (Jan 5, 2023):

I have verified the issue on the latest NVDA version, and it works fine, the issue is with Narrator, will forward the bug to Narrator team.

@Shubham786786 commented on GitHub (Jan 5, 2023): I have verified the issue on the latest NVDA version, and it works fine, the issue is with Narrator, will forward the bug to Narrator team.
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 A11ySev2 A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Needs-Tag-Fix Product-Terminal 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#18914
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?