RunestoneInteractive / RunestoneInteractive/rs
Runestone Issue: accessibility issues in Horizontal Parsons
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 69
- Forks
- 117
- Avg merge
- 6d 4h
- Merged PRs (30d)
- 24
Description
Horizontal Parsons problems lack essential accessibility features.
Both block areas should be tab stops. Within an area, arrows should move from block to block and space/enter should move the block to the other area.
There also should be non-visual feedback while navigating between blocks and when blocks are moved.
Contributor guide
No contributing guide indexed for this repository
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 Horizontal Parsons implementation and trace how its two block areas and individual blocks handle focus, keyboard input, and movement. Add keyboard navigation, block movement with Space or Enter, and non-visual feedback for navigation and moves; verify the behavior with the relevant existing checks for Horizontal Parsons.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100