Skip to content

The Shape of Access 4: Perceptible Information

The story

This story is fictional. The failure in it is common.

The station had been renovated the previous spring: concrete surfaces, quiet signage, screens hung from the ceiling. Mira liked the calm of it.

The departure board listed the 16:48 to Glasgow on Platform 3. She stepped away and came back seven minutes before departure. Platform 3 was empty.

The main board still said On Time. A smaller screen behind the help desk said Platform 5. There had been no announcement, no flashing notice, no alert on her phone.

A member of staff told her most passengers check their apps now.

She was not upset. She felt uninvited.

That evening she wrote: “I can read. I can hear. But I cannot be everywhere at once.”

The principle

Principle 4 of Universal Design (Center for Universal Design, NC State, 1997): the design communicates necessary information effectively to the user, regardless of ambient conditions or the user’s sensory abilities.

Guideline What it asks Held at this station?
4a Use different modes (pictorial, verbal, tactile) for redundant presentation of essential information No. One visual channel was updated; the audible and digital channels stayed silent
4b Provide adequate contrast between essential information and its surroundings No. A changed platform looked the same as an unchanged one
4c Maximise the legibility of essential information Partly. The correct information existed, on a screen facing staff
4e Provide compatibility with devices used by people with sensory limitations No. The fallback offered was an app, with no alert sent

Guideline 4a is the one the story is usually read against. It has a condition that is rarely written down: redundancy only helps when every channel carries the same information. Here the channels disagreed.

Service blueprint: current state

The passenger journey breaks at phase 3, while Mira is off the platform. Nothing in the frontstage tells her to come back. Rows marked (inferred) are deduced from the story, not observed.

Layer 1. Checks the board 2. Steps away 3. Platform changes 4. Returns 5. Asks staff
Evidence Main board: 16:48 Glasgow, Platform 3 None Help-desk screen: Platform 5. Main board: On Time Main board still On Time. Platform 3 empty A spoken reply
Passenger actions Reads the board, notes the platform Leaves the platform area Absent; nothing prompts a return Arrives 7 minutes before departure Asks what happened
Line of interaction
Frontstage Main departure board None No announcement, no visual flag, no app alert. F1 None “Most passengers check their apps now.” F3
Line of visibility
Backstage None None Train moved to Platform 5; change reaches the staff-side screen (inferred) Train waits at Platform 5 (inferred) No recovery step: next train, ticket validity, assistance (inferred)
Line of internal interaction
Support processes Public information feed None Public feed, announcements and app not triggered by the change (inferred). F2 None App treated as the main channel for changes (inferred)

1. Checks the board

  • Evidence Main board: 16:48 Glasgow, Platform 3
  • Passenger actions Reads the board, notes the platform
  • Line of interaction
  • Frontstage Main departure board
  • Line of internal interaction
  • Support processes Public information feed

2. Steps away

  • Passenger actions Leaves the platform area

3. Platform changes

  • Evidence Help-desk screen: Platform 5. Main board: On Time
  • Passenger actions Absent; nothing prompts a return
  • Line of interaction
  • Frontstage No announcement, no visual flag, no app alert. F1
  • Line of visibility
  • Backstage Train moved to Platform 5; change reaches the staff-side screen (inferred)
  • Line of internal interaction
  • Support processes Public feed, announcements and app not triggered by the change (inferred). F2

4. Returns

  • Evidence Main board still On Time. Platform 3 empty
  • Passenger actions Arrives 7 minutes before departure
  • Line of visibility
  • Backstage Train waits at Platform 5 (inferred)

5. Asks staff

  • Evidence A spoken reply
  • Passenger actions Asks what happened
  • Line of interaction
  • Frontstage “Most passengers check their apps now.” F3
  • Line of visibility
  • Backstage No recovery step: next train, ticket validity, assistance (inferred)
  • Line of internal interaction
  • Support processes App treated as the main channel for changes (inferred)

F1 Critical: the passenger is on the wrong platform minutes before departure. F2 Critical: root cause of F1. F3 Major: no recovery after the failure.

Where it broke

The station did not lack channels. It had four, and only one carried the change: a screen facing staff.

