Description
User Experience:
Keyboard dependent people will get impacted if any interactive element present on the page is not keyboard accessible. Due to which the end users will not be able to access the video of the bring code into your classroom section and might face difficulty in accessing the page.
Note:
User credentials should NOT be included in the bug.
Repro Steps:
- Launch application URL: https://www.microsoft.com/en-us/makecode/teach
- Teach page will open.
- Navigate the page using tab key and observe whether 'Start video' button is keyboard accessible or not.
Actual Result:
Issue: 'Start video' button is not keyboard accessible as it was not getting activated with 'Enter/Space/ CTRL Enter.
Observation There is play button beside the 'Start video' control, but keyboard focus doesn't move to it while navigating using tab key.
Expected Result:
'Start video' button should be keyboard accessible. When focus is on the 'Start video' button, by pressing 'Enter/Space' it should get activated.
MAS Reference:
ARIA Authoring Ref Link/Fluent Patterns Guidance /HITS Guidance:
NA
UIA/DOM details available:
NA
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 an 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”.
- Please reach out to C&AI Teams channel for any process-related queries.
Test Environment:
OS Version: Windows 11 24H2 (OS Build:26100.3037)
Browser: Chrome Version 132.0.6834.196 (Official Build) (64-bit)
Test Matrix: Chrome + NVDA
URL: https://www.microsoft.com/en-us/makecode/teach