[Accessibility][Name, Role, Value - Flow Chart]: Name is not defined for 'More Option' button.

[Padmini171991]

User Experience
Users who rely on AT will face difficulty to interact with the webpage if the name of the controls are not defined properly. As well as if the arrow's name's are not defined how the AT dependent user will know the flow.

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

Actual Result
Name of the "More Option" is not defined. As well as the name is not defined for the the arrow's and the end node.

Expected:
The name should be defined for all the controls and the arrows so that the user will know the flow of the arrow.
Note: Same issue is repro within 'Bot responses' and 'User Input. Refer attachmentMAS4.1.2_Bot responses_K4W (1).zip

Repro Steps:

1. Open the above mentioned URL in EDGE.
2. Select 'Design Flow' from left navigation.
3. Now, navigate to '+' button with tab in the flow chart.
4. Observe the issue.

MAS Impacted: MAS4.1.2

Attachment:

[ashish315]

@cwhitten Issue still repro, cross checked with 'Master' botframework composer.

[alanlong9278]

@ashish315 hi, I checked with master branch, there are name property in the more options , arrow and end node.

[corinagum]

I am able to reproduce this issue. These nodes/button do not have aria-label assigned. This means that the AT does not have information to announce. data-name and name are not announced by AT.

As another note, please do not add aria-labels to the SVG. The SVG should be hidden from the AT (aria-hidden), and a parent div should have the label.

[corinagum]

@Padmini171991 could you clarify the need for the end arrow + node to have a name defined? Is this because the non-visual user must know when reaching the end of the step editor? Thank you.

[alanlong9278]

arrow ,+ node is a svg node, as the notice says: do not have label in svg node, so we can not add labels. @Padmini171991 @corinagum

[ashish315]

@alanlong9278 So, is it by design???

[corinagum]

@ashish315 I believe this is by design. With mouse (and keyboard) the arrow+ does not receive focus, so I think aria-label is unnecessary. @alanlong9278 please correct me if I am wrong. :)

[ashish315]

As this is by design. So, HCL is closing the issue.