One platform change reached one screen out of fourOne platform change reached one screen out of fourStory 4, current state. Backstage links are inferred from the story.BackstageWhat passengers and staff seePlatform changePlatform 3 to Platform 516:48 to Glasgowupdatednot updatednot triggerednot sentHelp-desk screenShows Platform 5, but faces staffMain departure boardStill shows Platform 3, On TimeStation announcementNone madeApp push alertNone sentWrong or silentCorrect, but out of the passenger’s sight
One platform change reached one screen out of four. The correct platform reached a screen facing staff; the three channels facing passengers stayed wrong or silent.

F2: the change lived in one system. A platform change is a single event, but it reached one screen and stopped. Board, announcements and app run on separate triggers, and nobody triggered them. Adding a fifth channel would not fix this. Redundancy repeats whatever the shared record holds, and here the public record was wrong.

F1: steady state and changed state looked the same. “On Time” told the truth about the clock and hid the platform. A board that does not flag a change asks every passenger to re-read it, at the right moment, from the right place.

F3: the app became the strategy by default. “Most passengers check their apps now” shifts the work of watching onto the passenger. Mira’s line names the cost exactly. An app asks for constant attention; a station can broadcast.

For Mira this was an inconvenience. The same failure is total for others:

  • A Deaf passenger relies on the board, and the board was wrong.
  • A blind passenger relies on announcements, and there were none.
  • A passenger without a smartphone or data had no fallback at all.

What the principle needs here is consistency, not volume.

Standards and duties

These references show where the idea already appears in EU law and European standards. They illustrate the concept; they are not a compliance assessment.

Instrument Type What it asks that this station missed
European Accessibility Act, Directive (EU) 2019/882 Law Accessible delivery of transport service information, including real-time travel information
Rail Passengers’ Rights Regulation (EU) 2021/782 Law Travel information during the journey, including information for disabled passengers and passengers with reduced mobility
PRM TSI, Regulation (EU) 1300/2014 Technical regulation Visual and audible passenger information in stations, including dynamic information
EN 16584-2 Design standard Information given in visual, audible and, where needed, tactile form
EN 301 549 Harmonised standard Covers the app and website; its clauses follow WCAG. WCAG 4.1.3 Status Messages: a change must be announced to assistive technology without moving focus. It covers how an alert is presented, not whether one is sent

What good looks like

Fix the record first, then the channels. Frontstage fixes on their own would broadcast the same wrong information more loudly.

Fix Fail point Layer Type Likely owner
A platform change is one event that publishes to every channel at once: boards, announcements, app, help desk F2 Support processes Structural Station operator and information systems
The board marks a change for the time left before departure (“Now Platform 5, changed”), not only the new number F1 Frontstage Quick Station operator
Each change triggers an announcement, a visual flag and an alert to passengers booked on that train F1 Frontstage Quick, once F2 is fixed Station and train operator
Staff have a recovery script: acknowledge, next train, ticket validity, assistance offered F3 Backstage Quick Station operator, staff training
The app announces the change to screen readers (WCAG 4.1.3), and alerts work without an account for a single journey F1 Frontstage Structural Train operator, digital team

The first row is the only one that removes the cause. The others make sure the truth reaches every passenger once it exists.

How to test for it

This failure is invisible to a screen audit. It only shows up when you test the service while something is changing.

  1. Channel parity check. Make a platform change in a test environment, or watch a live one. Record when it appears on each channel: main board, help-desk screen, announcement, app. Any channel that never updates is F2.
  2. Service safari during disruption. Go with Deaf, blind and low-vision passengers, recruited through disability-led organisations and paid. Each person relies on their own main channel, and the gaps show up as missed trains, not opinions.
  3. Complaint and refund tagging. Tag missed-train complaints and ticket-extension requests that mention a platform change. This sizes the problem without new research.
  4. App alert test with VoiceOver and TalkBack. Check that a change is announced without moving focus (WCAG 4.1.3), and that someone who opens the app late can still find it.

Redundancy multiplies whatever the system knows. Here it knew two different things.

Sources

Previous
Next