microsoft / microsoft/BotFramework-WebChat
Screen reader is not announcing the proper information with 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 a screen reader does not announce the proper information with a bot response, users relying on assistive technology cannot understand the content or context of the response. They may only hear generic output like “text” or “message” without the actual content, which prevents them from following 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 Screen reader is not announcing the proper information with bot response.
What do you expect?
Screen reader should announce the proper information with bot response.
What actually happened?
Screen reader is not announcing the proper information with bot response.
Do you have any screenshots or recordings to repro the issue?
No response
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/info-and-relationships
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 issue in Edge with Windows Narrator using the 'Animationcard' query, then inspect the bot response in scan mode. Compare what the screen reader announces with the expected response content and use the WCAG information-and-relationships reference to define the accessibility requirement. Done means the response is announced with its proper information and context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100