[Keyboard Navigation- Make code - new branch name]: Screen reader doesn't announce the displayed error message for edit field under "New branch name" dialog. #5498
Screen reader dependent users will be impacted. If Screen reader is not announcing the error message information which appears for edit field. Due to this issue end users will be confused and unable to get the error message.
Note:
User credentials should NOT be included in the bug.
Navigate to "Review, Commit and push local changes to GitHub" button and select it.
Navigate through all the controls appearing and select Project name#master Drop down. and select.
Navigate through all the controls appearing under "Switch to a different branch" and select "Create new branch".
Navigate through all the controls under "New Branch name" Dialogue.
Provide the special character in edit field and error message displays
Observe and verify whether screen reader announces displayed error message or not.
Actual Result:
Screen reader doesn't announce the displayed error information for edit field.
Observation:
On providing invalid input as "%&" error message is displayed but screen reader remains silent.
Screen reader doesn't announce the infromation "Name cannot have spaces or special characters. Examples: my_feature, add-colors, fix_something" when focus moves to edit field.
Other Screen reader behavior: NVDA and Narrator remains silent after error message displayed on the screen.
Expected result:
The screen reader should announce the displayed error information for edit field.
Solution: Screen reader should announce like Error "Don't use spaces or special characters".
ARIA Authoring Ref Link/Fluent Patterns Guidance /HITS Guidance:
NA
DOM details available:
Yes(Please refer to the attachment)
Reference Links:
Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
External Bug Process: If this bug belongs to external team, mark it as resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this Link. “HCL Staff should not log any third-party external bugs. Should be routed to EDAD team”.
Yamini234u
commented
7 months ago
User Experience
Screen reader dependent users will be impacted. If Screen reader is not announcing the error message information which appears for edit field. Due to this issue end users will be confused and unable to get the error message.
Note: User credentials should NOT be included in the bug.
Repro Steps:
Actual Result:
Screen reader doesn't announce the displayed error information for edit field. Observation:
Expected result:
The screen reader should announce the displayed error information for edit field. Solution: Screen reader should announce like Error "Don't use spaces or special characters".
MAS Reference:
MAS 4.1.3 – Status Messages
ARIA Authoring Ref Link/Fluent Patterns Guidance /HITS Guidance: NA
DOM details available:
Yes(Please refer to the attachment)
Reference Links:
Test Environment:
https://github.com/microsoft/pxt-microbit/assets/117158108/ec7a965c-4c4d-47d7-bd55-f9080523e903