← Back to the Vibe Coding Lab
Vibe Coding Lab / Experiment 001 · Accessible journey-planning UX

Access Atlas: UX for More Predictable Rail Journeys.

An independent accessible-rail planning concept exploring a deceptively simple question: how can people compare journeys not only by duration, but by step-free access, interchange demands, assistance information and what is still unknown? Access Atlas puts those considerations beside the route — before someone commits to travelling.

Explore the interactive Access Atlas prototype

Fictional stations and journeys · not a real journey planner · demo choices aren't saved or sent

Fictional sampleWillow Quay → Fenmarket
Quickest sampleJourney A · 39 min
  1. StartWillow QuayStep-free in this scenariothen 18 min on the Estuary line
  2. Change · 7 minSaltmarsh RoadUnknown: check before travelthen 14 min on the Marsh line
  3. ArriveFenmarketStep-free in this scenario
Meets a step-free requirement hereJourney B · 52 min
  1. StartWillow QuayStep-free in this scenariothen 31 min on the Estuary line
  2. Change · 12 minHarbour JunctionStep-free in this scenariothen 9 min on the Valley line
  3. ArriveFenmarketStep-free in this scenario
Original illustration using invented stations. The quickest sample includes an unknown change at Saltmarsh Road; the slower one is step-free at every point in this fictional scenario. Neither is a real route.
Project
Access Atlas · Independent UX experiment
Design focus
Accessibility · Service design · Information confidence
Initial setting
UK rail · Fictional journey examples
Status
Product/content blueprint · Interactive concept prototype built (2026) · Fictional data · Not tested with users

Access Atlas is a new, independently developed portfolio product concept. It is not a National Rail, Passenger Assist, Southeastern, train-operator or regulator service, and is not affiliated with or endorsed by them. It does not provide real travel guidance, live access information or booked assistance.

A journey is more than a line on a map.

The quickest train is not necessarily the most workable journey. The UX challenge is to make access conditions, connection points and uncertainty visible early, while preserving choice and giving people a safe next step when information cannot be verified.

01 / Design opportunityIndependent problem framing · No new participant study

Fastest isn't always the right answer.

A train route might have a short journey time but a complicated change, uncertain lift availability or a gap in clear information about boarding assistance. A screen that shows only time and transfers can make important access decisions invisible. This concept tests a different information hierarchy: travel conditions first, then the trade-offs.

How might we

Help travellers understand whether a proposed rail journey works with their access requirements — and identify what still needs checking — without promising that travel conditions are guaranteed?

A portfolio design question, not a quote or validated finding from a participant.
Design response

Compare example routes by step-free access conditions, connection complexity, assistance touchpoints, information confidence and contingencies.

These are design hypotheses for an independent concept, not a description of an operator's deployed software.

Find / The relevant detail

Access conditions

Put the practical station/platform constraints beside the itinerary rather than bury them in another page.

Understand / The trade-off

Connections and alternatives

Show why an illustrative direct or lower-change journey may be preferable to one that's a little faster.

Verify / The uncertainty

What is known and unknown

Identify unverified lift status, missing details and actions the traveller can take before a real journey.

Ranked by time alone

  1. Journey A39 min · 1 change

    Includes unknown step-free information

  2. Journey B52 min · 1 change

    Step-free at every point in this scenario

With “step-free required”

  1. Journey B52 min · 1 change

    Meets the requirement in this scenario

Journey A is excluded, not hidden: Saltmarsh Road, platform 2 to platform 1: step-free access is unknown in this scenario.

Fictional sample journeys from Willow Quay to Fenmarket, taken from the prototype. The quickest journey isn't the one that meets the requirement, and unknown information is never counted as step-free.
02 / Public service contextPublished UK rail guidance · Not original Access Atlas research

The access information already matters.

The Office of Rail and Road (ORR) explains that train and station operators are required to maintain Accessible Travel Policies. ORR's public guidance highlights standardised information about step-free access, station staffing and facilities, alongside assistance and communication between stations. That public framework helps define which information a trustworthy planning interface should make legible. It does not validate this proposed design.

Regulator context

Station accessibility

ORR identifies access to accurate information about station facilities, staffing and step-free conditions as part of better journey planning.

ORR: Improving assisted travel

Passenger context

Assistance is a separate service

National Rail explains how Passenger Assist requests work, including help with boarding, alighting and station navigation. A request is not automatically a confirmed booking.

National Rail: Passenger Assist

Existing digital service

Don't reinvent a booking system

