microsoft / microsoft/pxt-microbit

[Screen Reader] Close button name is not announced in Blocks hint when navigating via keyboard

Open
#6,956 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2 screenreader
Dominant language
TypeScript
Stars
804
Forks
721
Avg merge
2d 9h
Merged PRs (30d)
2

Description

Describe the bug
When Windows 11 Narrator is enabled, the Close button in the Blocks hint is not correctly announced during keyboard navigation in the Blocks Start Tutorial.

Steps to reproduce the behavior:

  1. Enable Windows 11 Narrator.
  2. Navigate to Microsoft MakeCode for micro:bit.
  3. Use Tab to focus on the "Blocks Start Tutorial" button and press Enter.
  4. Press Tab to focus on the hint icon and press Enter to open it.
  5. Press Tab to move focus to the Close button.
  6. Observe Narrator output.

Actual behavior
Narrator announces only "button" and does not read the Close button name.

Expected behavior
Narrator should announce the Close button with its accessible name when focused.

Screen Recording
https://github.com/user-attachments/assets/eaa27598-c53e-49dc-bc7e-65a5c6393530

Additional context
1.OS: Windows 11 25H2
2.Browser: Chrome, Edge, and Firefox
3.makecode.microbit.org version: 8.1.26
4.Microsoft MakeCode version: 12.3.21

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue from the Blocks Start Tutorial: enable Windows 11 Narrator, open the hint with the hint icon, and tab to Close. Inspect the implementation behind that tutorial hint and its Close button, then verify that keyboard focus causes Narrator to announce the button's accessible name in Chrome, Edge, or Firefox.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.