ROUTE field guide
ROUTE Accessibility: VoiceOver, Contrast, and Reduced Motion
Accessibility considerations for route drawing, readable feedback, hints, and motion preferences.
Labels explain state
Control names, values, and hints should expose progress, availability, and consequences.
Color is not enough
Markers, endpoints, paths, and blocks need distinct form and contrast.
Motion cannot gate progress
Reduced effects must still reveal completion, errors, grade, and the next action.
Try it on a field
Open ROUTE on iPhone and change one path at a time. Every playable field is solver-validated, so a failure is useful evidence about corridor ownership, endpoint access, or coverage.
Sources and review scope
- ROUTE 1.0 in-app rule and mode copy.
- ROUTE support and purchase behavior, reviewed 2026-09-01.
- Apple subscription management for billing-control references.
Related guides
Updated 2026-09-01How to Play ROUTE: Cover Every Playable YardLearn the complete ROUTE rules for receiver pairs, defenders, crossings, and full-field coverage.Updated 2026-09-01ROUTE Rookie Campaign Guide: Build the Core HabitUse the first 20 free Rookie plays to learn endpoints, corridors, and coverage.Updated 2026-09-01ROUTE Endless Strategy: Build a Longer Clean RunApproach solver-validated Endless fields without rushing the next generated board.