Interface checks
The model has its own page of checks. This one is about the thing a student actually touches. It loads the real simulation, plays whole lives through it at three screen sizes, and prints PLAYABLE only if nothing threw, nothing locked up, and every control it was offered could be reached and clicked.
Playing...
Why this page exists.
On 4 August 2026 six faults were fixed in this simulation and four of
them were found by accident, while doing something else. A modal that
clipped its own content and left the page inert, reported twice
because it only reproduces on a short screen. A header that pushed
every page sideways on a phone. A car drawn off the edge of the
stage. None of them are model faults, and the model checks could
never have caught any of them.
- This does not check that the simulation is good. It checks that it can be played to the end without breaking, which is the floor and not the ceiling.
- It plays like a machine, not like a student: it takes the first option offered on every card. A person will find things this cannot.
- It checks that the simulation can be operated from a keyboard, but not that it is pleasant to. Nobody who relies on a screen reader has used this yet, and no amount of programmatic checking substitutes for that.
- Color contrast is not checked here. The model checks measure it on 86 rendered elements in both themes, and measuring it twice would mean two answers that can disagree.
- It runs the real page in a frame, so what it measures is the shipped interface rather than a copy of it.
The run being played