A page that responds to the keyboard

Following focus makes a page’s operational order visible, even when its layout already seemed clear.

Graphic and interaction design
A keyboard and four framed elements give form to the focus path.
A keyboard and four framed elements give form to the focus path. AI-generated illustration: a conceptual scene, distinct from the example on the page.

The mouse lets us jump between points without passing through what lies between. The Tab key exposes a sequence instead. One control receives focus, then another; at each step the page must make clear where we are and what we can do.

This sequence may describe an interface different from the one we saw. An apparently compact group breaks apart, a distant command arrives too soon, an outline disappears against the background. These details can remain undisturbed in an attractive still screenshot.

Four steps to follow

I built a small sample with a text field, a checkbox, an expandable detail and a reset command. Tab moves through them, with Shift and Tab moving in the opposite direction. The field sends no information and reset acts only on the local example.

A route through four controls

Open the detail

This text opens without sending data.

The W3C criterion on keyboard use requires functionality to be operable through a keyboard interface, with the specified exceptions for freehand movement. The sample allows one concrete case to be checked; it does not certify an entire website.

Focus is a position on the page that must be recognisable before we act. A visible outline provides this orientation. A control’s colour, selected state and focus do different jobs and may need to appear simultaneously.

The order beneath the arrangement

The sequence follows the document order. I have not added positive tab indices to visually repair a difficult route. I prefer structure and arrangement to agree, so changing the grid does not leave a second order behind that must be maintained by hand.

A thread runs through abstract controls, making their sequence visible.
A thread runs through abstract controls, making their sequence visible. AI-generated illustration: a conceptual scene, distinct from the example on the page.

A page can have more than one sensible route. Complete reading and the journey between controls do not necessarily stop at the same elements: an ordinary paragraph does not need to become a Tab stop. The operational steps must, however, retain the relationships needed to understand the task.

The expandable detail shows another distinction. It can be reached, activated and closed without inventing button behaviour inside a generic element. A native control already provides a foundation; its label, content and position remain the designer’s responsibility.

A trial to repeat after rearranging

The page’s sample remains usable without JavaScript. The AI-generated illustrations show a frame and a thread between controls; they are orientation metaphors. The actual route is that of the four elements in the document.

A keyboard check does not replace other accessibility checks. It brings out a precise question that is useful with a pointer too: how much of understanding depends on having already guessed where to go?

An arrangement is clear when the route for using it continues to make sense as we traverse it. After a visual reorganisation, I therefore return to the first control and begin again there. The mouse can wait a few steps.

A thread runs through abstract controls, making their sequence visible.
A thread runs through abstract controls, making their sequence visible. AI-generated illustration: a conceptual scene, distinct from the example on the page.