Accessibility statement

Built for every Nigerian. On every phone. On every network.

Travel, transport and logistics should be usable by everyone — including people living with disabilities, people using assistive technologies, and the millions accessing the internet on older phones and patchy networks. That's the standard we hold ourselves to, and this page explains how — honestly, including where we're not there yet.

🔄 Reviewed: May 2026 📐 Reference: WCAG principles 💬 Feedback: always open below
Our commitment

Who we design for

Accessibility isn't a checkbox — it's a promise to specific people. These are the users we actively design and test for, across mobile, desktop, booking flows and support channels.

Visual impairments

High-contrast text, screen-reader compatibility, scalable type and meaningful image descriptions.

Hearing impairments

Nothing on Travo requires audio — every booking, update and support conversation works fully in text.

Mobility limitations

Keyboard navigation, generous touch targets, and services — deliveries, errands, pickups — that bring the world to your door.

Cognitive accessibility

Plain language, one-thing-at-a-time forms, logical page structure and no dark patterns rushing your decisions.

Temporary challenges

A broken arm, a cracked screen, eye surgery — accessibility helps everyone at some point, not just some people always.

Slow networks & older devices

Light pages, minimal clutter and low-bandwidth channels — because access includes affording the data to access.

In practice

What we build toward

An honest verb, chosen deliberately: accessibility is continuous work, not a finished certificate. These are the standards we hold our pages and flows to.

📖 Readable structure

  • Clear headings in a logical hierarchy
  • Readable font sizes that scale with your settings
  • Simple navigation, consistent across every page
  • Plain language over jargon

📱 Mobile-first experience

  • Optimised for Android, iPhone and tablets
  • Booking, tracking and support built for one thumb
  • Layouts that reflow, never pinch-and-squint

⌨️ Keyboard & assistive technology

  • Keyboard navigation with visible focus indicators
  • Screen-reader compatibility work across key flows
  • Zoom and text-scaling support
  • Reduced-motion support for vestibular comfort

📝 Clear forms & bookings

  • Labelled fields — pickup, drop-off, schedules — that say what they need
  • Short steps instead of walls of inputs
  • Quotes and totals shown before you commit

🔍 This very page practices it: a skip-to-content link, semantic landmarks and headings, visible keyboard focus outlines, reduced-motion support, alt text on meaningful images and decorative icons hidden from screen readers. If you find something on it that fails you, the form below reaches the people who can fix it.

Access includes affordability

Designed for Nigerian internet realities

Accessibility statements written in Silicon Valley assume fibre and flagships. Ours assumes what's actually true for millions of our users:

  • Slower mobile internet — so pages load light and fast, without heavy scripts fighting your connection
  • Older smartphones — the platform works on the Android in your hand, not next year's model
  • Limited bandwidth — clean layouts, no autoplay, no unnecessary clutter burning your data
  • Intermittent connections — short forms that don't lose your work when the network blinks
The honest part

Where we're not there yet

Digital platforms evolve constantly, and some parts of our ecosystem may not yet meet every accessibility standard at all times. We'd rather name them than pretend — the same honesty policy as our sustainability ledger.

Each of these is on the review list, and your reports move items up it.

Known gaps under active review

  • Older content pages that predate our current design standards
  • Third-party integrations we don't fully control
  • Embedded booking systems from partners
  • External payment interfaces
  • Partner tools outside our direct control
Tell us what failed you

Accessibility feedback goes straight to the top of the queue

If any part of Travo blocked you — a form a screen reader couldn't parse, a button too small to tap, a page too heavy to load, a booking you couldn't finish — we want the details. Three pieces of information make a report actionable: the page, your device and browser, and what happened.

And if the website is the barrier itself: skip it entirely. Our support team will complete any booking with you directly by message.

Accessibility is never finished. Neither are we.

As Travo grows across Nigeria and beyond, we keep reviewing standards, testing with real devices on real networks, and acting on your feedback — because a platform for everyone has to actually work for everyone.

Send accessibility feedback Get help with a booking
WhatsApp Chat