Botframework-emulator: [MAS4.2.1] [Screen Reader->choose a different location] In browse mode NVDA is not navigating to the heading of the dialog window in logical order

[Kumar2608]

Actual Result:
In browse mode NVDA is not navigating to the heading of the dialog window in logical order present in the Resource setting for this bot

Expected Result:
In browse mode NVDA focus should moves to the heading of the dialog window in logical order

Note: This issue exits throughout the application for all dialog heading controls

Repro Steps:
Turn on the NVDA
1.Open the Bot Framework V4 Emulator.
2.Welcome tab screen gets opened
3.Navigate to the resources and select it
4.Navigate to the transcripts control and select it
5.Navigate to the choose a different location control and select it
6.Dialog gets opened
7.Navigate to the “Resource setting for this bot ” heading using browse mode(Down arrow key)

User Impact:
Users who rely on screen readers will be affected if the screen reader is not moving to the heading elements then the screen reader users will skip the feature

Test Environment:
OS Build: Version 1903(OS Build 18362.239)
Browser: Edge
Application: Bot Framework V4 Emulator
Screen reader: NVDA

MAS Reference Link:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={b24201d1-2276-4471-8183-e1e5353031ad}
MAS4.2.10_Choose a different location.zip

[tonyanziano]

@Kumar2608 @awalia13

What are the criteria for success here?

Do all the headings need to be hit, and what qualifies as a heading (label for inputs, main dialog heading - "Resource settings for this bot")? If the user keeps pressing the down arrow, should the focus eventually stop, or loop back up to the first heading?

[dollykumari5]

@tonyanziano, main dialog heading qualifies as a heading in this dialog box.

Normally when user press down arrow key after close button screen reader should narrate the heading(Resource settings for this bot) and then move to the next control, but here its skipping the heading and moving to the next control , so the heading is never read by screen reader.

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

[tonyanziano]

@dollykumari5 Great, thanks for the clarification.

[Kumar2608]

Verified in latest Bot emulator version -4.5.2-79718 with NVDA(2019.2) .Issue still reproing hence reactivating this bug .
In browse mode NVDA is not navigating to the heading of the dialog window in logical order present in the Resource setting for this bot

[tonyanziano]

@awalia13 @Kumar2608

I can't repro this on version 4.5.2-79718 or 4.5.2-79874 using NVDA 2019.2.

Can you please tell me exact step-by-step instructions on how you are encountering this issue?

When I enter Browse mode, and open the dialog, the narrator reads "Resource settings for this bot dialog." Also, my narrator does not get stuck on repeatedly narrating "blank" after it reaches the last control via the down arrow. It instead reads "Save changes button".

[awalia13]

@tonyanziano - We will look into this and provide guidance on priority.
@Kumar2608 - Please provide the single video from start which includes Version of Bot Emulator/NVDA Version and steps to replicate the issue.

[Kumar2608]

Verified in latest Bot emulator version -4.5.2-80608 with NVDA(2019.2) .Issue still repro'ing hence reactivating this bug .
In browse mode NVDA is not navigating to the "Resource settings for this bot "heading after close button.
Current focus order(Browse mode): Close button->Locations for scripts ->Text field->Browse control->Locations for Transcripts
Expected focus order(Browse mode): Close button->"Resource settings for this bot "heading->Locations for scripts ->Text field->Browse control->Locations for Transcripts
Please refer the attachment:1793.zip
1793.zip

[awalia13]

@tonyanziano - Team has uploaded the video. feel free to ping me if you have any questions.

[Kumar2608]

Verified in latest bot emulator version 4.5.2-80829 with NVDA(2019.2) issue got fixed now hence we are closing this bug