Ambulance and Bay
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. 12 of its 12 steps can be finished with the keyboard alone.
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, 13 steps, 27 clips |
| pass | loads nothing from another host |
| pass | the edge serves the bytes that were tested 2588450 bytes |
| pass | iPhone (WebKit, iOS Safari UA, 390x844): boots and the deck is real 2 scenes, 13 steps |
Build fingerprint (SHA-256 of the page the site serves): afc6ba54bc3092695c8f0a2012e2e62d03bb845fc7155d53b5fcdc514d2d0b08, 2,588,450 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 | 154 | 29 |
| iPhone 13/14/15, upright (390 x 664) | played to the end | 0 | 154 | 29 |
| Android phone, upright (360 x 680) | played to the end | 0 | 154 | 29 |
| iPhone held sideways (844 x 340) | played to the end | 0 | 146 | 29 |
| Small phone held sideways (667 x 320) | played to the end | 0 | 156 | 29 |
| iPad, upright (820 x 1106) | played to the end | 0 | 255 | 29 |
| iPad, sideways (1180 x 746) | played to the end | 0 | 256 | 29 |
| Laptop (1366 x 768) | played to the end | 0 | 246 | 29 |
- iPhone SE, upright (375 x 548): same walkthrough verdict on the laptop control: walkthrough exit 1: steps in the manifest: 13; steps photographed: 11
- iPhone 13/14/15, upright (390 x 664): same walkthrough verdict on the laptop control: walkthrough exit 1: steps in the manifest: 13; steps photographed: 11
- Android phone, upright (360 x 680): same walkthrough verdict on the laptop control: walkthrough exit 1: steps in the manifest: 13; steps photographed: 11
- iPhone held sideways (844 x 340): same walkthrough verdict on the laptop control: walkthrough exit 1: steps in the manifest: 13; steps photographed: 11
- Small phone held sideways (667 x 320): same walkthrough verdict on the laptop control: walkthrough exit 1: steps in the manifest: 13; steps photographed: 11
- iPad, upright (820 x 1106): same walkthrough verdict on the laptop control: walkthrough exit 1: steps in the manifest: 13; steps photographed: 11
- iPad, sideways (1180 x 746): same walkthrough verdict on the laptop control: walkthrough exit 1: steps in the manifest: 13; steps photographed: 11
- Laptop (1366 x 768): walkthrough exit 1: steps in the manifest: 13; steps photographed: 11
3. Accessibility
Keyboard only. The training was played with no mouse: Tab, Space, Enter and the arrow keys. 12 of 12 steps were finished that way.
Focus. 21 Tab stops were visited. Every one showed a visible focus indicator. After 0 of 35 key presses the focus went back to the top of the page.
Narration. 13 of 13 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, 1 boxes clipped their text.
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. Two 360 videos, the patient compartment of an ambulance and a station bay, played on a sphere; the project files do not say whether they were filmed or generated.
The training itself does not say whether its pictures are generated or photographed.
Declared limits
- The manifest was written by Volanno, not exported from the FUSE Manifest Builder, so a real video manifest may sequence events differently.
- Seek targets inside the video (continueVideoTime) are not exercised by this demo.
- The results record's shape is inferred from the manifest, not from a real FUSE results payload, and is marked unverified inside itself.
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: ambulance-bay.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.