starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Windows terminal>Setting>Profile>Appearance]:Color scheme names are truncated after applying resize settings. #23928

New Issue
Closed
opened 2026-01-31 08:56:26 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 08:56:26 +00:00
Owner
Copy Link

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

Originally assigned to: @carlos-zamora on GitHub.

Windows Terminal version

No response

Windows build number

No response

Other Software

No response

Steps to reproduce

Steps for applying Resize settings:
Settings>Display>Display Resolution (1680*1050)>Set scaling to 100%>Increase the text slider to 200% >Apply>Reopen the application.

Repro Steps:
1.Launch the Window terminal app.
2.Navigate to the 'New Open Tab' and select the 'Settings' menu item.
3.Settings pag will open and Follow all pre-requisites..
4.Navigate to Profile and select default.
5.Default page will open.
6.Navigate to Appearance and select the color sceheme
7.Observe the issue here.

User Experience:
Users who rely on larger text for readability (low vision, cognitive disabilities) cannot access full chat content after resizing. This creates barriers for communication and understanding, impacting usability and accessibility.

WCAG Reference Link:
https://www.w3.org/WAI/WCAG21/Understanding/resize-text

Attachements:
https://microsoftapc-my.sharepoint.com/:u:/g/personal/v-heparihar_microsoft_com/IQD-vqqzX3ErSKGC3CGntudiAc10F498rtUhr1QZvCYVUkY?e=1Imoer

Expected Behavior

The color scheme names should remain fully visible after resizing, or an accessible mechanism (e.g., tooltip on hover/focus or expandable view) should be provided to reveal the complete name.

Actual Behavior

After applying resize settings, color scheme names are truncated and not fully visible. No tooltip or alternative mechanism is available to reveal the complete name.

Originally created by @Saurabh220304 on GitHub (Dec 31, 2025). Originally assigned to: @carlos-zamora on GitHub. ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software _No response_ ### Steps to reproduce Steps for applying Resize settings: Settings>Display>Display Resolution (1680*1050)>Set scaling to 100%>Increase the text slider to 200% >Apply>Reopen the application. Repro Steps: 1.Launch the Window terminal app. 2.Navigate to the 'New Open Tab' and select the 'Settings' menu item. 3.Settings pag will open and Follow all pre-requisites.. 4.Navigate to Profile and select default. 5.Default page will open. 6.Navigate to Appearance and select the color sceheme 7.Observe the issue here. User Experience: Users who rely on larger text for readability (low vision, cognitive disabilities) cannot access full chat content after resizing. This creates barriers for communication and understanding, impacting usability and accessibility. WCAG Reference Link: https://www.w3.org/WAI/WCAG21/Understanding/resize-text Attachements: https://microsoftapc-my.sharepoint.com/:u:/g/personal/v-heparihar_microsoft_com/IQD-vqqzX3ErSKGC3CGntudiAc10F498rtUhr1QZvCYVUkY?e=1Imoer ### Expected Behavior The color scheme names should remain fully visible after resizing, or an accessible mechanism (e.g., tooltip on hover/focus or expandable view) should be provided to reveal the complete name. ### Actual Behavior After applying resize settings, color scheme names are truncated and not fully visible. No tooltip or alternative mechanism is available to reveal the complete name.
claunia commented 2026-01-31 08:56:29 +00:00
Author
Owner
Copy Link

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

Hi @Saurabh220304. What is the associated severities for this and the other accessibility bugs you filed?

As for a fix, I think just adding a tooltip should work. Should be pretty easy.

Images

Image Image
@carlos-zamora commented on GitHub (Jan 5, 2026): Hi @Saurabh220304. What is the associated severities for this and the other accessibility bugs you filed? As for a fix, I think just adding a tooltip should work. Should be pretty easy. ## Images <img width="1857" height="650" alt="Image" src="https://github.com/user-attachments/assets/f4c7af95-2ca2-4926-a4ca-2cfd248072ad" /> <img width="1857" height="650" alt="Image" src="https://github.com/user-attachments/assets/db9958fc-9e48-4c8d-9160-5938652652bc" />
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-Triage 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#23928
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?