[menu] Explicitly mention whether reading-flow should impact arrow key navigation
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Similar to a question I had about customisable select and reading-flow, per https://github.com/whatwg/html/issues/10407#issuecomment-2791525053 it seems that reading flow should impact the arrow key navigation of select options which is great. I'm assuming the same applies to the menu proposal. It would be good to explicitly state that in the proposal.
While it might not be best practice to randomly re-order things I think it would still be good if the keyboard accessibility is maintained in such scenarios.
Reading-flow isn't a complete situation (for example if you render your menu horizontally rather than vertically side arrows won't work but that can be dealt with in future.
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 reading the menu proposal and the linked WHATWG discussion on reading-flow and select navigation. Confirm how the proposal currently describes arrow-key behavior, then update its wording so the reading-flow relationship is explicit. Done means the proposal clearly states whether reading-flow affects menu arrow-key navigation, including the stated horizontal-layout limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html
- Domain
- accessibility, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100