RFC 6 · What should the arrow keys mean in a vertical, RTL interface?

[jihoons0]

Labels: RFC accessibility

Horizontally, arrow keys move left/right within a line and up/down between lines. Vertically, "next character" is downward and "next line" is leftward — so the keyboard model has to be remapped, and getting it wrong is instantly disorienting.

Where it shows up here: tabs, slider, popover-menu — every focusable, arrow-navigable component.

Open questions:

• Should ↓ always mean "next in reading order," or should physical arrows stay physical for muscle memory?
• How do Home/End, PageUp/PageDown translate?
• What does a screen-reader user expect the arrow semantics to be, and does that differ from a sighted keyboard user?

Write-up: https://vertically.works/challenges#keyboard-navigation
Propose your answer as a PR. Strong answers get merged into the spec.