microsoft / microsoft/BotFramework-WebChat

Role is not defined for the play/pause control.

Open
#5,741 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11ySev2 A11yWCAG Accessibility area-accessibility Bot Services BotFrameworkWebChat_Web bug customer-reported HCL-BIC
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

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 role is not defined for the play/pause control, screen reader users cannot understand what type of element it is or how to interact with it. They may only hear “button” or nothing at all, leaving them unsure whether it controls audio, video, or another function.

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 Role is not defined for the play/pause control.
What do you expect?

Role as button should be defined for the play/pause control.

What actually happened?

Role is not defined for the play/pause control.

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

https://github.com/user-attachments/assets/92cc09d1-765f-43cd-9a61-f91b61e53815

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the play/pause control in a Web Chat bot response using Edge with Windows Narrator, then inspect the control's DOM accessibility properties. Done means the control exposes a button role and screen reader users can identify how to interact with it.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
accessibility, frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.