For riders & accessibility
What a Rider Sees, on a Phone, Computer or Tablet.
A map on your website with your vehicles on it. Where each one is right now, and when that position was measured. Nothing to download and no account.
Route 1 · Downtown Loop
- Bus 14on route · 12 s ago
- Bus 22on route · 2 min 30 s ago
- Bus 31no data since 3:42 PM
- Bus 7no data today
Positions, not predictions
The map answers one question: where is the bus right now, and how fresh is that. Positions are under 90 seconds old in normal service. We don't tell a rider how long to wait, because we don't know.
Readable as a list, not only as a map
Every vehicle on the map is also a row of text with its own status, so a screen reader or a rider on a slow connection gets the same information in the same order.
The one thing we don't do yet
The map refreshes itself and has no pause control, which WCAG 2.2.2 requires. It is the one criterion our conformance report lists as not met, it is built before the first paid deployment, and you are reading it here rather than finding it yourself.
Thumb-sized targets, high contrast
Checked at the narrowest real phone width, in light and dark, with visible focus rings for keyboard use.
Why This Is Your Compliance Problem, and Why We've Taken It
ADA Title II obligations attach to your web content, including content you provide through a contract with a vendor. A rider-facing map on your site is your web content. If it isn't accessible, that's your exposure, not ours.
So we build to WCAG 2.1 AA and publish a conformance report (a VPAT-format ACR) that your IT reviewer can read and attach to a file. Not a claim in a sales deck. A document, with the failures listed too.
Put It In Front Of Your Riders For 60 Days and See.
Book a pilot