FUSE 2D Player Accessibility Conformance Report
Section 508 Edition · based on VPAT® Version 2.5Rev
A newer edition of this report exists: the second edition, re-tested after keyboard and screen-reader access shipped. This first edition is kept as it was measured, on the build of 17 September 2026.
Name of Product/Version: FUSE 2D Player, the browser player for FUSE trainings, as served by the 17 hosted FUSE 2D trainings on 2026-09-22 (build of 17 September 2026). Each training's exact build is identified by the SHA-256 fingerprint on its test-evidence page.
Report Date: 2026-09-22
Product Description: A training player that runs in any modern browser on phones, tablets and computers. A trainee works through steps in 360° scenes, still pictures and video: reading cards, answering questions, making timed decisions, and finding, pressing or marking things in the scene.
Contact Information: Volanno · 202.455.4785
Notes: This is a self-assessment by the vendor, on ITI's template, of the player a trainee uses. It does not cover the FUSE Builder web platform or the FUSE Studio authoring tool, which will get editions of their own, or the VR headset app. Every conformance level was set against a test run on the live builds on 2026-09-22, or against the player's source where a remark says so. It is a dated measurement: when a gap below is fixed, the criterion is re-tested and the report is reissued with a new date.
Evaluation Methods Used:
- Keyboard-only play-through of all 17 trainings, no mouse: Tab, Space, Enter and the arrow keys, with a step counted as keyboard-operable only if it was finished with keys alone from the moment it appeared (293 of 391 steps). Focus visibility was measured at every Tab stop by comparing the focused and blurred computed style.
- axe-core 4.10.3 (WCAG 2.0, 2.1 and 2.2 A and AA rules) in Chrome, on the first card, on the first step of every kind in each training, and on the finish screen.
- Narration against on-screen text for every spoken line (320 lines).
- Reflow at 320 CSS px, 200% zoom as a 683 x 384 viewport, and the WCAG text-spacing override.
- A full play-through on seven phone and tablet shapes, upright and sideways, plus a laptop (136 runs), with the layout measured before every screen.
- A live-site sweep confirming the bytes the public sites serve equal the files tested.
- Review of the player's source for criteria no run can see (sound control, motion sensors, hover content).
- Not performed: a full pass with a screen reader (NVDA, JAWS or VoiceOver) by a person; testing on physical phones (shapes were emulated in Chrome, and iPhone Safari as WebKit on Windows); Firefox; flash analysis of video content.
Summary
Of the 50 WCAG 2.1 Level A and AA criteria: 27 Supports, 13 Partially Supports, 6 Does Not Support, 4 Not Applicable.
Known gaps (Does Not Support)
- 2.1.1 Keyboard
- 2.1.4 Character Key Shortcuts
- 2.5.1 Pointer Gestures (WCAG 2.1)
- 4.1.2 Name, Role, Value
- 1.2.5 Audio Description (Prerecorded)
- 4.1.3 Status Messages (WCAG 2.1)
The first three share one cause: the markers a trainee presses in a scene are not controls a keyboard or screen reader can reach. Making them focusable, named buttons, adding a keyboard way to find and mark things in the scene, and announcing verdicts through a live region is the planned remediation; this report will be reissued when it ships and has been re-tested.
Applicable Standards/Guidelines
| Standard/Guideline | Included in Report | Remarks and Explanations |
|---|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A (Yes), Level AA (Yes), Level AAA (No) | Covered by the WCAG 2.1 tables below, which include every WCAG 2.0 criterion. |
| Web Content Accessibility Guidelines 2.1 | Level A (Yes), Level AA (Yes), Level AAA (No) | |
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | Yes |
Terms
- Supports: the functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: some functionality of the product does not meet the criterion.
- Does Not Support: the majority of product functionality does not meet the criterion.
- Not Applicable: the criterion is not relevant to the product.
WCAG 2.x Report
Section 508 incorporates WCAG 2.0 A and AA by reference (E205.4, E207.2, 602.3). WCAG 2.1 criteria are marked.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Controls carry text or an accessible name. The 360 scene itself has no text alternative beyond the narration and card text that describe it, and the markers a trainee presses in the scene have no accessible name (they are unlabelled elements; see 4.1.2). |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Partially Supports | Narration: 296 of 320 spoken lines across the fleet were on screen as text while they played (measured). Audio-clip steps show their transcript. 360 video scenes have no separate text or audio description of what the video shows beyond the card narration. |
| 1.2.2 Captions (Prerecorded) | Partially Supports | The player's narration is the on-screen card text read aloud, so the text is always present. Video scenes that carry their own soundtrack (the Metro Box technician videos) are not captioned; the player has no caption track support. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Partially Supports | Card narration describes what each step is about, but 360 video scenes have no audio description or full text alternative of the video content. |
| 1.3.1 Info and Relationships | Partially Supports | Answer choices are real radio buttons and checkboxes inside their labels; the control bar is a labelled toolbar and the scene map is a labelled dialog. Card titles are not marked up as headings, and markers in the scene have no role. axe-core rule label failed on 17 of 17 trainings: the unlabelled inputs are the three calibration sliders in the author's hidden tools drawer, which a trainee does not use but which are still in the page. axe-core rule scrollable-region-focusable failed on 11 of 17 trainings. |
| 1.3.2 Meaningful Sequence | Supports | Card content reads in the order it is shown; one card is in front of the trainee at a time. |
| 1.3.3 Sensory Characteristics | Partially Supports | Some instructions are spatial by nature ("turn to the unit on your left", "find every one in the room"). The card text names the object as well, but the task itself is visual. |
| 1.4.1 Use of Color | Supports | Right and wrong answers are stated in words on the verdict card, not by colour alone. |
| 1.4.2 Audio Control | Supports | Narration starts only after the trainee presses to start it. Mute (on screen and the M key) and Pause stop all sound: narration, video soundtrack and clips (source review). |
| 2.1.1 Keyboard | Does Not Support | Measured by playing every training with the keyboard only: 293 of 391 steps were finished with keys alone, and 0 of 17 trainings could be finished end to end without a pointer. Steps where the trainee must find every one in the scene, open numbered badges, pick out a point on a flat picture, press a marked point, draw a box on the scene cannot be done from the keyboard: the markers are not focusable, and finding or drawing in the scene needs a pointer. Cards, questions, decisions, and turning the room with the arrow keys work from the keyboard. |
| 2.1.2 No Keyboard Trap | Supports | Tab moved through every card and control and out again on all 17 trainings; focus was never held. |
| 2.1.4 Character Key Shortcuts | Does Not Support | Single-letter shortcuts (M mute, P pause, R replay, L look around, B back) are always on outside text fields and cannot be turned off or remapped. |
| 2.2.1 Timing Adjustable | Partially Supports | 1 of 17 trainings contain timed decision steps. Pause holds the clock for as long as the trainee wants, and Back re-runs the step on a fresh clock, but there is no setting to extend or turn off the time limit. Reading and review timers only delay the Continue button. |
| 2.2.2 Pause, Stop, Hide | Supports | The Pause control (and P) stops narration, video and every clock in the player. The one repeating animation (the "More below" nudge) runs only when the user has not asked for reduced motion. |
| 2.3.1 Three Flashes or Below Threshold | Supports | The player produces no flashing content. The video scenes in the fleet were not analysed with a flash-measurement tool. |
| 2.4.1 Bypass Blocks | Supports | Each training is a single screen with no repeated navigation blocks to bypass; the card is the main content. |
| 2.4.2 Page Titled | Supports | Every training's page title is the training's name (measured on all 17). |
| 2.4.3 Focus Order | Partially Supports | Tab order follows the screen, but after 840 of 1561 key presses during the keyboard play-through, focus fell back to the top of the page because the card is rebuilt; the trainee must Tab forward again. The author's hidden tools drawer adds up to 12 Tab stops that cannot be seen. |
| 2.4.4 Link Purpose (In Context) | Supports | The few links in the player say where they go. |
| 2.5.1 Pointer Gestures (WCAG 2.1) | Does Not Support | Looking around a 360 scene is a drag, and a draw-a-box step is a drag; on a touch screen neither has a single-tap alternative. On a keyboard the arrow keys turn the room. |
| 2.5.2 Pointer Cancellation (WCAG 2.1) | Supports | Markers and buttons act on release (the click event), not on press. |
| 2.5.3 Label in Name (WCAG 2.1) | Supports | Visible button text is the start of each accessible name. |
| 2.5.4 Motion Actuation (WCAG 2.1) | Supports | Nothing is operated by tilting or shaking the device (source review: the player reads no device-motion sensors). |
| 3.1.1 Language of Page | Supports | The page language is declared (lang="en" on 17 of 17, measured). |
| 3.2.1 On Focus | Supports | Moving focus never changes the step, the scene or the card. |
| 3.2.2 On Input | Supports | Ticking an answer does not submit it; the trainee presses Check or Continue. |
| 3.3.1 Error Identification | Supports | A wrong answer is identified in text on the verdict card, with the reason. |
| 3.3.2 Labels or Instructions | Supports | Every question and task states what to do on its card. |
| 4.1.1 Parsing | Supports | Obsolete in WCAG 2.1 per the W3C's 2023 errata; recorded as Supports as that errata directs. |
| 4.1.2 Name, Role, Value | Does Not Support | The markers a trainee presses in the scene (numbered badges, pins) are plain elements with a click handler: no role, no accessible name, not focusable. The start-narration prompt carries role="button". axe-core rule scrollable-region-focusable failed on 11 of 17 trainings. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The player has no live audio. |
| 1.2.5 Audio Description (Prerecorded) | Does Not Support | 360 video scenes have no audio description track. |
| 1.3.4 Orientation (WCAG 2.1) | Supports | Works upright and sideways: the play-through reached the end on phones and tablets held both ways (132 of 136 device runs clean). |
| 1.3.5 Identify Input Purpose (WCAG 2.1) | Not Applicable | The player asks for no personal information. |
| 1.4.3 Contrast (Minimum) | Partially Supports | axe-core rule color-contrast failed on 17 of 17 trainings. The failing text includes the card's kind and title line, the Look around and Continue buttons, the start-narration prompt, and the score labels on the finish screen, among others (the run keeps three examples per rule). Text over a live 360 scene cannot be measured by the rule engine and was not measured by other means. |
| 1.4.4 Resize Text | Partially Supports | At 200% zoom (measured as a 683 x 384 CSS viewport) 17 of 17 trainings had no sideways scrolling and 17 kept the main button on screen. On phones and tablets pinch-zoom is switched off (axe-core rule meta-viewport failed on 17 of 17 trainings). |
| 1.4.5 Images of Text | Supports | The player puts no text in images; text that appears inside a photographed or generated scene is part of the scene. |
| 1.4.10 Reflow (WCAG 2.1) | Supports | At 320 CSS pixels wide, 17 of 17 trainings had no sideways page scroll and 17 kept the main button on screen. The 360 scene is two-dimensional content, exempt as such. |
| 1.4.11 Non-text Contrast (WCAG 2.1) | Partially Supports | Buttons and their focus rings were designed against the player's own card colours. Markers sit over photographs and generated scenes, where contrast varies with the picture and was not measured. |
| 1.4.12 Text Spacing (WCAG 2.1) | Partially Supports | With the WCAG text-spacing override applied to the first cards, 16 of 17 trainings clipped no text. |
| 1.4.13 Content on Hover or Focus (WCAG 2.1) | Partially Supports | A marker's name appears as a tooltip on mouse hover; it stays while hovered, but it cannot be dismissed with Escape (source review). |
| 2.4.5 Multiple Ways | Not Applicable | A training is a single page and a step in a process, which the criterion exempts. |
| 2.4.6 Headings and Labels | Supports | Each card carries its kind and title, and every button says what it does. |
| 2.4.7 Focus Visible | Supports | 533 of 533 visible Tab stops visited during the keyboard play-through changed appearance when focused (measured: focused versus blurred computed style). |
| 3.1.2 Language of Parts | Supports | Content is in one language per copy. |
| 3.2.3 Consistent Navigation | Supports | The control bar is the same on every step of every training. |
| 3.2.4 Consistent Identification | Supports | Controls with the same function carry the same name throughout. |
| 3.3.3 Error Suggestion | Supports | The verdict card explains the right answer and why. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Not Applicable | The player makes no legal or financial commitment and changes no user data. |
| 4.1.3 Status Messages (WCAG 2.1) | Does Not Support | Verdicts, attempt counts and new cards are not announced to assistive technology: the player has no live region. |
Revised Section 508 Report
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Does Not Support | Finding, pressing and drawing on things in a 360 scene is a visual task and the markers are not exposed to assistive technology. A full screen-reader pass was not run. |
| 302.2 With Limited Vision | Partially Supports | Desktop browser zoom works (see 1.4.4 and 1.4.10); pinch-zoom is blocked on phones and some text fails minimum contrast (see 1.4.3). |
| 302.3 Without Perception of Color | Supports | No information is carried by colour alone (see 1.4.1). |
| 302.4 Without Hearing | Partially Supports | Everything narrated is on screen as text; video soundtracks are not captioned (see 1.2.2). |
| 302.5 With Limited Hearing | Partially Supports | As 302.4; narration can be replayed at any time. |
| 302.6 Without Speech | Supports | No step requires speech. |
| 302.7 With Limited Manipulation | Does Not Support | Pointer-only steps (see 2.1.1) and drag gestures (see 2.5.1) remain. |
| 302.8 With Limited Reach and Strength | Partially Supports | No step needs force or reach beyond the device's own screen, but the pointer-only steps in 2.1.1 still apply. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially Supports | Plain-language cards, Replay, Pause and Back are always available; timed decision steps add time pressure by design (see 2.2.1). |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| All of Chapter 4 | Not Applicable | The player is software; it includes no hardware. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope – Incorporation of WCAG 2.0 AA | See WCAG 2.x section | The player is web content; see the WCAG tables above. |
| 502 Interoperability with Assistive Technology | Not Applicable | Applies to platform software. The player runs inside the browser and is evaluated as web content under WCAG. |
| 503.2 User Preferences | Partially Supports | The player follows the reduced-motion preference; it does not follow the system colour scheme or font size beyond browser zoom. |
| 503.3 Alternative User Interfaces | Not Applicable | The player provides no alternative user interface that functions as assistive technology. |
| 503.4 User Controls for Captions and Audio Description | Not Applicable | The player has no caption or audio-description tracks to control (see 1.2.2 and 1.2.5). |
| 504 Authoring Tools | Not Applicable | This report covers the player a trainee uses. The FUSE Studio authoring tool is out of scope for this edition. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 602.2 Accessibility and Compatibility Features | Supports | This report and each training's public test-evidence page document the accessibility features and their gaps. |
| 602.3 Electronic Support Documentation | Supports | This report and the evidence pages were checked with the same rule engine (axe-core) at build time; see Evaluation Methods. |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | There is no non-electronic support documentation. |
| 603.2 Information on Accessibility and Compatibility Features | Supports | Provided in this report, the evidence pages and on request. |
| 603.3 Accommodation of Communication Needs | Supports | Support is available by phone (see Contact Information). |
Legal Disclaimer
This report describes the FUSE 2D Player as tested on the date above, by the vendor, using the methods listed. It is provided for information and does not constitute a warranty. Trainings authored by customers may add content (pictures, video, text) whose accessibility depends on how it was authored.
"Voluntary Product Accessibility Template" and "VPAT" are registered service marks of the Information Technology Industry Council (ITI). · Test evidence for every training · FUSE 2D Trainings