Ten-Foot Information Architecture
Overview
Optimize screens for distance readability, low cognitive load, and directional navigation. Prioritize fewer decisions per view with clear primary actions.
IA Rules
- •Keep primary CTA visible above fold on details screens.
- •Limit concurrent choices per row to avoid focus hunting.
- •Group metadata into short, scannable blocks.
- •Keep navigation hierarchy shallow for Back predictability.
Workflow
- •Define user intent per screen (browse, decide, play, recover).
- •Rank actions by priority and map to first-focus, second-focus, overflow.
- •Reduce branch complexity before adding new rails or tabs.
- •Design explicit empty/error states with valid focusable actions.
- •Confirm all flows are fully operable with directional keys only.
Visual Interaction Requirements
- •Strong focus ring contrast over bright hero art.
- •Clear state separation for focused, selected, disabled.
- •Legible type scale for typical viewing distance.
Validation Checklist
- •First meaningful action reachable in <= 3 moves from entry focus.
- •No required task depends on text entry unless unavoidable.
- •No dead-end state without clear recovery CTA.
References
- •Use
references/layout-heuristics.mdfor page templates and spacing heuristics.