Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Keyboard navigation - Make code Arcade- Project-editor]: Keyboard focus moving incorrect order after the 'Go back' control. #6117

Open
BURRAshiva01 opened this issue Mar 17, 2025 · 0 comments

Comments

@BURRAshiva01
Copy link

BURRAshiva01 commented Mar 17, 2025

User Experience:

Keyboard dependent people will get impacted if keyboard focus moves incorrect order while navigating using tab key. Due to which the end users will not be able to distinguish between the controls present on the page and can find difficulty in accessing the page.

Note: Login Credentials must not be provided within the bug.

Repro Steps:

  1. Launch application URL: https://makecode.microbit.org/#editor
  2. Now 'editor' page will open and navigate to the 'Git hub' control and select it.
  3. Navigate to the 'Pull changes' button and observe the issue.

Actual Result:

Keyboard focus moving incorrect order after the 'Go back' control.

Observations: After the 'Go back' button, keyboard focus moving to the 'Pull Changes' control instead of 'Open repository in GitHub' link.

Expected Result:

Keyboard focus should move in logical or sequential order.

Example: Keyboard focus should sequential order i.e Go back' Control->'Open repository in GitHub' link->'Pull Changes' control.

MAS Reference:

MAS 2.4.3 – Focus Order

ARIA Authoring Ref Link/Fluent Patterns Guidance /HITS Guidance/previous test pass bug id's: N/A

UIA/DOM details available:

Yes (Refer 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 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

Attachment:

Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment