Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The “Unable to connect” text can be easily missed #5217

Open
Kirank915 opened this issue Jun 20, 2024 · 1 comment
Open

The “Unable to connect” text can be easily missed #5217

Kirank915 opened this issue Jun 20, 2024 · 1 comment
Labels
area-accessibility Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete.

Comments

@Kirank915
Copy link

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?

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

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 (x2).
  5. Use the down arrow key to access the message content.
  6. Listen to the prompt.
  7. Make a selection.
  8. Select ‘Next’.
  9. Did you hear that it was unable to connect?

What do you expect?

The “Unable to connect” should be announced by screen reader as soon as user starts interacting with the page.
If the ‘Help me choose’ window is not “connected”, then ensure that it is provide first in the read order, and is narrated first in the read order.

What actually happened?

The “Unable to connect” text can be easily missed. It is only narrated when the user moves past the ‘Next’ button.

Observation: When the ‘Next’ button is pressed it is narrated as ‘pressed’, but there is no indication that nothing happens. The user has to explore outside of that area to see if they can determine why the interface is not working.

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?

image

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 Kirank915 added area-accessibility Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete. labels Jun 20, 2024
@Kirank915
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-accessibility Bot Services Required for internal Azure reporting. Do not delete. Do not change color. bug Indicates an unexpected problem or an unintended behavior. customer-reported Required for internal Azure reporting. Do not delete.
Projects
None yet
Development

No branches or pull requests

1 participant