How it is built
Getting Around This Site
This page states what was actually done rather than which standard is claimed, because a claim is easy to type and a keyboard is easy to test. Everything known to fall short is listed further down, by name.
The site works with the script switched off
That is the first and largest thing. Turn the script off and every page still shows its whole text, every link still works, the navigation still works because it is a plain list of links rather than a menu that has to be opened, and the catalogue still lays out because the layout is stylesheet work rather than script work.
Three things behave differently without the script, and none of them hides any reading:
- The parts of a page arrive fully visible instead of easing in. Nothing is hidden waiting for a script that failed to run.
- The storage card does not appear, and nothing is stored.
- The fare lookup cannot suggest a city, so it cannot be submitted. It says so beside the button rather than failing quietly.
Keyboard
Every link, field, button and offer in the fare lookup is reachable in order with a keyboard alone. The visible focus outline is three pixels of a dark red against the page and is never removed.
A skip link is the first thing on every page and jumps straight to the reading. The city suggestion list is operated with the down and up arrows, chosen with Enter and closed with Escape, and the field tells a screen reader which offer is current as it moves.
Screen readers
- One first level heading per page, and heading levels that step by one and never skip
- The page language is declared as United States English
- Every image carries alternative text describing what is in it, and every image on this site is decorative in the sense that no information exists only inside a picture
- Tables have real header cells with a scope, so a cell can be read with its column
- The fare lookup's fields are labeled, and its status line is announced politely when it changes
- The one hidden field in each form is a trap for automated submissions, is off the tab order, and is hidden from assistive software
Color and size
Every text pairing on this site was measured rather than eyeballed. Ordinary reading text sits well above the ratio required for normal size text, and the four largest pairings are above the stricter ratio.
Nothing on this site uses color alone to carry meaning. The making group of an entry is written in words in every place it appears, never signaled by a swatch.
Text is set in relative units and can be enlarged in the browser to twice its size without anything overlapping or being cut off. The page reflows to a single column on a narrow screen with no horizontal scrolling, and the one wide element, a table, scrolls inside its own box rather than pushing the page sideways.
Motion
The only movement on this site is a short fade as a part of the page comes into view. Where a browser or a system asks for reduced motion, that fade is switched off entirely rather than shortened.
There is nothing that moves on its own, nothing that plays, nothing that flashes, nothing that scrolls by itself, and nothing that appears over the reading and has to be dismissed.
What falls short, by name
- The place list in the fare lookup is large. On a slow connection the first suggestion after typing can take a moment, and until it arrives the field appears to do nothing. There is no progress indication in that gap.
- Table cells on a very narrow screen can require sideways scrolling inside the table box. The content is complete but reading a wide row on a small phone is awkward.
- The generated images carry alternative text that describes the material rather than every detail in the frame. Somebody reading with a screen reader gets the point of the picture and not the whole of it.
- No page has been tested with every combination of browser and screen reader. What is claimed above was checked with a keyboard and with the tools available here, and that is not the same as universal testing.
Reporting a barrier
Write to letters@hazelmilepost.com and say which page and what happened. Naming the browser and the assistive software helps and is not required.
A barrier that stops somebody reading is treated as a fault rather than a request: it goes to the front of the queue and gets a reply in the same two working days as everything else, Monday to Thursday, 10 am to 4 pm Central. If it cannot be fixed quickly, the reply says what the workaround is in the meantime.
Reviewed August 9, 2026.