Why we built ARK: the gap in accessible transportation

Standard ride-hailing apps weren't built for riders with disabilities. They were built for the median case and accessibility was bolted on later — if at all.

The result: wheelchair-accessible vehicles (WAVs) get listed as "optional extras" with a surcharge. Riders are forced to repeat their accessibility needs on every single booking. Vehicle equipment is unverified — a driver can list a WAV and show up without the tie-down system.

We know this because we talked to hundreds of riders across Canada before writing a line of code.

The three problems we set out to solve

1. The accessibility surcharge. Using a ramp or travelling with a service animal should cost the same as any other ride. We built ARK's pricing model so that WAV equipment is factored into the base fare — not charged as an add-on.
2. Repeating your needs every booking. Set your accessibility profile once. Every ride request automatically filters to eligible vehicles. You never answer the same questions twice.
3. Unverified equipment. Every ARK driver submits vehicle documentation as part of onboarding — including the specific accessibility equipment on the vehicle. Our admin team verifies before approval. Drivers cannot list equipment they don't have.

ARK is built from the ground up for this. The accessible experience isn't a feature — it's the whole product.