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

[Terminal >Actions]: Screen Reader users are not able to know the purpose of Actions List inside Actions tab page. #16290

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

Originally created by @ghost on GitHub (Dec 28, 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

Steps to reproduce

Repro Steps:

  1. Open Windows Terminal.
  2. Open Settings page using 'Ctr+,'.
  3. Open Narrator using 'Win + Ctrl + Enter' keys.
  4. Activate 'Actions' tab and then navigate to actions list using tab/arrow keys and observe the issue.

User Experience:
Screen Reader users UX will not be good as they are not able to know the purpose of list item when they navigate to them.

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

Attachments:
Screen Reader users are not able to know the purpose of Actions List inside Actions tab page..zip

Expected Behavior

Screen Reader users should be able to know the purpose of Actions List inside Actions tab page.
i.e. When user first time jumps to 'Actions' list item control, Screen Reader should announce something like this 'Actions List item, Use these actions to perform available functionality inside Terminal Text Area....'

Actual Behavior

Screen Reader users are not able to know the purpose of Actions List inside Actions tab page.

Observation: Same issue repro with NVDA and JAWS Screen Reader.

Originally created by @ghost on GitHub (Dec 28, 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 ### Steps to reproduce **Repro Steps:** 1. Open Windows Terminal. 2. Open Settings page using 'Ctr+,'. 3. Open Narrator using 'Win + Ctrl + Enter' keys. 4. Activate 'Actions' tab and then navigate to actions list using tab/arrow keys and observe the issue. **User Experience:** Screen Reader users UX will not be good as they are not able to know the purpose of list item when they navigate to them. **Guideline Reference:** https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships **Attachments:** [Screen Reader users are not able to know the purpose of Actions List inside Actions tab page..zip](https://github.com/microsoft/terminal/files/7783331/Screen.Reader.users.are.not.able.to.know.the.purpose.of.Actions.List.inside.Actions.tab.page.zip) ### Expected Behavior Screen Reader users should be able to know the purpose of Actions List inside Actions tab page. i.e. When user first time jumps to 'Actions' list item control, Screen Reader should announce something like this 'Actions List item, Use these actions to perform available functionality inside Terminal Text Area....' ### Actual Behavior Screen Reader users are not able to know the purpose of Actions List inside Actions tab page. **Observation:** Same issue repro with NVDA and JAWS Screen Reader.
claunia commented 2026-01-31 05:02:57 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 18, 2022):

"Actions List item, Use these actions to perform available functionality inside Terminal Text Area...."

Having trouble figuring out how to do this. Here's a few notes:

  • add an AutomationProperties.Name to the ListView:
    • Name is read when focus moves inside the list. So if it's set to "Actions", moving to the first item says "Actions ".
    • Issue: it's weird that Narrator doesn't say the control type "list". NVDA does so I'll just assume this part is ok. Otherwise, if I name it "Actions list", NVDA will say "Actions list list"
  • how do you get it to say "Use these actions..."?
    • Help text on the ListView isn't automatically read.
    • Help text on the action seems like the wrong place.
    • It should be a property on the ListView, but I don't know which one.

I (or someone) will circle back around to fix this bug.

@carlos-zamora commented on GitHub (Jul 18, 2022): > "Actions List item, Use these actions to perform available functionality inside Terminal Text Area...." Having trouble figuring out how to do this. Here's a few notes: - add an `AutomationProperties.Name` to the `ListView`: - Name is read when focus moves inside the list. So if it's set to "Actions", moving to the first item says "Actions <name of action> <key chord>". - Issue: it's weird that Narrator doesn't say the control type "list". NVDA does so I'll just assume this part is ok. Otherwise, if I name it "Actions list", NVDA will say "Actions list list" - how do you get it to say "Use these actions..."? - Help text on the `ListView` isn't automatically read. - Help text on the action seems like the wrong place. - It should be a property on the `ListView`, but I don't know which one. I (or someone) will circle back around to fix this bug.
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 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#16290
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?