A11y_.NET Core_WPF_EditExaminer_Color Contrast: The non-text color contrast between the keyboard focus and its background for "No exception! Warning Box" is 2.296:1 which is < 3:1

[v-inanda]

Description

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

GitHubTags:

#A11yMAS;#A11yTCS;#BM_.NET Core[WPF]_Win32_May23;#.NET Core;#A11ySev2;#A11yWCAG2.1;#WCAG1.4.11;#DesktopApp;#Win11;#Non-Text contrast;#Benchmark;#Closed;#Regressed:06-27-23;

Environment Details:

Application Name: .NET Core
.NET Version: .NET-SDK-8.0.100-preview.4.23260.5
WPF
Operating System: Windows 11 Enterprise 21H2

Reproduction Steps

1. Launch VS 2022 Preview
2. Navigate to Sample Applications and right click on the "Editing Examiner Demo" and click on build.
3. Then right click on Editing Examiner Demo then Click on Debug-->Start New Instance.
4. "Edit Examiner" screen should open.
5. TAB to "No exception! Warning Box".
6. Verify whether the non-text color contrast between the keyboard focus and its background for "No exception! Warning Box" is 2.296:1 which is less than 3:1 or not.

Expected behavior

The non-text color contrast between the keyboard focus and its background for "No exception! Warning Box" should be greater than equals to 3:1.

Actual behavior

The non-text color contrast between the keyboard focus and its background for "No exception! Warning Box" is 2.296:1 which is less than 3:1.

Regression?

No response

Known Workarounds

No response

Impact

Low vision users won't be able to recognize the focus if it fails the minimum non-text color contrast ratio of 3:1.

Configuration

No response

Other information

No response

[harshit7962]

Updated the code to fix the issue. The non-text color contrast between keyboard focus and its background for "no-exception! warning box" is 8.592:1 now. Kindly fetch the new code and test for the same.
Merged PR at: microsoft/WPF-Samples#490

[v-inanda]

@harshit7962 Verified the issue and it is still reproducing.

[v-inanda]

@harshit7962 Verified the issue and it is fixed. Hence, closing the bug.