Colour in Wayfinding & Signage

Colour is one of wayfinding's best tools and one of its most over-trusted. Done well, a colour code lets a stranger navigate a hospital, an airport, a car park or a metro at a glance: 'follow the blue', 'we parked on the orange level', 'take the green line'. Colour is fast, pre-verbal and works across languages - a genuine gift in public buildings full of hurried, stressed, unfamiliar people. But colour also has hard limits that get ignored, and a wayfinding scheme that leans on colour alone will fail exactly the people who most need help.

The limits come straight from the earlier lessons. Colour changes under different light (Module 3) - the 'teal' zone under daylight is a different animal under sodium car-park lamps, and a printed map rarely matches the painted wall. Colour is confused by a large minority of viewers (Lesson 8.2). Colour has cultural and contextual baggage (Module 2) that varies by audience. And people simply cannot hold many colours in mind - ask someone whether they parked on the purple or the magenta level and watch the system break.

So the mature position is: use colour to speed recognition, never to carry the message by itself. Colour is the accelerator; text, shape, number and position are the load-bearing structure. When the two agree, wayfinding feels effortless. When colour is asked to do the whole job, it becomes a trap for the colour-blind, the low-vision, the elderly, the anxious and anyone under the wrong light.

> Colour helps you find the sign fast. It is the words, numbers and symbols that tell you what it means.

There is also a capacity question that good schemes respect. Reliable colour coding tops out at roughly six or seven distinct, nameable colours - and that is under good light for good eyes. Beyond that, colours start to collide (is that light green or teal?), and the whole point of quick recognition is lost. A large, complex building is better organised by a clear hierarchy - zones, then levels, then rooms - than by inventing a fifteenth colour nobody can name.

The heart of accessible wayfinding is redundancy: every piece of information carried by colour is also carried by at least one thing that is not colour. The gold-standard example is a well-run metro. Take a line that is 'the Blue Line': it is also Line 3, it is also named, its stations are listed in order, and on the platform it is reinforced by position and signage. A passenger who cannot tell blue from purple still rides it perfectly, because four independent cues point the same way.

One message, four independent cues (metro line):
  colour ..... blue      (fast recognition)
  number ..... Line 3    (unambiguous, sayable)
  name ....... 'Blue Line' / terminus names
  position ... fixed slot on every map and board

Build the same redundancy into any coded environment:

Redundancy toolkit for wayfinding:
  colour + NUMBER ...... 'P2', 'Level 3', 'Line 6'
  colour + NAME ........ 'Cardiology', 'North Wing'
  colour + SHAPE ....... circle / square / triangle tab
  colour + ICON ........ bed, plane, parking 'P'
  colour + POSITION .... same corner, same order, always
  colour + TEXTURE ..... a banded vs plain floor strip

Shape deserves special mention because it is the most robust partner to colour and the basis of the safety-sign system (Lesson 8.4): a triangle, a circle and a square are told apart instantly, at distance, in poor light, in silhouette and by everyone regardless of colour vision. Pairing each zone colour with a consistent shape tab is one of the cheapest, strongest moves in the toolkit.

Consistency is what turns cues into a language. A colour or shape must mean the same thing everywhere in the building, every time - green is always 'this way to the gardens', never 'gardens here' on one floor and 'emergency' on another. The moment a code contradicts itself, users stop trusting it and fall back to reading every word, which defeats the purpose. Map the whole system before you place a single sign, and audit it for collisions: does any zone colour clash with the mandatory safety colours (red, yellow, green, blue) already claimed by fire and emergency signage? Those meanings are reserved, and your decorative wayfinding must not fight them.

A colour code is worthless if the sign carrying it cannot be read, so everything from Lesson 8.1 comes back here, applied to the sign itself. Three questions decide whether a sign works: is there enough value contrast, is the text big enough for the distance, and is it free of glare?

Value contrast first. The text-to-background contrast on a sign should clear the WCAG-style thresholds - aim for the large-text 3:1 as an absolute floor and 4.5:1 or better for anything approaching normal reading size. The safest, most timeless signage is high value-contrast: dark text on a light ground or light text on a dark ground. Coloured backgrounds are where schemes come unstuck - white text on mid-yellow, or dark text on saturated red, often fails - so choose the pairing for value, then let hue do the zone-coding job. A blue-zone sign can be a dark navy with white text (excellent contrast) rather than mid-blue with white text (marginal).

Sign legibility checklist:
  contrast ...... >=4.5:1 text; >=3:1 large text and arrows
  cap height .... ~25 mm per 6-8 m of reading distance
  finish ........ matt / low-glare; watch overhead lamps
  typeface ...... clean, open, generous counters
  case .......... sentence case for anything long
  arrows ........ count as UI parts - give them contrast too

Size and distance follow the rule of thumb from 8.1 - roughly 25 mm of letter height per 6 to 8 metres of viewing distance - so overhead concourse signs need big type and a directory read at arm's length can be smaller. Glare quietly destroys more signs than bad colour does: a glossy or glass-fronted sign under a downlight mirrors the lamp into the reader's eyes. Specify matt faces and think about the lighting the sign will actually sit under, day and night.

Do not forget the arrow and the icon: WCAG treats graphical elements that carry meaning as needing 3:1 contrast too, and an arrow the eye cannot find is as bad as a word it cannot read. Tactile and Braille signage, and mounting height, belong to the fuller accessibility standards, but the colour designer's contribution is clear - make the value contrast generous and the coloured pairing legible, and the code you worked so hard to design will actually be seen.

Pulling it together, here is how to design a colour-coding system that survives real use. Start by asking whether you need colour coding at all - a small, legible building with good sightlines and clear names may not. If you do, design it as a hierarchy, not a rainbow.

A robust wayfinding hierarchy (example, hospital):
  1. Zone .... few big colours + name + shape
              (Blue = Diagnostics, Green = Wards...)
  2. Level ... numbers, consistent everywhere (L1, L2)
  3. Dept .... names + icons within the zone colour
  4. Room .... numbers in a logical, signed sequence

Keep the colour count within the six-or-seven ceiling, and choose the colours deliberately: pick hues that differ in value as well as hue (so they survive greyscale and CVD), avoid the red-green and blue-purple collisions, and steer clear of the reserved safety colours for anything that is not a safety message. Give every colour a plain, agreed name ('teal', not 'the blue-green one') and write it into the signage manual so it is used consistently in maps, spoken directions and print.

Then make it redundant everywhere, as in the earlier sections: colour plus number plus name plus shape plus consistent position. Test the whole thing before it is built:

Pre-build wayfinding test:
  - greyscale the map and boards - still navigable?
  - CVD-simulate them (deuteran/protan/tritan)
  - check every sign's contrast and letter size
  - view the real paint under the real lamps on site
  - walk it with a first-time user and watch where
    they hesitate

That last step - watching a stranger try to find something - is worth more than any checklist, because wayfinding fails at the joins between signs, not usually at a single sign. And remember the maintenance horizon: paint fades, lamps get relamped to a different colour temperature, temporary signs breed and contradict the system. A colour code is a living thing that needs an owner and a manual, or it decays into the confusing patchwork we have all been lost in.

Done with this discipline, colour coding is a quietly brilliant public service: it lets a frightened visitor find the right ward, or a tired traveller find their car, without reading a word - while never leaving behind the people for whom colour alone would fail.