TAGO
Region
EN
Log inFind rides
RidesTransitEventsDriveSafetyAboutHelp
Region
Log in

Accessibility Statement

Operated by
Tago Rides, Inc., a Delaware corporation
Last updated
August 1, 2026
Effective date
August 1, 2026
Applies to
the TAGO iOS app and www.tagorides.com
Contact
support@tagorides.com

TAGO is built by a very small team, and this statement is written the way the rest of our documents are: it tells you what actually works today, and it names what does not. We would rather you find the gaps here than find them halfway through booking a ride.

Two different things are described below, and it is worth keeping them apart:

  1. Accessibility of the app — whether you can use TAGO with a screen reader, with larger text, with a switch or a keyboard. That is §2 and §3.
  2. Accessibility of the ride — whether the car that turns up fits you. That is §4, and it is a product feature, not a compliance statement.

Our target is WCAG 2.2 Level AA on the website and Apple's iOS accessibility guidelines in the app. We have not reached it everywhere, and we have not been independently audited. §3 is the honest list.

We are committed to making TAGO usable by as many people as possible, including people who use screen readers, magnification, larger text, reduced motion, keyboard-only or switch input, or voice control.

We are not claiming conformance. A conformance claim means an audit, and we have not had one. What we can tell you is what we have built, what we have measured, and what we know is missing. When a gap here is closed, this page changes and the "last updated" date moves.

Standards we are working to:

  • Website — WCAG 2.2 Level AA.
  • iOS app — Apple's Human Interface Guidelines for accessibility, which is what VoiceOver, Dynamic Type, Reduce Motion and the rest are defined against.
  • Keyboard. Every interactive control can be reached and operated with a keyboard. A "Skip to content" link is the first thing in the page and moves focus, not just the scroll position — so it actually works for a screen-reader user, which the scroll-only version does not.
  • Visible focus. Focus outlines are drawn on keyboard focus and are not removed.
  • The date picker is fully keyboard-operable. Arrow keys move by day, it uses a roving tab stop rather than trapping you in a grid of thirty buttons, Escape closes it, and focus returns to the field you opened it from.
  • Screen readers. Structural landmarks, headings in order, labelled controls, and decorative graphics hidden from the accessibility tree rather than read out as noise. Content that changes without a page load — search results, form errors — is announced.
  • Reduced motion is respected. If your system is set to reduce motion, the reveal animations, the counters and the moving route lines stop moving. This is honoured in every place the site animates, not just some of them.
  • Contrast. Body text and interface controls are checked against the WCAG minimums — 4.5:1 for text, and 3:1 for the borders of buttons and inputs, which is the one most sites miss. We measure this against rendered pixels, not against what the design file says.
  • Both light and dark themes are styled and checked, and the site follows your system setting unless you override it.
  • No motion or colour is the only way information is conveyed on the marketing site — anything shown by colour is also shown by text or shape.
  • No third-party scripts, which also means no injected overlay widget. See §3.4 for why that is deliberate.
  • VoiceOver. Controls throughout the app carry spoken labels, and groups of elements are combined so VoiceOver reads a card as one thing instead of six fragments.
  • Reduce Motion is respected throughout. This is the single best-supported accessibility feature in the app — the animated transitions, the map camera moves and the live-ride motion all check your Reduce Motion setting and fall back to a still presentation. It is honoured in well over a hundred places.
  • Standard iOS controls. Most of the app is built from standard SwiftUI components, so system behaviours you rely on — VoiceOver gestures, Voice Control, Switch Control, Full Keyboard Access, Zoom — generally work without us having to reimplement them.
  • Colour and contrast follow a single design token set with light and dark variants, rather than hard-coded colours scattered through the app.

3. What does not work yet — the honest list#

If you have increased the text size on your iPhone, most of the TAGO app will ignore you. The app was built with fixed type sizes — we counted 1,433 fixed-size text styles against 29 that scale with your setting. Larger Accessibility Text Sizes are not supported at all.

Where text is too long for its space, the app currently shrinks it to fit, which is exactly the wrong behaviour for someone who needs it bigger.

