Start → Wayfinding UX

Bearing 090

Wayfinding for screens

Interfaces should behave like good signposts: always telling people where they are and how to continue.

You are here

Page titles that match navigation labels. Highlighted current section. Step counters in forms.

Where next

A single primary action per screen. Secondary options grouped and quieter.

Way back

Back, cancel and undo always available. Typed input preserved after errors.

Hazards

Confirmation before deletion. Plain-English warnings with what to do next.

Method

  1. Map journeys: the routes people take through the product, including the detours.
  2. Sketch the signage: navigation, labels and hierarchy before visual style.
  3. Prototype: a clickable model on real devices.
  4. Walk the route with users: short sessions watching where people hesitate or turn back.
  5. Design system: components, states and tokens documented for developers.

Accessible routes

Wayfinding has always been about everyone reaching the destination. We design towards WCAG 2.2 AA: contrast, keyboard paths, focus visibility, text scaling and screen reader labels are part of the first sketches, not a final audit.

Deliverables

Journey maps, screen designs with every state, a component library, a short written guide and a findings report from testing.