Record what works, what fails and what still needs testing.

Open Cadet mode at approximately 1440 px width and inspect hierarchy, clipping and arena visibility.

Evidence: Mission title, controls, arena, telemetry and score are readable without accidental overlap.

Open Builder mode with custom PID controls and inspect the full engineering layout.

Evidence: Controls remain understandable and no engineering panel is clipped or visually lost.

Review the mission around 768 px width in portrait and landscape orientations.

Evidence: Panels stack logically, controls remain touchable and horizontal overflow is absent.

Review Cadet mode around 390 px width from prediction through launch and evidence.

Evidence: The primary action is obvious, text remains readable and phase progress is usable.

Review Builder custom controls around 390 px width.

Evidence: Numeric inputs, sliders and labels are reachable without overlap or tiny targets.

Complete mode selection, prediction, configuration, launch, playback tabs and report navigation using only the keyboard.

Evidence: Every interactive control is reachable in a logical order with a visible focus indicator.

Press Tab from the top of the page and activate the skip link.

Evidence: Focus moves directly to the flagship mission content.

Inspect the page with a screen reader or browser accessibility tree.

Evidence: Main content, navigation, headings, labels and buttons have meaningful names and order.

Inspect learner mode, display preferences, sliders, tabs and playback controls.

Evidence: State, value and purpose are announced without relying on color alone.

Inspect body text, muted labels, controls and status chips in the default display mode.

Evidence: Critical instructional and operational text remains legible.

Enable High contrast and inspect controls, panels and focus states.

Evidence: Contrast improves without hiding content or changing mission behavior.

Review the page at 200% browser zoom.

Evidence: Content reflows without loss of controls, text or evidence.

Enable Reduce motion and repeat launch and tab navigation.

Evidence: Non-essential motion is suppressed while telemetry and mission state remain understandable.

Ask a primary-age learner or teacher to explain the objective and choose a flying style.

Evidence: The learner understands the immediate mission goal and can predict a cause-and-effect outcome.

Ask a middle-school learner or teacher to compare battery, rate and link evidence.

Evidence: The learner can identify at least one trade-off using telemetry rather than score alone.

Ask a secondary or college learner to change one bounded parameter and justify the result.

Evidence: The learner links a parameter change to overshoot, settling, energy or communication evidence.

Walk through the teacher guide and estimate whether the core lesson fits a 55-minute session.

Evidence: The sequence is teachable with one device per team and no hardware dependency.

Print or save the student experiment sheet to PDF on A4.

Evidence: Fields, tables and page breaks are usable in monochrome and no navigation chrome is printed.

Complete a run, open Evidence & Report and print or save it to PDF.

Evidence: Mission identity, score, phase evidence, findings, provenance and boundaries remain readable.

Ask the reviewer to identify which channels are simulated, estimated, commanded, reference and derived.

Evidence: No software-only channel is mistaken for measured hardware truth.

Ask the reviewer what M1 does and does not model.

Evidence: The reviewer describes F1 one-axis attitude plus teaching-grade mission systems and does not infer flight certification.