You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User Experience
Users who rely on AT will face difficulty and easily confused if the headings are not defined correctly.
Test Environment
Browser: Microsoft Edge Canary Version: 82.0.425.0 (Official build)
OS build: 2004 (19564.1005)
Screen Reader: Narrator
URL: Bot Framework Composer Prerequisite Here
Repro Steps:
Open the above mentioned URL in EDGE.
Select 'Design Flow' from left navigation.
Now, turn on the narrator and navigate with 'H' i.e. shortcut for Headings.
Observe the issue in the flow chart area.
Actual:
The heading of the flow chart i.e. 'Dialog started' is not defined under heading tags.
Expected:
The name of the flow chart should be defined under heading tag. So, that the user will able to navigate quickly through the heading shortcut.
@corinagum As checked, now it is defined in heading {specifically in h4} but the heading structure is not logically correct as no h1, h2 or h3 is defined on the page.
As checked and verified on below environment, the issue is fixed now. So, we are closing the issue.
Test Environment
Browser: Microsoft Edge Dev {Version 83.0.467.0 (Official build) dev (64-bit)}
OS build: 2004 (19588.1000)
Screen Reader: Narrator
URL: Bot Framework Composer Prerequisite Here
User Experience
Users who rely on AT will face difficulty and easily confused if the headings are not defined correctly.
Test Environment
Browser: Microsoft Edge Canary Version: 82.0.425.0 (Official build)
OS build: 2004 (19564.1005)
Screen Reader: Narrator
URL: Bot Framework Composer
Prerequisite Here
Repro Steps:
Actual:
The heading of the flow chart i.e. 'Dialog started' is not defined under heading tags.
Expected:
The name of the flow chart should be defined under heading tag. So, that the user will able to navigate quickly through the heading shortcut.
MAS Impacted: MAS2.4.6
Attachment:
The text was updated successfully, but these errors were encountered: