What the Image Shows
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. 19 of its 22 steps can be finished with the keyboard alone; steps where you find every one in the scene, open numbered badges, 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 2 scenes, 22 steps, 52 clips |
| pass | loads nothing from another host |
| pass | the edge serves the bytes that were tested 11790472 bytes |
| pass | iPhone (WebKit, iOS Safari UA, 390x844): boots and the deck is real 2 scenes, 22 steps |
Build fingerprint (SHA-256 of the page the site serves): ea2853ec8029b7309e53d977f170d411e4dc809a20b878e2304ee001135a6cfd, 11,790,472 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 | 255 | 55 |
| iPhone 13/14/15, upright (390 x 664) | played to the end | 0 | 245 | 54 |
| Android phone, upright (360 x 680) | played to the end | 0 | 254 | 54 |
| iPhone held sideways (844 x 340) | played to the end | 0 | 204 | 55 |
| Small phone held sideways (667 x 320) | played to the end | 0 | 199 | 55 |
| iPad, upright (820 x 1106) | played to the end | 0 | 487 | 54 |
| iPad, sideways (1180 x 746) | played to the end | 0 | 430 | 54 |
| Laptop (1366 x 768) | played to the end | 0 | 446 | 54 |
3. Accessibility
Keyboard only. The training was played with no mouse: Tab, Space, Enter and the arrow keys. 19 of 22 steps were finished that way. Steps where you find every one in the scene, open numbered badges, 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. 67 Tab stops were visited. Every one showed a visible focus indicator. After 110 of 210 key presses the focus went back to the top of the page.
Narration. 19 of 19 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. One generated 360 image of a security checkpoint, used for both scenes, plus a six-second generated film clip; the voices are synthetic.
Told to the trainee: “THIS ROOM IS A GENERATED IMAGE. Nobody in it is a real person”
Declared limits
- The picture does not quite close: one vertical join behind you is declared, and no step aims within 42 degrees of it.
- It is not any agency's procedure. Screening procedures are Sensitive Security Information and are not published.
- It does not teach reading an X-ray image; the bag on the screen is a drawing.
- It gives no alarm-resolution procedure and no numbers on detection, throughput, wait times or performance.
- The audio exchange is scripted and spoken by synthetic voices, not a recording.
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: what-the-image-shows.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.