The principles on this page guide the work today. The capabilities described as “planned” are future intentions, are not available in the current release, and do not guarantee a feature or delivery date.
Accessibility is part of the whole journey
Access needs can shape how someone plans, moves through an airport, receives an update, makes a connection, reaches an accessible transfer and arrives at a suitable stay. Atlas aims to reduce uncertainty without taking control away from the traveller.
Our roadmap considers mobility, visual, hearing, cognitive and neurodivergent experiences. We intend to develop it with disabled people, not simply for them.
Our design principles today
Clarity before complexity
Important information should be easy to find, written in plain language and presented without unnecessary pressure or distraction.
Choice and control
Travellers should choose how information is presented and whether accessibility preferences are saved, used or shared.
Support without assumptions
Atlas should not infer what someone can do or what assistance they need. Disabled travellers are the experts in their own journeys.
The whole journey matters
A disruption can affect an accessible transfer, suitable room, medication timing, rest period or support arrangement—not only the flight.
Confirmation must be honest
A request, reminder or draft handoff is not a confirmed service. Only the responsible provider can confirm assistance.
Calm is functional
Predictable layouts, clear time cues and one useful next step can reduce cognitive load and travel anxiety.
Planned accessibility capabilities
Scope and timing may change as we test with travellers and understand what dependable airport, airline, mapping and transport data is available.
Mobility and physical access
- Optional mobility preferences without repeated re-entry
- Step-free routes, rest points and longer transfer timing
- Accessible transport and room requirements considered in alternatives
- Knock-on effects when a delay changes an accessible connection
Visual access
- Scalable type and strong colour contrast
- Information that does not rely on colour alone
- Screen-reader structure and meaningful labels
- Voice-led journey summaries and spoken updates
Hearing access
- Visual equivalents for important audio alerts
- Optional haptic patterns for time-sensitive changes
- Written summaries of spoken or complex information
- Customisable visual, haptic and text combinations
Cognitive and neurodivergent access
- Calm, step-by-step journey views
- Plain-language explanations of what changed
- Reduced-motion and reduced-distraction options
- Predictable layouts, clear time cues and transition prompts
Airport wayfinding
- Routes through security, passport control and departures where required
- Step-free and lower-sensory path choices when supported by airport data
- Extra time for lifts, assistance points and rest stops
- Clear distinction between concept timing and live airport information
Reducing travel anxiety
- A clear “what happens next” view after disruption
- Confirmed, likely and waiting states kept separate
- Optional medication, rest or equipment-charging prompts
- Permission-based journey summaries for a companion or support worker
Travel-assistance handoffs
Where a future integration supports it, Atlas may help a traveller prepare or pass relevant assistance details to an airline, airport, transfer provider, accommodation provider or human support team.
Before anything is shared, the traveller should be shown what information will be shared, who will receive it and why it is needed. The status should then be precise:
The request has left Atlas. It is not yet evidence that the provider has received or accepted it.
The provider has acknowledged the request. This may still differ from a confirmed service arrangement.
The responsible provider has explicitly confirmed the service or arrangement.
The traveller may need to contact the provider directly or check a time-sensitive requirement.
Privacy, consent and sensitive preferences
Accessibility information can be highly personal and may reveal health or disability information. Our planned approach is to:
- ask for explicit consent before saving or sharing a sensitive accessibility preference where required;
- collect only the information needed for the feature a traveller chooses;
- keep preferences optional and editable;
- avoid sharing accessibility information by default;
- show exactly what will be shared before a handoff; and
- provide controls to withdraw consent or delete saved information, subject to legal or operational requirements.
Accessibility preferences should not be used to make assumptions about a traveller or to limit the options shown to them.
Accessibility of this website
The current website uses semantic headings, keyboard-visible focus, a skip link, responsive layouts, scalable system type, labelled interactive controls and reduced-motion handling. Content remains available if the optional reveal animation or roadmap interaction does not run.
The website has not yet been independently audited, so we are not claiming conformance with a particular Web Content Accessibility Guidelines level. We plan to test more formally and publish known limitations as Atlas develops.
Help shape the roadmap
Good accessibility comes from research with people who have different lived experiences. If you would like to share feedback or take part in future accessibility research, email huseyin@ucab.co.uk.
This roadmap describes current intentions, not a guarantee of specific features or delivery dates. We will publish clearer availability information as features are tested and released.