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

[Windows terminal>Settings>Terminal chat]: Visual labels are not programmatically associated with edit fields; screen reader announces only “Edit” #23924

New Issue
Closed
opened 2026-01-31 08:56:20 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 08:56:20 +00:00
Owner
Copy Link

Originally created by @Saurabh220304 on GitHub (Dec 30, 2025).

Originally assigned to: @PankajBhojwani on GitHub.

Windows Terminal version

1.25.3571.0

Windows build number

Windows 11 Version 26H1 (OS Build 28000.1340)

Other Software

No response

Steps to reproduce

Repro Steps:
1.Launch the Window terminal app.
2.Navigate to the 'New Open Tab' and select the 'Settings' menu item.
3.Settings page will open.
4.Now navigate to 'Terminal chat' and select 'it'.
5.Terminal chat page will open.
6.Now turn on the narrator using 'CTRL+Win+Enter' keys.
7.Now navigate to 'Edit' fields present on the page.
8.Observe the issue here.

User Experience:
Screen reader users are unable to identify the purpose of form fields, which can lead to confusion and a higher rate of form completion errors. This does not meet fundamental accessibility standards for forms.

WCAG Reference Link:
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value

Attachements:
https://microsoftapc-my.sharepoint.com/:u:/g/personal/v-heparihar_microsoft_com/IQAUrnj56gCAQZZkNuo26uuTAQ4RhZZLcXkiXI23ju8U5Qw?e=bYFpgJ

Expected Behavior

Visual label or name should be programmatically bound to its corresponding edit field.

Actual Behavior

All visual labels for edit fields are not programmatically associated with their respective input controls.
When navigating the form using a screen reader, each input field is announced only as “Edit” with no label or context.
This makes it difficult for screen reader users to understand the purpose of each edit field.

Originally created by @Saurabh220304 on GitHub (Dec 30, 2025). Originally assigned to: @PankajBhojwani on GitHub. ### Windows Terminal version 1.25.3571.0 ### Windows build number Windows 11 Version 26H1 (OS Build 28000.1340) ### Other Software _No response_ ### Steps to reproduce Repro Steps: 1.Launch the Window terminal app. 2.Navigate to the 'New Open Tab' and select the 'Settings' menu item. 3.Settings page will open. 4.Now navigate to 'Terminal chat' and select 'it'. 5.Terminal chat page will open. 6.Now turn on the narrator using 'CTRL+Win+Enter' keys. 7.Now navigate to 'Edit' fields present on the page. 8.Observe the issue here. User Experience: Screen reader users are unable to identify the purpose of form fields, which can lead to confusion and a higher rate of form completion errors. This does not meet fundamental accessibility standards for forms. WCAG Reference Link: https://www.w3.org/WAI/WCAG21/Understanding/name-role-value Attachements: https://microsoftapc-my.sharepoint.com/:u:/g/personal/v-heparihar_microsoft_com/IQAUrnj56gCAQZZkNuo26uuTAQ4RhZZLcXkiXI23ju8U5Qw?e=bYFpgJ ### Expected Behavior Visual label or name should be programmatically bound to its corresponding edit field. ### Actual Behavior All visual labels for edit fields are not programmatically associated with their respective input controls. When navigating the form using a screen reader, each input field is announced only as “Edit” with no label or context. This makes it difficult for screen reader users to understand the purpose of each edit field.
claunia commented 2026-01-31 08:56:22 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 6, 2026):

Looks like we need to add an AutomationProperties.Name to these text fields in the Terminal Chat page.

Image

https://github.com/user-attachments/assets/8dd83e56-4530-4cd7-908d-842f1895564e

@carlos-zamora commented on GitHub (Jan 6, 2026): Looks like we need to add an `AutomationProperties.Name` to these text fields in the Terminal Chat page. <img width="1913" height="519" alt="Image" src="https://github.com/user-attachments/assets/d9546b30-4b5b-43ef-be99-cd071cef01b3" /> https://github.com/user-attachments/assets/8dd83e56-4530-4cd7-908d-842f1895564e
claunia commented 2026-01-31 08:56:22 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jan 14, 2026):

Fixed by #19717

@carlos-zamora commented on GitHub (Jan 14, 2026): Fixed by #19717
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#23924
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?