the build, the testing, and the parts that still fall short

Accessibility

Written against WCAG 2.2 level AA. The second half of this page is the part worth reading, because it lists what is still weak.

Eight things that were done on purpose

Keyboard alone: Tab through any of the three page grounds and every control answers, with a focus ring you can actually see sitting on whichever one holds it
Heads in order: A single h1 opens each page, and from there the levels step down one at a time. None are jumped for looks
Contrast figures: Measured against the ground each line actually sits on. This site does not use a near white backdrop, so measuring against one would produce numbers that describe a different page
Text for images: Written after looking at the picture. Decorative pictures get an empty attribute instead, because hearing the caption read out a second time helps nobody
Group size marks: Encoded as one fixed area that never varies, and never as a hue. Print the page in grayscale, or read it with any form of color blindness, and nothing is lost
Motion on arrival: Blocks settle by shifting ten pixels. Opacity is left alone throughout, so a stalled animation cannot hide a page. Ask the system for reduced motion and the shift stops happening
Four hundred percent: Zoom that far and the columns reflow. No horizontal scrollbar appears
Form controls: Real labels on every field, errors written out in words beside the field that caused them, and nothing anywhere that carries meaning by hue alone

Table of five rows: The comparison table on a trip page has to be dragged sideways on a narrow phone. It is legible that way. It is not pleasant that way
Sixteen entries: On a phone the full list is a long thumb scroll, and no filter exists yet to cut it down
One reader, one browser: That pairing was tested. The rest of the field was not, and an accessibility page that pretended otherwise would be failing at the one thing it is for
English only: No second language is offered. The English is plainer than this trade usually manages, and that is the whole of the claim

Where to send it: standby@theconstanttravellers.com, with the page, the software you were reading it with, and the point at which it stopped working
What arrives back: Either a fix with a date on it or a plain statement that none is planned. Silence is the one answer this desk does not send