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

[Usability] [Screen reader -Help] In browse mode screen reader is reading as blank and nvda focus got struck after “the bot framework emulator GitHub Project” link. #1810

Closed
Kumar2608 opened this issue Aug 31, 2019 · 3 comments

Comments

@Kumar2608
Copy link

Actual Result:
In browse mode screen reader is reading as blank and nvda focus got struck after “the bot framework emulator GitHub Project” link.

Expected Result:
In browse mode screen reader should not read the blank and nvda focus shouldn’t get struck after “the bot framework emulator GitHub Project” link.

Repro Steps:
Turn on the NVDA
1.Open the Bot Framework V4 Emulator.
2.Navigate to the help menu and select it
3.Navigate to the get started with channels(bot inspector) and select it
4.get started with the bot inspector screen gets appears
5.Navigate to the “the bot framework emulator GitHub Project” using down arrow key(browse mode)
6.Observe the issue

User Impact:
Users who rely on screen reader will be affected if screen reader is reading multiple times blank and focus is not moving to the next controls screen reader users will skip the feature.

Test Environment:
OS Build: Version 1903(OS Build 18362.239)
Application: Bot Framework V4 Emulator
Screen reader: NVDA
Usability_Help.zip

@Kumar2608
Copy link
Author

Verified in latest bot emulator Version 4.5.2-78641 and issue has partially fixed .Hence reactivating the bug
In browse mode NVDA focus got struck at “the bot framework emulator GitHub Project” link
Please refer the attachment:1810.zip

1810.zip

@awalia13 awalia13 removed the Fixed label Sep 19, 2019
@tonyanziano tonyanziano added the InfoRequested Used to tag a11y issues that need a response from the a11y team. label Sep 25, 2019
@tonyanziano
Copy link
Contributor

@awalia13 @Kumar2608

According to another person from the accessibility team, this is the expected behavior in browse mode:

and regarding the next query , If the user keeps pressing the down arrow, focus should stop at the last control.

Focus stops at the last control here, which is the GitHub link.

@awalia13
Copy link

@tonyanziano - Agree with you hence closing the bug. In modal dialog it should go to the first control after reaching last control but not on the pages.

@ShikhaMishra11 ShikhaMishra11 removed the InfoRequested Used to tag a11y issues that need a response from the a11y team. label Nov 1, 2019
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