microsoft / BotFramework-WebChat

A highly-customizable web-based client for Azure Bot Services.
https://www.botframework.com/
MIT License
1.56k stars 1.51k forks source link

Screen reader is announcing “Grouping” when navigating through chat history in browse mode. #5213

Open Kirank915 opened 2 weeks ago

Kirank915 commented 2 weeks ago

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?

  1. 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.
  2. Start NVDA.
  3. [Tab] to the ‘Help me choose’ button and open the window. Focus will be on the close “X”.
  4. Tab x 2
  5. “Chat history, use the up and down arrow keys”
  6. “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?

image

Did you find any DOM elements that might have caused the issue?

No response

MAS reference

https://aka.ms/MAS1.3.1

WCAG reference

No response

WAI-ARIA reference

No response

Adaptive Card JSON

No response

Additional context

No response

Kirank915 commented 2 weeks ago

A11yusable;#A11ySev4;#AILimited;#HCL;#Accessibility;#FeatureBotframeworkwebchat-Apr23;