The bay that mattered: why we added accessibility filters to Volta

The problem most mapping apps ignore

When you're building a unified map across 40+ UK charging networks, you're already solving for fragmentation. Networks have different tariffs, different speeds, different payment methods. Most apps flatten that chaos into a single interface and call it done.

But they miss something obvious: not every charger is equally usable for every driver. A bay marked as "available" on a busy forecourt means nothing if there's no accessible space. You can't optimise a journey or trust your arrival time if the infrastructure doesn't work for your body.

The accessible bay problem sits at the intersection of data reliability and real-world fairness. Network operators record whether bays exist. Most mapping tools don't surface that data, or surface it inconsistently. Even when they do, the information is often stale or incomplete. We realised early on that Volta's job wasn't just to show you chargers. It was to show you chargers you could actually use.

What accessibility filters do in Volta

In the map view, you can filter by accessible bays. Toggle it on. The map redraws. Locations without recorded accessible spaces fade. What remains are chargers where you know, before you leave home, that an accessible bay exists.

It's a small toggle. It changes everything about trust. A daily commuter doesn't have to arrive and improvise. A rideshare driver doesn't lose time hunting for a compliant space. A fleet manager doesn't schedule a charge at a location that won't work for every driver on the team.

The filter pulls from the underlying network data. Some operators report this more thoroughly than others. Some charger locations have been mapped for years; others are newer. We're transparent about that. The filter shows you what's recorded in the networks' own systems. If a bay is marked as accessible by the operator, it appears. If it's not recorded, the location filters out when you toggle accessibility on.

Why it took longer than we expected

You'd think adding a filter is straightforward. Show me only chargers with accessible bays. Done.

It wasn't. The 40+ networks we aggregate don't all use the same schema. Some record accessibility granularly. Some have a single "accessible bay" flag per location. Some don't record it at all. We spent weeks mapping which networks reported accessibility data and how consistently they updated it. We had conversations with operators about data quality. We made decisions about what to show when information was incomplete.

There was also a design question underneath: if you turn the filter on and a charger has one accessible bay that's currently occupied, should we still show it? We decided yes. You might be willing to wait, or circumstances might change by the time you arrive. But we flagged it clearly so you're not surprised.

The work was granular. Unglamorous. But it mattered because the alternative was shipping a feature that would silently fail for the drivers who needed it most.

Who this actually helps

The obvious answer: wheelchair-using drivers, people with mobility limitations, parents with prams or buggies, anyone who needs extra space or a level approach to the charger.

Less obvious but real: drivers with invisible disabilities who need to plan routes carefully to avoid unnecessary physical strain. Older drivers who prefer not to walk far from their car. Drivers with health conditions that make accessibility non-negotiable.

And there's a fleet angle. A business running a mixed team of drivers can't assume everyone has the same mobility requirements. If you're managing a fleet through Volta, accessibility filtering lets you choose routes and chargers that work for all your people. That's not charity. That's operational sense.

What we got wrong, and what comes next

The email that sparked this arrived early. We shipped the filter. Then we learned that some drivers were still arriving at chargers marked accessible only to find the bay blocked or missing. Not because the network lied. Because things change. A bay gets cordoned off for maintenance. Parking rules shift. The data ages.

This taught us that accessibility filters are only as good as the data behind them. We now remind drivers to check in via Arrive-to-charge when they reach a location. That real-time confirmation helps us spot when recorded data and ground truth drift apart. If a bay is consistently reported as inaccessible by drivers who arrive, we flag it with the operator.

We're also watching the networks themselves. Some are improving how they report accessibility. Some are slower. We're honest about that inconsistency. If a network's data is patchy, we say so in the app.

The feature is live now. But it's not finished. It's iterating because the drivers using it keep telling us when it works and when it doesn't.