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

[Settings]: At 400% Scaling, Text and Controls are not properly visible. #15252

New Issue
Open
opened 2026-01-31 04:32:55 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:32:55 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Sep 17, 2021).

Windows Terminal version (or Windows build number)

1.10.2383.0

Other Software

Test Environment:
OS: Windows 11 Version 21H2 (OS Build 22000.168)
Screen Reader: Narrator
Tool: Accessibility Insight for Windows

Steps to reproduce

Prerequisites:

  1. Open Settings app using 'Windows + i' Key.
  2. Navigate to System and activate it.
  3. Then Set Display Resolution to 1280 x 1024.
  4. Then Navigate to System>Display> Scale
  5. Inside Scale page, Set Custom Scaling at 400 and Sign out

Repro Steps:
Open Windows Terminal.
Open Settings page using "Ctrl + ',' ".
Verify that whether user can use app properly.

User Experience:
Low vision user will be impacted here as content is not properly visible as result user will find difficulty in using the app.

Guideline Reference:
https://www.w3.org/WAI/WCAG21/Understanding/reflow

Attachments:
At 400% Scaling, Text and Controls are not properly visible..zip

Expected Behavior

At 400% Scaling, Text and Controls should be properly visible.

Actual Behavior

At 400% Scaling, Text and Controls are not properly visible. User have move up and down to fully see and read Control and Text name.

Originally created by @ghost on GitHub (Sep 17, 2021). ### Windows Terminal version (or Windows build number) 1.10.2383.0 ### Other Software **Test Environment:** OS: Windows 11 Version 21H2 (OS Build 22000.168) Screen Reader: Narrator Tool: Accessibility Insight for Windows ### Steps to reproduce **Prerequisites:** 1. Open Settings app using 'Windows + i' Key. 2. Navigate to System and activate it. 3. Then Set Display Resolution to 1280 x 1024. 4. Then Navigate to System>Display> Scale 5. Inside Scale page, Set Custom Scaling at 400 and Sign out **Repro Steps:** Open Windows Terminal. Open Settings page using "Ctrl + ',' ". Verify that whether user can use app properly. **User Experience:** Low vision user will be impacted here as content is not properly visible as result user will find difficulty in using the app. **Guideline Reference:** https://www.w3.org/WAI/WCAG21/Understanding/reflow **Attachments:** [At 400% Scaling, Text and Controls are not properly visible..zip](https://github.com/microsoft/terminal/files/7185544/At.400.Scaling.Text.and.Controls.are.not.properly.visible.zip) ### Expected Behavior At 400% Scaling, Text and Controls should be properly visible. ### Actual Behavior At 400% Scaling, Text and Controls are not properly visible. User have move up and down to fully see and read Control and Text name.
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 A11yTTValidated A11yWCAG Area-Accessibility HCL-E+D HCL-WindowsTerminal Issue-Bug Needs-Tag-Fix 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#15252
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?