[Adaptive Cards> Designer> Card Structure]: Ensures the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds.

[vagpt]

Target Platforms

Other

SDK Version

1.6

Application Name

Adaptive Cards

Problem Description

Test environment:
URL: https://adaptivecards.io/designer/
OS Version: 23H2 (OS Build 25931.1000)
Browser Version: Edge Dev 118.0.2060.1
Tool: Accessibility Insight For Web

Repro Steps:

1. Open the above URL on the EDGE Dev Browser.
2. Run the accessibility insight for web tool and observe the issue.

Actual Result:
The luminosity ratio for the 'Creator' text is '3.392.1' which is less than 4.5:1.

Expected Result:
Color Contrast ratio for the 'Creator Name' text should be equal to or greater than 4.5:1.

Element path:
.selected.acd-tree-item > .acd-tree-item-text > .acd-tree-item-additionalText

Snippet:
[${creator.name}]

How to fix:
Fix any of the following:
Element has insufficient color contrast of 3.39 (foreground color: #757575, background color: #bce2ff, font size: 10.5pt (14px), font weight: normal). Expected contrast ratio of 4.5:1

User Impact:
It will impact the low vison user as they will not be able to see properly the text if the contrast ratio is less than 4.5:1.

WCAG Guideline:
https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html

"Have feedback to share on Bugs ? Please help fill Trusted Tester Bug Feedback (office.com) “.

Screenshots

Card JSON

NA

Sample Code Language

No response

Sample Code

No response

[vagpt]

Hi @jwoo-msft ,

As this issue is still repro, and this bug is marked as closed so could you please let us know whether your team will work on this or not also it would be great if please provide us reason for marking this as 'Won't Fix' so that in future we can avoid to logging this type of issue.

[vagpt]

Hi @jwoo-msft ,

As this issue is still repro, and this bug is marked as closed so could you please let us know whether your team will work on this or not also it would be great if please provide us reason for marking this as 'Won't Fix' so that in future we can avoide to logging this type of issue.