UI/UX design for accessible journey planning in Delhi

Help riders see where a journey is step-free, where information is missing and how to check the next leg before leaving.

See the route comparison test
Light line illustration of India Gate and the stepped galleries of Agrasen ki Baoli in Delhi.

Give riders a route they can assess

A fictional trip with two Central Delhi interchange options

Delhi Metro Rail Corporation describes accessibility features such as ramps, tactile paths and lifts. This fictional route example is for a journey-planning team using its own approved data. GreyBath provides UI/UX design remotely.

Break the trip into checks at entry, transfer and exit

A rider asks for a step-free journey. In a fictional example, option A takes 26 minutes but has an unknown transfer lift status. Option B takes 34 minutes and each leg was verified at 10:15. Present the extra eight minutes alongside the difference in certainty.

Keep a missing status visible at the decision point

When a scheduled update fails, retain the stamp of the last verified report and label the current status unknown. Put the warning next to the interchange step and expose it in the screen reader order.

Make the fallback easy to find

Show the check-this-route action, then offer the verified alternative. Let the rider return to the original origin and destination without starting a new search.

Bring riders and the team that maintains the information

Include riders who use step-free routes and the editor responsible for the status messages. Observe how each person checks the same trip.

Mobility product teams

Choose the journey and decide who can approve facts before they are visible to riders.

Journey information editors

Confirm where facility data comes from and how stale or missing information is marked.

Riders and accessibility reviewers

Compare two possible trips and check whether the available information supports a decision.

Engineering and support teams

Use the states to scope data integrations and the help path when details are unavailable.

Compare two routes when one lift status is unknown

  1. Trace a rider’s route

    Break one example into entrance, platform, transfer and exit. Record what the rider needs to check at each stage.

  2. Prototype the decision

    Have the rider compare the 26- and 34-minute trips. Ask which step is unresolved and where they would check it.

  3. Test a status change

    Change the transfer status while the route is open. Check that the selection remains clear and the warning is available by keyboard and screen reader.

Agree what the interface can confirm

Scope the prototype to two fictional routes and their critical steps. The project owner is responsible for data permission, accessibility facts and updates to facility information.

Discuss your project
Facility data coverage

Agree which entrances, lifts and transfers have evidence and how often the source refreshes.

Stale information

Set the expiry rule for a confirmation and name the team that reviews failures.

Interface and physical access

Test the interface with users and coordinate any statements about actual route access with the data owner.

Questions about accessible journey interfaces

Ask us something else
Can the planner guarantee an accessible route?

The interface can display supported and verified route information. A project owner must maintain the underlying facility data and decide what can be confirmed.

How should a stale lift update appear?

Show the last verified update and keep the current status as unknown until a reliable update arrives.

Do we need real-time data for a first prototype?

Start with clearly marked sample records. Live data integration can be scoped when the source and update rules are agreed.

How do we test if riders understand the warning?

Ask a rider to identify the affected transfer and explain their next step without prompting. Repeat with a screen reader and on mobile.

What should we bring to discovery?

Bring one route, a known data gap and the team responsible for correcting a facility update.

Test the whole journey before building the planner