Role is not defined for the play/pause control.
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- html
- Domain
- accessibility, frontend
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.
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:
- Open URL: Web Chat in edge browser.
- Ask query 'Audio'.
- Navigate to Pay/pause control present in bot response.
- 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
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/BotFramework-WebChat
-
Bot Services bug customer-reported
Difficulty 1/5 Under an hour Newbie friendliness 65/100
microsoft/BotFramework-WebChat#5165 ·
-
area-accessibility Bot Services bug customer-reported
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoft/BotFramework-WebChat#5861 ·
-
Bot Services bug customer-reported
Difficulty 3/5 1-2 days Newbie friendliness 58/100
microsoft/BotFramework-WebChat#5859 ·
-
area-accessibility Bot Services bug customer-reported
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/BotFramework-WebChat#5857 ·
-
A11ySev3 A11yWCAG area-accessibility Bot Services BotFrameworkWebChat_Web bug customer-reported
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoft/BotFramework-WebChat#5856 ·
All issues in microsoft/BotFramework-WebChat
Similar issues
-
accessibility angular bug good first issue typescript ux
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
apache/fineract-backoffice-ui#584 · 1 comment ·
-
bug
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
spartan-ng/spartan#1763 ·
-
Access Score Gallery Label Map
Difficulty 2/5 Half a day Newbie friendliness 68/100
ProjectSidewalk/SidewalkWebpage#5430 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100