[Screen Readers-Ask HR Bot-Ask HR Virtual Assistant]: NVDA is not narrating proper information if user invokes the Suggested questionnaire buttons from the list present in the page. #4296
Labels
a11y-verify-pending
area-accessibility
bug
Indicates an unexpected problem or an unintended behavior.
ExemptFromDailyDRIReport
exempt from daily DRI report
external-askhr
Milestone
PWD Impact:
Screen reader users are getting impacted if once the user invokes the suggested questionnaire buttons in the page and screen reader is not narrating the invoked button information.
Test Environment:
OS: WIN10 1909 (OS Build 18363.836)
Browser: New Edge Version 83.0.478.37 (Official build) (64-bit)
URL: https://microsoft.sharepoint.com/teams/HR_Web_Dev_Site/SitePages/AskHRBotTest.aspx
Screen Reader: NVDA 2019.3.1
Repro Steps:
Step 1: Enable NVDA and open the above URL in New Edge browser.
Step 2: Navigate to the “Ask HR Bot” Button in browse mode and invoke it.
Step 3: Chat window of “ASK HR Bot” is displayed on the screen.
Step 4: Verify the screen reader behavior upon invoking the Suggested questionnaire button in the page.
Actual Result:
NVDA is not narrating proper information if user invokes the Suggested questionnaire buttons from the list present in the page.
Ex: NVDA is narrating the previous information of what Bot Said which is already present upon invoking the "As a Generic Question" button in the chat box.
Expected Result:
NVDA should narrate the proper information if user invokes the Suggested questionnaire button from the list present at the bottom of the chat box.
Ex: Once user invokes “Ask a Generic Question” suggestion button then NVDA should narrate as Puneet Said Ask a Generic Question then with next Down arrow NVDA should narrate the suggestion provided from BOT .
Ensure that: If user ask a different question like “Leave/Time Away” then many suggestions appear on the screen NVDA should also narrate the information of the suggestions correctly while navigating in NVDA browse
MAS Reference:
MAS 4.2.1 - Object Information (33A)
The text was updated successfully, but these errors were encountered: