Follow the same evidence.
Visuals should make a concept easier to inspect. TraceToScale also provides forms, recorded steps and readable component evidence.
Use the keyboard and forms.
Prediction choices, parameters, run controls, explanation fields and account actions use labeled native controls. Focus indicators and a skip-to-content link help navigate the application.
The architecture studio offers component selection, parameter editing, connection creation, removal, undo and redo through controls alongside its canvas. React Flow also supports keyboard node interaction. A graph can be imported or exported as versioned JSON.
Choose how to inspect a run.
Pause, rewind, step or scrub the recorded trace. A component table identifies status, placement and recorded values. Events and metrics remain text-readable; color is paired with status labels.
The application respects the browser’s reduced-motion preference. Automatic trace playback is disabled in that mode while stepping and scrubbing remain available. Spatial cameras change only when requested; they do not rotate automatically.
Use spatial views selectively.
Selected region and zone lessons offer a spatial view synchronized with the same recorded state. Keyboard-accessible buttons rotate, tilt, zoom and reset its camera. The equivalent flat graph and component table remain available.
If WebGL is unavailable or its graphics context fails, the view returns to the flat alternative. No learning answer requires using a 3D camera.
Keep audio and timing optional.
The written interview path is complete without a microphone. Permission denial, an unsupported recording format or unavailable private storage leaves text available. Uploaded audio is not automatically transcribed.
Timed interview rooms offer a 10–60 minute window selected before starting. The server deadline continues while a tab is hidden. Untimed lessons and the studio remain available when timed practice does not suit your needs.
Report a barrier.
Accessibility review is an ongoing release activity. Browser, assistive-technology and device combinations can expose issues beyond the automated and manual checks performed during development.
An accessibility contact has not yet been configured. The operator must publish a working contact before public release.