The Passenger Assistance app/website already lets travellers request assistance. Access Atlas proposes a clearer pre-journey decision layer, not a competing or fictional assistance confirmation flow.

National Rail: Passenger Assistance app

From public context to product decisions

  1. Public context

    Accurate information about station facilities, staffing and step-free access is part of better journey planning.

    ORR: Improving assisted travel (opens in a new tab)
    Design implication

    Put access conditions beside each journey, not on another page.

    In the prototype

    Every journey shows its step-free points, in words, at the start, each change and the end.

  2. Public context

    Passenger Assist handles requests for help with boarding, alighting and getting around stations; a request is not automatically a confirmed booking.

    National Rail: Passenger Assist (opens in a new tab)
    Design implication

    Hand off to the official service; never simulate a booking.

    In the prototype

    An assistance step with official links and no booking status at all.

  3. Public context

    An official app and website already exist for requesting assistance.

    National Rail: Passenger Assistance app (opens in a new tab)
    Design implication

    Don't reinvent the request; prepare the traveller for it.

    In the prototype

    A checklist of questions to take to official sources, labelled as fictional.

A design reasoning diagram. The left column summarises public guidance already cited on this page; the other columns are SP's design decisions, not research findings.

Evidence boundary: these are regulator and National Rail publications. No privately held research, passenger quotations, unpublished Southeastern findings, operator analytics, journey metrics or participant outcomes are reproduced or attributed to this concept.

03 / Inclusive UX principlesProposed design rules · To be tested

Personal needs, not assumptions.

01 / Needs, not labels

Ask about the journey

Let visitors choose functional planning preferences such as step-free travel, fewer changes or extra time at connections. Do not ask for a medical diagnosis or disability category.

02 / Accessible by design

More than one input method

Use labels, text, keyboard controls and readable route descriptions; never depend on a map, icon or colour alone to communicate access.

03 / Truthful uncertainty

Unknown is not accessible

Separate documented station facilities from unverified operational conditions, and avoid green “all clear” badges when data is missing.

04 / Traveller agency

Explain the recommendation

Compare time, interchanges and constraints; allow the person to weigh trade-offs rather than make a universal “best accessible route” claim.

05 / Respect the service

Assistance must be confirmed elsewhere

Show where to request and verify assistance with official providers; never imply a prototype action has booked it.

06 / Change is normal

Plan for disruption

Communicate what to re-check and illustrate an accessible alternative when a fictional lift or connection becomes unavailable.

The prototype asks about the journey

  • Step-free access at every station point?A hard requirement: never relaxed by the interface.
  • Prefer fewer changes?A preference: changes the order and explains why.
  • How much time to change trains?A preference: shorter changes are flagged, not hidden.

It never asks

  • Diagnosis, condition or disability category
  • Health details or medication
  • Location, account, contact details or travel history
The inputs built into the prototype. Choices stay in temporary page memory and disappear on restart or refresh.
04 / Information model & provenanceProposed trust architecture · No live data connection

Say what we know. Show what we don't.

A credible accessible planner needs to distinguish a station's published infrastructure information from today's operational status, the traveller's chosen preferences and the confirmation status of an assistance request. Blending those into one “accessible” score would be convenient but misleading.

Published facility information

Infrastructure facts

Station categories, relevant platform access and facilities would need authoritative current sources in a real service. In the prototype, every route and station fact is fictional and explicitly labelled.

Current operational conditions

Could be outdated or unknown

Working lifts, platform changes and disruptions require fresh, verified operational information. The demo must never invent a timestamp such as “updated live” or assert current status.

Personal planning preferences

Needs are user-controlled

Visitors may prefer step-free routes, fewer interchanges or more connection time. These preferences are not medical history and will remain in temporary demo state.

Assistance request status

A request is not a confirmation

A future genuine integration would need verified state from the relevant operator. This demo cannot request, book, acknowledge or confirm assistance.

Three communication states

Illustrative information available · Information unknown or unverified · Check with the official provider.

All demo conditions remain fictional; even a positive illustrative label is not a guarantee about a real station.
A product integrity rule

If no fictional route meets a chosen access constraint, clearly say “No matching example found” and offer a next step. Do not silently relax a hard accessibility preference.

A product rule for future prototyping, not an evaluated algorithm.

  • Step-free in this scenarioThe fictional data describes a step-free way through this point. Still not a guarantee: lifts and conditions on the day need checking.
  • Unknown: check before travelNo information. It is never counted as step-free, so a hard requirement excludes it.
  • Not step-free in this scenarioThe fictional data describes stairs, or the simulated outage has removed the step-free way.
