A11y_Windows Terminal_About_Color Contrast: Links present in the "About" pop up window and the text to the back ground color in the "ok" button are not meeting the color contrast ratio 4.5:1

[SpandanaPaladi]

#A11y_WindowsTerminal; #WindowsTerminal; #A11yMAS; #A11yTCS; #DesktopApp; #Win10; #C+E-H; #ColorContrast; #A11ySev2; #NonBenchMark; #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 "Dropdown" control and press enter or use "Ctrl + Shift + Space"
5. Tab till "About" and press enter
6. Verify whether the links and the text to the back ground color in the "OK" button are meeting the color contrast ratio 4.5:1 or not

Actual Result:
The links present in the "About" pop up window and the text to the back ground color in the "OK" button are not meeting the color contrast ratio 4.5:1​

Expected Result:​
The links present in the "About" pop up window and the text to the back ground color in the "OK" button should meet the color contrast ratio 4.5:1
​
User Impact:​
Low vision users will face difficulty in viewing the content if the Color Contrast ratio fails to meet 4.5:1 ratio for links and text to the back ground color in the "OK" button

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

[mdtauk]

Isn't this down to the choice of Accent colour in the system?

[carlos-zamora]

We just use the built-in ContentDialog from the WinUI Theme Dictionary. Submitted the following issue on the WinUI repo:
microsoft/microsoft-ui-xaml#2354

[Amulya-95]

Regressed the bug in latest environment. The issue is resolved, controls have color contrast ratio equal to 4.5:1. Hence closing this bug.
Please find the attachments for reference.

Attachments: