Play/Pause control name is not descriptive.

Is it an issue related to Adaptive Cards?

Yes, this is related to Adaptive Card. However, it does not repro on Adaptive Cards Designer.

What is the PWD impact?

When the play/pause control name is not descriptive, screen reader users cannot understand what the control does. Hearing only “button” or a vague label like “control” leaves them unsure whether it starts audio, pauses video, or performs another action.

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

What is the public URL for the website?

No response

How to reproduce the issue?

Repro Steps: ​

1. Open URL: Web Chat in edge browser.
2. Ask query 'Audio'.
3. Navigate to Pay/pause control present in bot response.
4. Observe the issue that Play/pause control name is not descriptive.

What do you expect?

Screen reader should announce the descriptive name for the pay/pause control.

What actually happened?

Play/pause control name is not descriptive.

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

https://github.com/user-attachments/assets/b0e67926-9fb2-4b3e-928e-e70b48f2fbf7

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

No response

MAS reference

No response

WCAG reference

https://www.w3.org/WAI/WCAG21/Understanding/name-role-value

WAI-ARIA reference

No response

Adaptive Card JSON

Additional context

No response

Start by reproducing the issue in Web Chat with Edge and Windows Narrator: ask for “Audio” and navigate to the play/pause control. Inspect how the control is exposed to assistive technology and verify that its announced name identifies the media action rather than only “button” or “control”.