microsoft / microsoft/BotFramework-WebChat
Incorrect role is defined for ‘Place to buy’ and ‘Related product’ control.
Nobody has claimed this yet.
- 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 an incorrect role is defined for the “Place to buy” and “Related product” controls, screen reader users receive misleading or incomplete information. For example, if these controls are marked as role="link" but actually behave like buttons, users may expect navigation instead of an 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:
- Open URL: Web Chat in edge browser.
2.Ask query 'Carousel'. - Navigate to ‘Place to buy’ and ‘Related product’ control.
- Observe the issue that Incorrect role is defined for ‘Place to buy’ and ‘Related product’ control.
What do you expect?
Role as button should be defined for the ‘Place to buy’ and ‘Related product’ control.
What actually happened?
Incorrect role is defined for ‘Place to buy’ and ‘Related product’ control.
Do you have any screenshots or recordings to repro the issue?
https://github.com/user-attachments/assets/a5276b16-a066-4509-bebd-fc243601470d
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
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.
Research direction
Start by reproducing the Carousel flow in Edge with Windows Narrator, then inspect the DOM roles for the “Place to buy” and “Related product” controls. No source file or test is named in the issue. Done means both controls expose button roles and screen readers receive the expected action information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100