2.2.1

Each journey option should be represented by the vehicles in that journey. This will define the journey for the user and they will understand how many changes are involved. Stating the number of changes numerically is always open to misinterpretation.

2.2.2

The graphical representation of the journey should not include walking, except where the whole journey is a walk. This is consistent with how people think of journeys (i.e. walking is assumed). Walks will be fully represented in the actual journey plan.

2.2.3

There should be strong visual distinction between each option. It is important that the user can view each option as a discrete package of information, but also make quick comparisons between options.

2.2.4

Each journey option should have its own "View" button. This should directly follow the option information and only one full journey plan should be shown at a time.

2.2.5

Additional functions for filtering or sorting journey options should visually separate from the options. Such additional functions are non-essential, but may have the added benefit of providing a key for icons in the options.