Using This Site

Does the indent mean anything?

It is decoration. Nothing else.

The five steps are laid out with a growing indent, and that is a picture of the axis rather than a statement of it. Every entry gives its step in words and as a number out of five, beside the title, in every list it appears in. A reader who never perceives the indent, on a narrow screen, through a screen reader, or with a stylesheet that failed to load, has exactly the information a reader who does.

Color carries nothing either. The pages print correctly in black and white and there is no legend anywhere, because there is nothing to look up.

What breaks without a script?

The letter button and the fare search. Nothing else, and both say so where they stand.

The letter button arrives switched off and the script enables it, because every check on a letter lives in the script. A note sits beside it carrying two other routes to the same desk.

The fare search button also arrives switched off, and that one is worth explaining. The booking service reads a single packed parameter rather than separate fields, and packing it needs the same script that turns a typed city name into an airport code. A button that looked usable without the script would hand the service a query it could not read. So it stays off, and a note inside the form says so.

Everything else, which is all of the reading, is present the instant the markup arrives.

Is there any movement?

Blocks rise a few pixels into place as they arrive, and that is all of it.

Where a browser or system asks for reduced motion, none of it runs: the stylesheet keeps everything visible and the script sees the preference and does nothing. Nothing plays, blinks, drifts, or covers the reading, and a block that has appeared never disappears again. If the script stalls, everything is put up regardless a fifth of a second after load.

Can I use it on a keyboard alone?

Yes. Every page opens with a link that skips the heading matter and lands in the text. From there the tab order follows the document, taking in each link, field and button once.

Wherever focus lands it is drawn as a three pixel outline in the cool accent, and that outline is never turned off. There is nothing to open, nothing that captures the keyboard and nothing to escape out of, the sections being a plain row of links.

The two place fields on the search are comboboxes: type two letters, use the arrow keys, press Enter to take one, Escape to close the list.

What reaches a screen reader?

• One first level heading per page, with levels below descending a step at a time and never skipping.
• The document language set to United States English.
• Photographs described from the finished frame rather than from the instruction that produced them, and nothing stated in a picture alone.
• Column and row headers throughout the tables, so no cell is read out stranded from its subject.
• Labeled fields without exception. A single decoy field catches machine submissions; it is out of the tab order and out of the accessibility tree.
• One status line for the whole search, announced politely, and each refused field points at that line rather than carrying a second message of its own.

Does it survive bigger text and narrow screens?

Type is set in relative units and doubles without collision or clipping. Below a certain width the paper becomes one column and the indent collapses, which costs nothing because the step is in words.

Tables too wide to fit are given their own scrolling box, which is why the document itself stays put horizontally at every width we could produce. No tap target is under forty four pixels on its short side.

Where does it fall short?

Three places, stated rather than implied.

1. Adjacent steps are hard to tell apart by indent alone. Steps two and three differ by one increment. The words are the answer and they are always there.
2. The widest table still wants a sideways drag on a small phone, inside its own box rather than moving the page.
3. What testing there was came down to a keyboard and whatever was installed. No laboratory, no matrix of readers and browsers, and it seemed better to admit that than to imply one.

How do I report a barrier?

Send the page and the symptom to openings@thecoveregister.com. Telling us the browser and the assistive software speeds it up; leaving them out does not stop it.

Whatever obstructs the reading gets treated as a fault to be repaired rather than as a request to be ranked against other work.

Reviewed August 12, 2026.