microsoft / microsoft/BotFramework-WebChat
In scan mode, screen reader is focus is moving multiple time of bot response.
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?
No response
What is the PWD impact?
When the screen reader focus moves multiple times on a single bot response in scan mode, users relying on assistive technology experience redundant navigation. Instead of encountering the response once, they are forced to cycle through repeated focus stops, which disrupts reading flow, increases cognitive load, and makes it harder to understand the conversation.
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 'Animationcard'.
- Navigate to bot response in scan mode.
- Observe the issue that In scan mode, screen reader is focus is moving multiple time of bot response.
What do you expect?
In scan mode, screen reader is focus should not move multiple time of bot response.
What actually happened?
In scan mode, screen reader is focus is moving multiple time of bot response.
Do you have any screenshots or recordings to repro the issue?
https://github.com/user-attachments/assets/198ca519-d2a6-48ad-90c7-d7038d165536
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/meaningful-sequence
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
Reproduce the issue in Web Chat using Edge with Windows Narrator: ask for “Animationcard” and navigate to the bot response in scan mode. Compare the attached recording with the expected single focus stop; the payload does not identify a source file or test, so the next step is locating the response focus handling.
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
- 48/100