oficina / docs Public

The formatting bar is one tab stop, not eleven

role="toolbar" is a promise: a single tab stop, with the arrow keys
moving between the controls inside it. This branch made that promise in
the markup and did not keep it — eleven tab stops between the page
header and the first word of a document, on every page load, for someone
who only wanted to type. Measured, not estimated: the drive counted nine
presses from sign-out to the editor before this commit.

toolbar.mjs now implements the WAI-ARIA pattern. Every control is
tabindex="-1" in the server-rendered markup and the module promotes one;
Left/Right (and Home/End) move between them, with preventDefault on the
keys it handles because a closed native <select> changes its own value
on Left/Right. Up/Down are left alone, which is how the three selects
stay operable from the keyboard.

Not by reordering the DOM, which was the other available fix and is
worse: the bar sits above the paper visually, so DOM order already
matches reading order, and pulling focus order away from visual order to
save a few tab presses trades a small annoyance for a WCAG 2.4.3 Focus
Order violation. (Raised, and argued correctly, by the caret-placement
session.)

Nothing here touches focus VISIBILITY. The controls keep rastrillo's own
ring — a roving tabindex decides which control Tab reaches, not whether
you can see which one you are on — and show.html's ring removal stays
scoped to [docs-editor] alone.

One trap this pattern sets, handled: undo and redo start disabled, a
disabled control cannot take focus at all, and a tab stop parked on one
makes the whole bar unreachable rather than merely awkward. ensureReachable
runs after every sync, because sync is what enables and disables things.

Three checks in the browser drive, all confirmed red before being kept:

- A focus trap on the bar (preventDefault on Tab) — the reachability
  check reports twelve presses without arriving.
- The pre-fix behaviour (every control its own tab stop) — nine presses,
  which is what the single-tab-stop check now refuses.
- Arrow navigation removed — focus goes "from undo to undo".

The reachability check exists because of a gap in the previous commit's
keyboard assertion, spotted by the caret session: focusing the editor
programmatically succeeds whether or not a person could ever have got
there with Tab, so a bar that trapped focus would have left the document
unreachable to anyone without a mouse while every check still passed. It
tabs in from the sign-out button instead, bounded at twelve presses —
bounded rather than exact, so it does not become an assertion about how
many controls the bar has this week.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YYB9fUAfxXNzkeC3fsFYzR