The three information states used everywhere in the prototype. Each has its own shape and its own words, so meaning never depends on colour.
Information confidence for three fictional journeys from Willow Quay to Cedar Vale, as the prototype shows them.
JourneyStartChangeArrive
Journey A52 minStep-free in this scenarioWillow Quay, platform 1Step-free in this scenarioHarbour Junction, platform 1 to platform 3Step-free in this scenarioCedar Vale, platform 2
Journey B68 minStep-free in this scenarioWillow Quay, platform 2No changeStep-free in this scenarioCedar Vale, platform 2
Journey C58 minStep-free in this scenarioWillow Quay, platform 1Not step-free in this scenarioMill Street, platform 1 to platform 2Unknown: check before travelCedar Vale, platform 1

Station and interchange detail · four fictional cases

  • Harbour Junction · Lift between platforms

    Step-free in this scenario. Lift between platforms 1 and 3.

  • Mill Street · Stairs only

    Not step-free in this scenario. Footbridge with stairs only; no lift in this scenario.

  • Mill Street · Same-platform change

    Step-free in this scenario. Cross-platform change on the same island platform.

  • Saltmarsh Road · Not described

    Unknown: check before travel. No information about getting between platforms 1 and 2.

Original schematics of invented interchanges, drawn by the same code as the prototype. The written status beside each drawing carries the meaning; the drawings are not plans of real stations.
05 / Product definitionNew independent UX concept · Not launched

Journey planning with the conditions visible.

Access Atlas proposes a planning interface built around the access decisions that often disappear behind a route summary. Rather than optimising a journey to one opaque number, it reveals differences between illustrative options and helps a traveller prepare to verify the parts that matter.

Illustrative JTBD

When I'm comparing train journeys, help me understand which route is likely to work with my access requirements and what I still need to confirm before I leave.

A constructed design scenario, not a quotation from actual research participants.
First version's scope

Example journey search, functional access preferences, two or three fictional route comparisons, explicit unknowns, an official assistance-information handoff, a hypothetical disruption and a clear travel-preparation checklist.

No real journey planning, booking, timetable, payment, fare, lift-status API, operator integration or endorsed accessible-route recommendation.

Route choices and trade-offs · Cedar Vale → Fenmarket (fictional)

  • Journey A 33 min 1 change Step-free at every point in this scenario
  • Journey B 42 min 1 change Includes unknown step-free information
  • Journey C 49 min 0 changes Step-free at every point in this scenario
Three fictional journeys from the prototype. Time, changes and step-free status pull in different directions, so the interface explains the trade-off rather than issuing a single "best accessible route".

Information architecture of the built prototype

  1. Set up

    1. 1WelcomeFictional-data disclosure
    2. 2JourneyStations · swap · validation
    3. 3PreferencesHard requirement · preferences
  2. Decide

    1. 4CompareRanked journeys · exclusions · no-match
    2. 5DetailsPoint-by-point · interchanges · checks
  3. Prepare

    1. 6AssistanceOfficial handoff · no booking
    2. 7DisruptionSimulated lift outage · recovery
    3. 8ChecklistCopy · print · restart
Eight steps in three phases. Back keeps every choice; Restart clears all temporary demo state.
06 / End-to-end user flowDesigned future workflow · Not observed behaviour

Before travel, know what to check.

01 / Starting point

Enter an example journey

Choose from invented stations, such as Willow Quay and Cedar Vale. Show a prominent “fictional demo routes” banner and never use real timetables.

02 / Preferences

Describe how you'd like to travel

Set step-free travel as a required constraint, prefer fewer changes, or request more changeover time. Avoid diagnosing, classifying or collecting health details.

03 / Compare

See the trade-offs

Compare a fictional shorter one-change option with an illustrative longer direct option. Clearly disclose unknown lift or platform details rather than assigning fictional reliability scores.

04 / Inspect

Open a route's access story

Inspect each segment, a fictional station's accessibility note, connection demands and any unresolved questions.

05 / Prepare

Check assistance and facilities

Open the official Passenger Assist guidance or other official sources in a separate tab. The prototype must explain it cannot make or track a request.

06 / Disruption rehearsal

What if a lift is unavailable?

Activate a clearly labelled fictional lift disruption and see the route comparison respond. If the access condition becomes unknown, never leave a misleading positive route badge.

07 / Review

Take a preparation checklist

Review the fictional journey, required verifications and important official links. A browser-only copy/print feature can export this illustrative checklist without saving personal data.

Journey map · questions, steps and safeguards

  1. 01Plan
    Traveller question
    Can I get from here to there?
    Prototype step
    Journey
    Honesty safeguard
    Fictional stations only; identical stations are caught.
  2. 02Set needs
    Traveller question
    Can it work with how I travel?
    Prototype step
    Preferences
    Honesty safeguard
    Functional choices; no diagnosis or health questions.
  3. 03Compare
    Traveller question
    Which journey works, and why isn't the quickest listed?
    Prototype step
    Compare
    Honesty safeguard
    Exclusions are explained; unknown is never step-free.
  4. 04Inspect
    Traveller question
    What happens at the change?
    Prototype step
    Details
    Honesty safeguard
    Point-by-point text with the gaps that need verifying.
  5. 05Prepare
    Traveller question
    Who can help me on the day?
    Prototype step
    Assistance
    Honesty safeguard
    Official handoff; no fake booking or status.
  6. 06Rehearse
    Traveller question
    What if the lift is out?
    Prototype step
    Disruption
    Honesty safeguard
    A labelled simulation and an honest recovery or no-match.
  7. 07Take away
    Traveller question
    What do I still need to check?
    Prototype step
    Checklist
    Honesty safeguard
    Copy or print, labelled FICTIONAL DEMONSTRATION.
Proposed journey. The traveller questions are illustrative and were written for this portfolio; they are not participant quotes.

Journey examples, station names, routes, durations, interchanges and disruption conditions are entirely fictional and used only to test UX decisions. They must not be used to plan a real trip.

07 / Assistance service boundaryOfficial handoff · No fake requests

Plan here. Confirm with the provider.

National Rail's Passenger Assist service supports advance assistance requests, including help at stations and with boarding and alighting. The existing Passenger Assistance app and website can send a request for checking and confirmation by the relevant train company. Access Atlas should link to those official processes, not impersonate them. Read official Passenger Assist guidance.

What this concept can show

Explain the options

Which part of the fictional journey might involve station help, a ramp, a change of train or a question worth asking before travel.

What it cannot do

Send or verify assistance

The prototype cannot request, book, acknowledge or confirm real Passenger Assist services, guarantee a ramp or communicate with station staff.

  1. Access Atlas (this concept)Plan and prepareCompare fictional journeys, see unknowns, list what to ask.
  2. Access Atlas stops here
  3. Passenger Assist (official)Request assistanceThrough National Rail's official app or website.
  4. The train companyCheck and confirmA request is checked; it isn't confirmed automatically.
The assistance handoff built into the prototype. It shows no booking, acknowledgement or confirmation status because it cannot request assistance.
08 / Designing for changeHypothetical service-recovery scenario

When a route changes, so should the explanation.

Lift outages and platform alterations can change whether a station is usable for a particular trip. A responsible prototype should show the difference between a route that was previously described as step-free in fictional information and one whose hypothetical access conditions are now uncertain or unavailable.

Example fictional disruption

“The lift at Harbour Junction is unavailable in this scenario.”

A scripted demo event; NOT a real outage, alert, prediction or operator-supplied status.
Expected interface response

Update the route comparison, explain which illustrative transfer is affected, show a matching fictional alternative if one exists, and point to official sources before real travel.

Never promise an alternative is accessible without the information needed to verify it.

Simulated lift-disruption recovery, as built

  1. 1 · Before · Willow Quay → Cedar Vale

    • Journey A · 52 min meets the requirement
    • Journey B · 68 min meets the requirement
    • Journey C · 58 min excluded: not step-free or unknown

    Journey A is chosen. Step-free access is required.

  2. 2 · Simulation on

    • Journey A · 52 min excluded: simulated lift outage
    • Journey B · 68 min meets the requirement
    • Journey C · 58 min excluded: not step-free or unknown

    Journey A changes at Harbour Junction, so it is excluded and flagged.

  3. 3 · Recovery

    Switch to Journey B (68 min, 0 changes)

    The checklist updates and still lists what to verify, including the Cedar Vale lift on the day.

When nothing matches: from Willow Quay to Fenmarket, the simulation leaves no journey that meets the requirement. The prototype says so, keeps the requirement, and offers other stations, turning the simulation off, or assistance information.

Generated from the prototype's fictional scenario logic. The outage is switched on by the visitor; it is not a real alert or prediction.
09 / Interaction design and prototype briefPrototype built · Fictional data · Not yet tested with users

Turn the access question into an interaction.

This phase developed original low-fidelity wireframes, polished route-comparison screens and a real browser-based, offline-friendly interactive concept. Unlike a visual-only mockup, the demo controls genuinely change the fictional journey results and explanatory details.

