Ten Seconds on the Line
On 2026-10-30 this training passed 7 of 7 live-site checks and played to the end on 8 of 8 screen shapes with no layout blockers. 26 of its 27 steps can be finished with the keyboard alone; steps where you press a marked point still need a mouse, finger or pen.
1. The live site
Opened at its public address in Chrome and in WebKit (the engine inside Safari) set up as an iPhone. The last check compares the bytes the internet serves with the file that was tested, so this page describes exactly what you get.
| Result | Check |
|---|---|
| pass | answers 200 over https 200 |
| pass | the engine BOOTS: running, not merely served |
| pass | no page errors |
| pass | the deck is real 4 scenes, 27 steps, 52 clips |
| pass | loads nothing from another host |
| pass | the edge serves the bytes that were tested 15752210 bytes |
| pass | iPhone (WebKit, iOS Safari UA, 390x844): boots and the deck is real 4 scenes, 27 steps |
Build fingerprint (SHA-256 of the page the site serves): df7f3046f1bec263a7ea3a815d3df5988b22926a44af8bd746d495957728cf53, 15,752,210 bytes.
2. Phones, tablets and a laptop
The whole training was played start to finish at each screen shape, answering every step the way a trainee does, and the layout was measured before every screen: a control that cannot be reached or is covered, a page that scrolls sideways, a card too small to read. Those are blockers. Warnings are smaller things, like a target under 40 px.
| Screen | Result | Layout blockers | Warnings | Screens measured |
|---|---|---|---|---|
| iPhone SE, upright (375 x 548) | played to the end | 0 | 372 | 62 |
| iPhone 13/14/15, upright (390 x 664) | played to the end | 0 | 366 | 62 |
| Android phone, upright (360 x 680) | played to the end | 0 | 379 | 62 |
| iPhone held sideways (844 x 340) | played to the end | 0 | 364 | 62 |
| Small phone held sideways (667 x 320) | played to the end | 0 | 379 | 62 |
| iPad, upright (820 x 1106) | played to the end | 0 | 653 | 62 |
| iPad, sideways (1180 x 746) | played to the end | 0 | 599 | 62 |
| Laptop (1366 x 768) | played to the end | 0 | 575 | 62 |
- iPhone SE, upright (375 x 548): walkthrough exit 1: steps in the manifest: 27; steps photographed: 26; Re-run straight after the sweep, same build, same device shape, one run at a time: all 27 steps photographed and the finish reached (devices-rerun/_report.json). The first run missed one or two steps timed on the training's video while three device runs were decoding video at once; not a layout fault. It is shown here as it happened.
- iPhone 13/14/15, upright (390 x 664): walkthrough exit 1: steps in the manifest: 27; steps photographed: 26; Re-run straight after the sweep, same build, same device shape, one run at a time: all 27 steps photographed and the finish reached (devices-rerun/_report.json). The first run missed one or two steps timed on the training's video while three device runs were decoding video at once; not a layout fault. It is shown here as it happened.
- iPhone held sideways (844 x 340): walkthrough exit 1: steps in the manifest: 27; steps photographed: 26; Re-run straight after the sweep, same build, same device shape, one run at a time: all 27 steps photographed and the finish reached (devices-rerun/_report.json). The first run missed one or two steps timed on the training's video while three device runs were decoding video at once; not a layout fault. It is shown here as it happened.
- Small phone held sideways (667 x 320): walkthrough exit 1: steps in the manifest: 27; steps photographed: 26; Re-run straight after the sweep, same build, same device shape, one run at a time: all 27 steps photographed and the finish reached (devices-rerun/_report.json). The first run missed one or two steps timed on the training's video while three device runs were decoding video at once; not a layout fault. It is shown here as it happened.
- iPad, upright (820 x 1106): walkthrough exit 1: steps in the manifest: 27; steps photographed: 26; Re-run straight after the sweep, same build, same device shape, one run at a time: all 27 steps photographed and the finish reached (devices-rerun/_report.json). The first run missed one or two steps timed on the training's video while three device runs were decoding video at once; not a layout fault. It is shown here as it happened.
3. Accessibility
Keyboard only. The training was played with no mouse: Tab, Space, Enter and the arrow keys. 26 of 27 steps were finished that way. Steps where you press a marked point could not be finished without a pointer, so a mouse was used for those steps only, to reach the rest of the training.
Focus. 31 Tab stops were visited. Every one showed a visible focus indicator. After 1 of 166 key presses the focus went back to the top of the page.
Narration. 26 of 26 spoken lines were on screen as text while they played.
Zoom and reflow. 320 CSS px (SC 1.4.10): no sideways scrolling, main button on screen; 200% zoom (SC 1.4.4): no sideways scrolling, main button on screen. With the WCAG text-spacing override, no text was clipped.
Automated rules (axe-core 4.10.3, WCAG 2.x A and AA), run on the first card, on the first step of every kind and on the finish screen. Rules that failed at least once:
- No rule failed.
The full conformance report for the player is the accessibility conformance report (VPAT).
4. What this training says about itself
Pictures. A ten-second stock 360 video of a working restaurant kitchen, with close-ups cut from its frames and one flat still.
The training itself does not say whether its pictures are generated or photographed.
Declared limits
- The clip does not quite join up behind you; this is declared on the first card, and the scene opens facing the line, away from the join.
- It is stock footage of somebody else's kitchen; the cooks did not agree to be examples, and no step asks you to judge a person.
- No printed text in the clip is legible, so nothing is named from a label.
- The safety practices are general. Extinguisher locations, house rules and whether flaring is allowed at all need the customer's own word.
5. What was not tested
- Real handsets. The screen shapes are Chrome set to each size, with a phone's touch and toolbar behaviour simulated. The iPhone check runs WebKit on Windows, not an iPhone.
- A screen reader (NVDA, JAWS, VoiceOver) played through the whole training by a person.
- Firefox, and Safari on a Mac.
- A slow or dropped network while the training plays.
- A VR headset. This page covers the browser player only.
- Whether the teaching is right for your site. That is a subject-matter review, not a test.
Machine-readable record of this page: kitchen-line.json. Every number on this page comes from that record, and every value in it comes from a test run on 2026-10-30. Nothing is typed in by hand.