microsoft / microsoft/pxt-microbit
[Screen Reader] Clickable block name is incorrectly announced in tutorial step content during keyboard navigation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
Describe the bug
When using a screen reader (Windows Narrator or macOS VoiceOver), the clickable block name in tutorial step content is incorrectly announced as its category name instead of the block name during keyboard navigation.
Steps to reproduce the behavior:
- Enable a screen reader: Windows Narrator (Windows 11) or VoiceOver (macOS)
- Navigate to Microsoft MakeCode for micro:bit.
- Tab to a tutorial card.
- Press Enter twice to start the tutorial.
- Use Tab/Enter to navigate to a tutorial step content area.
- Observe the screen reader announcement.
Actual behavior
The screen reader announces the category name instead of the clickable block name.
Expected behavior
The screen reader correctly announces the clickable block name when focused in the tutorial step content.
Screen Recording
https://github.com/user-attachments/assets/3f2c7115-57db-4a45-9f02-ca2c9355fe69
Additional context
1.OS: Windows 11 25H2 & Mac Mini M2 macOS Tahoe 26.5.1
2.Browser: Chrome, Edge, Firefox, and Safari
3.makecode.microbit.org version: 8.1.28
4.Microsoft MakeCode version: 12.3.24
5.Screen Readers: Narrator and VoiceOver
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the tutorial card and tutorial step content entry points involved in keyboard navigation, then reproduce with Narrator or VoiceOver and inspect the focused clickable block's accessible name. Compare the announced category name with the expected block name across the listed browsers. Done when the block name is announced correctly during Tab/Enter navigation.
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
- 48/100