microsoft / microsoft/BotFramework-WebChat
Screen reader is announcing “Grouping” when navigating through chat history in browse mode.
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.
What is the PWD impact?
No response
What browsers and screen readers do this issue affect?
Windows: Edge with Windows Narrator, Windows: Chrome with NVDA, Windows: Chrome/Firefox with JAWS
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?
- Open https://www.microsoft.com/en-us/surface?at_preview_token=4FhxMZZq5RXQNNpOOuFqCLBpWwq30eLAUx7_sjX2n68&at_preview_index=1_2&at_preview_listed_activities_only=true in Edge.
- Start NVDA.
- [Tab] to the ‘Help me choose’ button and open the window. Focus will be on the close “X”.
- Tab x 2
- “Chat history, use the up and down arrow keys”
- “Grouping Bot Surface said” – Is it clear to the user what this means?
What do you expect?
Screen readers should not announce grouping information while navigating through chat history.
Remove the role=”group” from the
What actually happened?
Screen reader is announcing “Grouping” when navigating through chat history in browse mode.
Do you have any screenshots or recordings to repro the issue?
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
No response
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 at the linked Microsoft Surface URL with Edge and a screen reader, then inspect the chat-history DOM for the div using role="group". Done means the grouping role is removed for this content and screen readers no longer announce “Grouping” while navigating chat history.
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
- 35/100