microsoft / microsoft/pxt-microbit
[Morse Chat Tutorial] Keyboard Navigation: "What is Morse code?" Section Cannot Be Expanded Using Enter or Space
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 804
- Forks
- 721
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 2
Description
Describe the bug
In the Morse Chat tutorial, the "What is Morse code?" expandable section can receive keyboard focus, but it cannot be expanded using the keyboard(Enter or Space).
Steps to reproduce the behavior:
- Navigate to Microsoft MakeCode for micro:bit.
- Scroll to the Tutorials for the new micro:bit (V2) section.
- Use Tab to move focus to the Morse Chat tutorial card.
- Press Enter to open the tutorial.
- Continue using Tab until focus moves to the "What is Morse code?" expandable section.
- Press Enter or Space.
- Observe the behavior of the section.
Actual behavior
The "What is Morse code?" section receives keyboard focus, but pressing Enter or Space does not expand the content.
Expected behavior
The "What is Morse code?" section should expand and collapse when activated using Enter or Space, allowing keyboard-only users to access the content in accordance with standard accessibility expectations for expandable controls.
Screenshots
Additional context
1.OS: Windows 11 25H2 & Mac Mini M2 macOS Tahoe 26.5.2
2.Browser: Chrome, Edge, Firefox, and Safari
3.makecode.microbit.org version: 9.0.3
4.Microsoft MakeCode version: 13.0.3
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 by opening the Morse Chat tutorial and locating the "What is Morse code?" expandable section and its activation handling. Reproduce the issue with keyboard focus, then verify that Enter and Space expand and collapse the section and that the content is accessible to keyboard-only users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100