Accessibility work often starts with a claim that is bigger than the evidence. A small static page is a good place to practise the opposite: measure what you can see, record what you did not test, and leave a baseline someone else can repeat.
The page
The receipt demo shows a CSS Grid problem. A long order reference pushes a payment status outside its panel at 320 px. A second panel uses minmax(0, 1fr) and overflow-wrap: anywhere to keep the same content visible. It is one HTML file with no images and no framework.
After adding a public accessibility section, the page has five focusable controls: a viewport selector and four links. That count matters because a baseline is a snapshot. Add a control and the old numbers stop describing the page.
What I measured
I re-ran the checks in Vibe Chrome on 20 November 2026:
Keyboard focus. Starting from the top of the page, Tab moved through the five controls. The focused control showed a 3 px solid rgb(23, 101, 80) outline with a 3 px offset.…