starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

{Freeway-Bug} [Windows Terminal - Settings]: Correct role as link should be defined for 'Open JSON file' control. #23130

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

Originally created by @Saurabh220304 on GitHub (Apr 8, 2025).

Windows Terminal version

1.23.10732.0

Windows build number

27823.1000

Other Software

Test Environment:
OS: Windows 11 Version Dev (OS Build 27823.1000)
App: Windows Terminal Preview
Screen Reader: Narrator

Steps to reproduce

Repro steps:

  1. Open the 'windows terminal' application.
  2. Turn on Narrator by pressing 'Ctrl + Windows + Enter' keys.
  3. Navigate to the 'Settings' page.
  4. Now navigate to the 'Open JSON file' control by tab key and activate it.
  5. Observe the behavior when opening the file in the selected editor (e.g., Notepad).
  6. Close or minimize the editor and observe the state of the 'Open JSON file' control.

User experience:
Users may be confused by the current role assignment, as a list item suggests selection rather than activation. This misinterpretation can cause uncertainty when interacting with the control, leading to difficulty understanding its intended function. Defining the correct role as a link would improve accessibility and usability.

Attachment:
Correct role as link should be defined for 'Open JSON file' control..zip

Expected Behavior

The 'Open JSON file' control should be assigned the correct role as a link instead of a list item. Additionally, an 'Open in new window' sign or appropriate information should be associated with it to ensure clarity for users. When activated, the control should behave like a proper link and not remain visually selected when the editor is closed or minimized.

Actual Behavior

The 'Open JSON file' control is currently defined with the role of a list item instead of a link. Upon activation, the JSON file opens in the selected editor (e.g., Notepad), but the control remains visually selected even after the editor is closed or minimized. This behavior creates confusion for users, as the control does not behave as a typical link.

Originally created by @Saurabh220304 on GitHub (Apr 8, 2025). ### Windows Terminal version 1.23.10732.0 ### Windows build number 27823.1000 ### Other Software **Test Environment:** OS: Windows 11 Version Dev (OS Build 27823.1000) App: Windows Terminal Preview Screen Reader: Narrator ### Steps to reproduce **Repro steps:** 1. Open the 'windows terminal' application. 2. Turn on Narrator by pressing 'Ctrl + Windows + Enter' keys. 3. Navigate to the 'Settings' page. 4. Now navigate to the 'Open JSON file' control by tab key and activate it. 5. Observe the behavior when opening the file in the selected editor (e.g., Notepad). 6. Close or minimize the editor and observe the state of the 'Open JSON file' control. **User experience:** Users may be confused by the current role assignment, as a list item suggests selection rather than activation. This misinterpretation can cause uncertainty when interacting with the control, leading to difficulty understanding its intended function. Defining the correct role as a link would improve accessibility and usability. **Attachment:** [Correct role as link should be defined for 'Open JSON file' control..zip](https://github.com/user-attachments/files/19648119/Correct.role.as.link.should.be.defined.for.Open.JSON.file.control.zip) ### Expected Behavior The 'Open JSON file' control should be assigned the correct role as a link instead of a list item. Additionally, an 'Open in new window' sign or appropriate information should be associated with it to ensure clarity for users. When activated, the control should behave like a proper link and not remain visually selected when the editor is closed or minimized. ### Actual Behavior The 'Open JSON file' control is currently defined with the role of a list item instead of a link. Upon activation, the JSON file opens in the selected editor (e.g., Notepad), but the control remains visually selected even after the editor is closed or minimized. This behavior creates confusion for users, as the control does not behave as a typical link.
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 A11yUsable 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#23130
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?