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

[MAS1.3.1][Screen Reader-Connect the bot] Voiceover announces the same name on the two control with different role. #1909

Closed
Kumar2608 opened this issue Oct 4, 2019 · 1 comment

Comments

@Kumar2608
Copy link

Kumar2608 commented Oct 4, 2019

Actual Result:
The voiceover announces the same name i.e. "Restart Conversation" on "Restart conversation" button and "Restart conversation" dropdown.

Expected Result:
Both the controls should be associated and consolidated focus should land on them.
Else the voiceover should announce them as "Restart Conversation" menu pop-up combo box.

Repro Steps:

  1. Open the Bot Framework V4 Emulator.
  2. Welcome tab screen gets opened.
  3. Navigate to the "Open Bot" button and activate it.
  4. Open a Bot Dialog box gets opened.
  5. Navigate to the "bot URL" edit box and enter URL- http://localhost:3978/api/messages
  6. Navigate to "Connect" button and activate it.
  7. "Live Chat" separate window appears.
  8. Navigate to "Menu Bar" control.
  9. Observe the issue.

User Impact:
Users who depends on the Screen reader will get confused if same name is defined for both the controls with different role.

Test Environment:
OS: MacOs Version 10.15
Application: Bot Framework V4 Emulator (Version 4.5.2-80829)

Impacted MAS Link:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={54f28d1f-a2d1-4dcd-84e1-5c9b87e8aba4}

Attachment:
Same name defined for two controls.zip

@ShikhaMishra11
Copy link

As we have checked and verified, the issue gets fixed in the latest version of BOT. So, we are closing the issue.

Regression Environment:
OS: MacOs Version 10.15
Application: Bot Framework V4 Emulator (Version 4.6.0-93410)

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants