You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users who depend on keyboard navigation will be impacted if controls are not accessible with keyboard and they will not be able to perform any desired action with the keyboard.
Now verify that user is able to insert the different category blocks in editor area or not without drag and drop feature.
Actual Result:
There is no keyboard access for "Input Section" controls under "Blocks"
Observation:
While focus is on "Input" control , after pressing tab , right/left arrows and ctrl+arrows focus is not moving to the Right section of input controls.
Expected Result:
"Input Section" controls should be accessible through the keyboard.
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 External Bug Process (sharepoint.com). “HCL Staff should not log any third-party external bugs. Should be routed to EDAD team”.
User Experience:
Users who depend on keyboard navigation will be impacted if controls are not accessible with keyboard and they will not be able to perform any desired action with the keyboard.
Repro Steps
Actual Result:
There is no keyboard access for "Input Section" controls under "Blocks"
Observation:
While focus is on "Input" control , after pressing tab , right/left arrows and ctrl+arrows focus is not moving to the Right section of input controls.
Expected Result:
"Input Section" controls should be accessible through the keyboard.
MAS Reference
MAS 2.1.1 – Keyboard
Reference Links:
Test Environment:
MAS2.1.1-Keyboard.acesssible-Make.code.mp4
The text was updated successfully, but these errors were encountered: