[Usable - Bot Framework Web Chat - Card Breakfast]: In High contrast (Aquatic and Night sky) themes, ‘Play’, ‘Mute / Unmute’, ‘more options’ buttons present on the audio are not properly visible.

[KattaBhargav]

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

User Experience:

Color sensitive users who use high contrast themes will be impacted as they get confused and consider it as an enabled element and the user's perception and experience will be impacted.

Note:

User credentials should NOT be included in the bug.

Prerequisite:

Turn on High Contrast themes. Path: System Settings->Search and select 'Contrast themes'.

What browsers and screen readers do this issue affect?

Windows: Edge with Windows Narrator

Are there any code-based customization done to Web Chat?

No, I am using Web Chat without any customizations except "styleOptions".

What version of Web Chat are you using?

Latest production

Which area does this issue affect?

Others or unrelated, Suggested action

What is the public URL for the website?

https://compulim.github.io/webchat-loader/

How to reproduce the issue?

1. Open URL: https://compulim.github.io/webchat-loader/ and sign in using valid credentials.
2. Navigate to web chat page and select 4.18.1-main.20240927.ea7a875 (30/9/2024) version and then select mockBot link under present label and then select open web chat in new window link at bottom.
3. Navigate to white label experience chat page and type Card Breakfast word in type your message text box.
4. Navigate to the results.
5. Verify the issues.

What do you expect?

In High contrast (Aquatic and Night sky) themes, ‘Play’, ‘Mute / Unmute’, ‘more options’ buttons present on the audio should be properly visible.

What actually happened?

In High contrast (Aquatic and Night sky) themes, ‘Play’, ‘Mute / Unmute’, ‘more options’ buttons present on the audio are not properly visible.
Observation: This issue does not repro in Desert and Dusk modes

Do you have any screenshots or recordings to repro the issue?

Did you find any DOM elements that might have caused the issue?

No response

MAS reference

No response

WCAG reference

No response

WAI-ARIA reference

No response

Adaptive Card JSON

No response

Additional context

No response

[KattaBhargav]

#A11yUsable;#A11ySev4;#HCL;#Accessibility;#Benchmark;#BotFrameworkWebChat-Oct24;#PWD#Win11-Edge(Chromium);