2026 · Interactive concept prototype

Explore the interactive Access Atlas prototype

Eight steps from choosing fictional stations to a printable checklist, including a no-match case and a simulated lift outage. Every control works; every station and journey is invented.

Open the Access Atlas prototype

Really works in the browser

  • Station selection with swap and same-station validation
  • A step-free hard filter, plus fewer-changes and connection-time preferences that reorder and explain
  • Journey comparison with written exclusion reasons and a genuine no-match state
  • Point-by-point journey details and interchange drawings with text equivalents
  • A simulated lift outage that re-evaluates every journey and offers recovery
  • Copy and print of a labelled fictional checklist; Back and Restart

Fictional or out of scope

  • All stations, platforms, lines, durations and access notes
  • The lift outage: a simulation, not a real alert
  • No timetables, live status, routing of real journeys or GPS
  • No assistance requests, bookings or confirmation status
  • No accounts, storage, tracking or external data
Built / Journey setup

Example origin and destination

Selectable fictional stations with a swap control and clear error states. No location lookup, tracking or real station dataset.

Built / Access preferences

Hard constraints and preferences

Step-free travel as a required filter where applicable; fewer changes and extra transfer time as transparent comparison preferences.

Built / Explainable comparison

Route alternatives

Two or three clearly fictional options with a text-based journey breakdown. Never disguise a preference-based sort as a medical, safety or accessibility guarantee.

Built / Missing information

Unverified and unavailable states

Show when fictional route evidence is missing. Use labels, not colour alone, and provide a visible “what to check” note.

Built / Disruption

Scenario toggle and replan

A working “simulate lift outage” control updates the affected illustrative route, without inventing a live service alert.

Built / Prepare

Accessible travel checklist

Provide a simple copied or printable summary, clearly labelled as a fictional demo, plus working official external information links. No fake assistance-booking controls.

The interactive page is work/access-atlas-prototype.html, linked above. It was built with HTML, CSS and vanilla JavaScript and checked in the browser with automated keyboard, layout and scenario tests. It has not been tested with participants, and all of its data is fictional.

10 / UX evaluation and release-readinessPlans only · No recruited participants or operational integrations

Evaluate understanding, not just clicks.

A working prototype would enable real usability tasks, but the existence of a functional demo is not evidence that the planning concept helps passengers. The first research study should examine whether users can make informed choices, spot unverified information and understand that a sample itinerary is not a confirmed real journey.

Task 01 / Access constraints

Find a suitable example

Can a visitor find an illustrative route that meets the step-free requirement, or understand when no sample option qualifies?

Not yet run
Task 02 / Information confidence

Recognise the unknown

Can a visitor identify which fictional station details are unverified and what official information they'd need before travelling?

Not yet run
Task 03 / Assistance handoff

Separate planning from booking

Can a visitor explain why Access Atlas cannot confirm assistance, and find the actual official Passenger Assist process?

Not yet run
Task 04 / Recovery

Respond to a changed condition

Can a visitor recognise a simulated lift disruption and choose a reasonable next action instead of trusting outdated sample conditions?

Not yet run
Release gate / Real data

Authoritative, maintained feeds

Any real service would need appropriate permissions, dependable station/train data, timely updates, error monitoring and information ownership. None is connected today.

Future gate · not started
Release gate / Accessibility

Real-world review

Test with disabled and older travellers with varied requirements; ensure usable keyboard/screen-reader interaction and review service language with domain experts before a production claim.

Future gate · not started

Proposed evaluation measures: task completion, understanding of evidence uncertainty, error recovery, trust calibration and route-comparison comprehension. All are proposed; no participants, outcomes, usability scores, commercial impact or production readiness are claimed.

11 / Sources, authorship and limitationsPublished policy context · Original product concept · No private client research

Make the boundary as clear as the journey.

Original portfolio work

Independent design continuation

Problem framing, UX principles, fictional journey comparison, information-confidence model and an interactive concept prototype (built 2026, fictional data). These are new portfolio work, not recovered Southeastern project materials or verified participant findings.

Not claimed

No service or data partnership

No National Rail/operator affiliation, proprietary rail research, confirmed assistance booking, live timetable, working lift-status feed, real-time disruption coverage, route guarantee, validated evaluation or launched product.

All sample stations and route scenarios must be visibly fictional. This design is a UX exploration and cannot be used to plan, book or verify an actual train journey. For real travel, use current official operator, National Rail and Passenger Assist information.