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

A11y_Windows Terminal_Open any Application_Color Contrast: While Opening any application which is not existing then the error message will be displayed and it is not meeting the color contrast ratio 4.5:1 #7456

New Issue
Closed
opened 2026-01-31 01:04:30 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 01:04:30 +00:00
Owner
Copy Link

Originally created by @SpandanaPaladi on GitHub (Apr 17, 2020).

Originally assigned to: @carlos-zamora on GitHub.

#A11y_WindowsTerminal; #WindowsTerminal; #A11yMAS; #A11yTCS; #DesktopApp; #Win10; #C+E-H; #ColorContrast; #A11ySev1; #BenchMark; #MAS1.4.3

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier

Environment Details:
Version: 0.10.781.0

Repro steps:

  1. Hit the URL ""aka.ms/terminal"" and install ""Windows terminal (Preview)"" application
  2. Open ""Windows terminal (Preview)"" application
  3. Open the "Accessibility insights" tool to check color contrast ratio
  4. Tab to ""Windows Powershell"" tab
  5. Type any application name which is not existing(displays an error message)
  6. Verify whether the color contrast ratio for the error message displayed is meeting 4.5:1 contrast ratio

Actual Result:​
The "Error" message which is displayed is not meeting 4.5:1 contrast ratio

Expected Result:​
The "Error" message which is displayed should meet 4.5:1 contrast ratio
​
User Impact:​
Low vision users will face difficulty in viewing the text if the text Error message fails to meet the contrast ratio 4,.5:1

MAS Reference:​
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={a73546c7-765f-489c-b18f-afb659fe99e6}

Bug_color contrast fails for error message

Originally created by @SpandanaPaladi on GitHub (Apr 17, 2020). Originally assigned to: @carlos-zamora on GitHub. #A11y_WindowsTerminal; #WindowsTerminal; #A11yMAS; #A11yTCS; #DesktopApp; #Win10; #C+E-H; #ColorContrast; #A11ySev1; #BenchMark; #MAS1.4.3 [Check out Accessibility Insights!](https://nam06.safelinks.protection.outlook.com/?url=https://accessibilityinsights.io/&data=02%7c01%7cv-shcha1%40microsoft.com%7cb67b2c4b646d4f9561a208d6f4b5c39b%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636965458847087032&sdata=uWx6cTEfazn%2BoCV3cL1iYB4KN%2BuXQ/MTlmOVec%2BZgKc%3D&reserved=0) - Identify accessibility bugs before check-in and make bug fixing faster and easier **Environment Details:** Version: 0.10.781.0 **Repro steps:** 1. Hit the URL ""aka.ms/terminal"" and install ""Windows terminal (Preview)"" application 2. Open ""Windows terminal (Preview)"" application 3. Open the "Accessibility insights" tool to check color contrast ratio 4. Tab to ""Windows Powershell"" tab 5. Type any application name which is not existing(displays an error message) 6. Verify whether the color contrast ratio for the error message displayed is meeting 4.5:1 contrast ratio **Actual Result:​** The "Error" message which is displayed is not meeting 4.5:1 contrast ratio **Expected Result:​** The "Error" message which is displayed should meet 4.5:1 contrast ratio ​ **User Impact:​** Low vision users will face difficulty in viewing the text if the text Error message fails to meet the contrast ratio 4,.5:1 **MAS Reference:​** https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={a73546c7-765f-489c-b18f-afb659fe99e6} ![Bug_color contrast fails for error message](https://user-images.githubusercontent.com/63839131/79562628-03472f00-80c9-11ea-85ce-08ab34d81031.png)
claunia commented 2026-01-31 01:04:31 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Apr 20, 2020):

Moving this one over to v1.0 milestone because we discussed offline that changing the color scheme to Campbell should suffice. (assuming Campbell provides a good color contrast)

@carlos-zamora commented on GitHub (Apr 20, 2020): Moving this one over to v1.0 milestone because we discussed offline that changing the color scheme to Campbell should suffice. (assuming Campbell provides a good color contrast)
claunia commented 2026-01-31 01:04:32 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Apr 22, 2020):

#5432 is included in 0.11. Updating tag.

@carlos-zamora commented on GitHub (Apr 22, 2020): #5432 is included in 0.11. Updating tag.
claunia commented 2026-01-31 01:04:32 +00:00
Author
Owner
Copy Link

@Amulya-95 commented on GitHub (May 12, 2020):

Regressed the bug in latest environment. The issue is resolved, contrast ratio for "Error" message is greater than 4.5:1 ratio. Hence closing this bug.

Fixed Bug 5393_Color contrast ratio passes for error message

@Amulya-95 commented on GitHub (May 12, 2020): Regressed the bug in latest environment. The issue is resolved, contrast ratio for "Error" message is greater than 4.5:1 ratio. Hence closing this bug. ![Fixed Bug 5393_Color contrast ratio passes for error message](https://user-images.githubusercontent.com/51435266/81691327-41423380-947a-11ea-8b90-a274c2c8a09d.png)
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 Area-Accessibility Issue-Task Product-Terminal Resolution-Fix-Available
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#7456
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?