[Screen Readers-Ask HR Bot-Ask HR Virtual Assistant]: JAWS is narrating the suggestion invoked by the user twice upon invoking the Suggested Questionnaire button present in the “Ask HR Virtual Assistant” chat window.

[KattaBhargav]

PWD Impact:

Screen reader users are getting impacted if JAWS is narrating the suggestion invoked by the user twice upon invoking the Suggested Questionnaire button present in the “Ask HR Virtual Assistant” chat window.

Test Environment:

OS: WIN10 1909 (OS Build 18363.836)
Browser: Chrome Version 83.0.4103.61 (Official Build) (64-bit)
URL: https://microsoft.sharepoint.com/teams/HR_Web_Dev_Site/SitePages/AskHRBotTest.aspx
Screen Reader: JAWS 2019.1912.1

Repro Steps:

Step 1: Enable JAWS and open the above URL in Chrome browser.
Step 2: Navigate to the “Ask HR Bot” Button in cursor mode and invoke it.
Step 3: Invoke any of the suggested questionnaire button present in the chat window.
Step 4: Verify the screen reader behavior upon invoking the suggestion questionnaire button present in the “Ask HR Virtual Assistant” chat window.

Actual Result:

JAWS is narrating the suggestion invoked by the user twice upon invoking the Suggested Questionnaire button present in the “Ask HR Virtual Assistant” chat window.
Ex: JAWS is narrating as: "User Said Ask a Generic HR Question sent at
29th May 2020 2.16 P.M User Said Ask a Generic HR Question sent at
29th May 2020 2.16 P.M. "

Expected Result:

JAWS should narrate the suggestion invoked by the user once upon invoking the Suggested Questionnaire button present in the “Ask HR Virtual Assistant” chat window.
JAWS should narrate as : "User Said Ask a Generic HR Question sent at
29th May 2020 2.16 P.M."

MAS Reference:

MAS 4.2.1 - Object Information (33A)

[KattaBhargav]

Bug copied from CSEO team Bug id:-BUG 5843513

[axelsrz]

assigning @compulim

[compulim]

Action items:

• When a message with suggested actions arrives, we should narrate it thru live region twin
• Suggested actions container should be a toolbar role
  • Buttons will implement using the roving index mechanism
  • tabindex="0" for focusing button, tabindex="1" for non-focusing, so TAB key will skip all other buttons and move focus to next focusable after the container
• Move accesskey attribute from the buttons to the suggested actions container
• (Optional) We may not need to narrate "suggested actions: is empty"
• (Optional and need asks) Carousel flipper buttons could have TAB disabled (tabindex="-1") to reduce confusion and complexity when pressing TAB key to access the suggested action buttons

[compulim]

Reopen to pend for verification.

[compulim]

This is done in PR #4323. Testers did not verify it on time, so we assume this is fixed properly.

[KattaBhargav]

#A11yMAS;#A11ySev3;#HCL;#WCAG4.2.1;#Accessibility;#Win10-Edge(Chromium);#BotFrameworkWebChat-Aug21;#Linked:BUG 5843513;#LinkedBug;