We are not going to dress this up: this is the most significant accessibility defect in TAGO, it affects a large number of people, and fixing it is a rebuild of the app's typography rather than a patch. It is on our roadmap. Until it lands, system-wide Zoom and the magnifier are the workarounds, and they are poor substitutes.

  • Screen-reader hints are sparse. Controls are labelled, but few carry the extra hint that explains what happens when you activate them. Some multi-step flows — publishing a trip, the offer chooser — will be harder to follow with VoiceOver than they should be.
  • We do not support "Differentiate Without Color." Some states, such as ride status colours, are distinguished largely by colour. Most also carry text, but we have not verified all of them.
  • Live, moving content — a driver's position updating during a ride — is not announced in a controlled way to screen readers.
  • The map is the least accessible part of the app. A map is a visual medium, and we have not built a non-visual equivalent for it. Addresses, times and status are all available as text elsewhere in the same screen.
  • No end-to-end screen-reader testing has been done by a person who relies on one. We have used VoiceOver ourselves. That is not the same thing, and we know it.
  • Not independently audited. Our checks are our own.
  • Some complex visuals — the animated route diagrams — convey their meaning visually and are hidden from screen readers with a text alternative nearby rather than being made fully navigable.
  • Some third-party content, such as an embedded map, is outside our control and may not meet the same standard.

We will not install an "accessibility overlay" widget — one of those floating-icon products that promises instant compliance. Disabled users' own organisations have repeatedly said these tools interfere with the screen readers and settings people already use, and they do not fix the underlying problems. We would rather have a shorter list of real fixes than a badge.

This is a different thing from the app being usable, and it matters more on the day you are travelling.

TAGO does not own cars and does not employ drivers. Every car is a private person's own car. So we cannot promise you an accessible vehicle. What we can do is let drivers state what their car actually has, let you say what you need, and match on those facts instead of on assumptions:

  • Wheelchair space — whether the car can carry a wheelchair.
  • Trunk space — whether there is room for a rollator, a folded chair or other equipment.
  • Accessibility needs on your profile — what you need, recorded once, so you do not have to explain it to every driver.

Two honest limits.

First, these are declarations, not inspections. A driver ticks a box; we do not send anyone to measure the car. Treat it as the driver's word, and confirm in the chat before the trip if it matters.

Second, your accessibility information is health-adjacent, and we treat it that way. It is deliberately kept out of anything the wider network can see, and is released only to the person you are actually travelling with. The Privacy Policy §4.3 says exactly who sees it.

Service animals. A driver may not refuse a rider because of a service animal. That is in our Community Guidelines §2, and refusing is grounds for suspension.

  • A caregiver travels free. Always, on any trip. There is no form to fill in and no approval step — it is built into how the cost share is calculated.
  • You can add a companion to any trip, subject to the seats actually being in the car.
  • If you are booking on someone else's behalf, please read Terms §11 — you are responsible for having their permission to give us their details.

Email support@tagorides.com. Please put "Accessibility" in the subject line so it is routed properly.

The more of this you can tell us, the faster it gets fixed — but send it even if you can only answer the first question:

  1. What you were trying to do, and where.
  2. Whether you were on the iPhone app or the website.
  3. What assistive technology you use, if any — VoiceOver, Zoom, Switch Control, larger text, a keyboard only, a screen reader on the web.

What happens then. We aim to acknowledge you within 5 business days, and to tell you either how to work around it now or when we expect to fix it. If a fix is going to take a while, we will say so rather than go quiet.

If a barrier is stopping you from completing something time-sensitive, say so and we will help you directly — including doing it for you at our end where we can.

If our response does not resolve it, you can escalate:

  • Write to support@tagorides.com with "Accessibility complaint" in the subject. It will be read by someone with the authority to act on it.
  • You may also contact the U.S. Department of Justice ADA Information Line at (800) 514-0301 (TTY (833) 610-1264), or the California Department of Rehabilitation.
  • Nothing in this statement, and nothing in our Terms, takes away a right you have under the Americans with Disabilities Act, the California Unruh Civil Rights Act, or any other accessibility law.

This statement was prepared on 1 August 2026 by reviewing TAGO's own source code, not by filling in a template. The figures in §3.1 are counted from the app's own code. When we say something works "in over a hundred places", that is a count.

It will go stale, and that is the risk with a page like this. We review it when we ship anything that touches typography, navigation or the design system, and at minimum once every six months. If you find a claim here that is not true of the app in your hands, that is a bug — tell us at support@tagorides.com and we will correct the page as well as the app.

Related documents: Terms of Service · Privacy Policy · Community Guidelines

Ride mode