microsoft / BotFramework-WebChat

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

The navigation of the interface is not simple and increases user cognitive load. #5220

Closed Kirank915 closed 1 month ago

Kirank915 commented 3 months ago

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

Navigation in the chat region is not easy. Cognitive users will find it difficult in navigation, remembering or understanding when to use the [up/down arrow] and when to [Tab] is frustrating. The user can easily move out of the ‘Help me choose’ window without even knowing it.

What browsers and screen readers do this issue affect?

Others

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?

https://www.microsoft.com/en-us/surface?at_preview_token=4FhxMZZq5RXQNNpOOuFqCLBpWwq30eLAUx7_sjX2n68&at_preview_index=1_2&at_preview_listed_activities_only=tru

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. Turn on the NVDA ‘Speech viewer”.
  4. Navigate the interface and listen to or read the content.

What do you expect?

The navigation of the interface should be simple and clear.

What actually happened?

The navigation of the interface increases user cognitive load. Determining what text and sections are in the chat history is unclear. Remembering or understanding when to use the [up/down arrow] and when to [Tab] is frustrating. The user can easily move out of the ‘Help me choose’ window without even knowing it.

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

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 3 months ago

A11yMAS;#A11ySev2;#MAS1.3.1;#HCL;#Accessibility;#FeatureBotframeworkwebchat-Apr23;#AILimited;

OEvgeny commented 3 months ago

We're removing this screen as we already follow well known keyboard shortcuts #5218