[Screen Reader- API Management -Change background]: In the process of selecting the background color, screen reader is not announcing the updated value for the current focused color.
JMach1 opened this issue · 0 comments
TL;DR
- styles page
- open a color editor
- screen reader does not work properly with the color picker
Original MS task
https://msazure.visualstudio.com/One/_workitems/edit/15430834
User Experience:
Users dependent on screen-reader to navigate the page will face difficulty in navigating the page if the modified information does not narrate by screen reader, hence user will face difficulty in navigating the page efficiently
Note: User credentials should NOT be included in the bug.
Repro-Steps:
Open Azure portal with valid credentials and create an API Management.
Select Developer Portal (Preview) button and select it.
Navigate to the URL:API Management (azure-api.net)
Navigate to the Left nav and select Styles button.
Navigate to style page and select Change background button.
Navigate to the various controls of the "Change background" dialog box
Verify the issue
Actual Result:
In the process of selecting the background color, screen reader is not announcing the updated value for the current focused color.
Observation: Screen reader keep silent when user modified the value of background color.
Expected Result:
While modify the value of background color screen reader should be announcing the updated value.
EX: Screen reader should announce when user modified the value of background color.
Note: Same issue repro with all the screen readers.
MAS Reference:
MAS 1.3.1 – Info and Relationships
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 resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this External Bug Process (sharepoint.com) “HCL Staff should not log any third-party external bugs. Should be routed to EDAD team”.
Please reach out to C&AI Teams channel for any process related queries.