How California’s Robotaxi Law Forces Driverless Cars to Answer to Police on July 1

Starting July 1, 2026, the driverless cars rolling through California streets have to do something they could not reliably do before: respond to the police officer or firefighter standing next to them. A state law takes effect that day requiring every autonomous vehicle operating without a human in the cabin to connect a first responder with a live, trained human operator within 30 seconds, and to pull its entire fleet out of an emergency zone within two minutes of being told to. For the millions of Californians who now share the road with robotaxis from companies like Waymo, it is the clearest set of rules yet for what happens when a self-driving car meets a crash scene, a fire, or a traffic stop.

The change comes from Assembly Bill 1777, written into the California Vehicle Code as Section 38751. It does not touch how the cars drive themselves. Instead it fixes a problem police and fire crews have complained about since robotaxis first reached public streets: a car with no driver and no obvious way to reach anyone in charge, sitting in the middle of an emergency. Here is what the law actually demands, why it exists, and what it means if you live in or drive through a city where these vehicles operate.

What Changes for Driverless Cars on July 1

Section 38751 applies to any manufacturer whose vehicles can run on public roads with no human driver inside. From July 1 those companies must meet four specific requirements, each tied to a measurable deadline.

The first is a dedicated emergency telephone line that operates whenever the vehicles are on public roads. A remote human operator has to answer within 30 seconds and must have the authority and the technical ability to immobilize or move a vehicle when an emergency official asks. The second is a two-way voice device built into each car so that a police officer or firefighter standing at the curb can speak directly to that remote operator, again with contact established within 30 seconds.

The third requirement covers physical controls. If a vehicle has a manual override system, law enforcement and firefighters must be able to reach and use it during an emergency, and the manufacturer has to provide ongoing training and up to date materials so responders know how to operate it safely. The fourth is emergency geofencing. When an official sends a geofencing message marking an area to clear or avoid, the company must direct its fleet to comply within two minutes.

These are not voluntary best practices. Section 38751 has teeth because the California Department of Motor Vehicles can refuse to renew, reinstate or expand a company’s permit unless it certifies full compliance. An operational lapse can trigger investigations, new permit conditions, or a suspension that halts California operations entirely. Missed 30-second or two-minute benchmarks could also surface as evidence in lawsuits if an emergency response goes wrong.

Why First Responders Pushed for the Law

The law grew directly out of real incidents. As robotaxis expanded across San Francisco, Los Angeles, Phoenix and other cities, fire departments and police logged a string of cases where driverless cars drove into active emergency scenes, parked on fire hoses, blocked ambulances, or ignored hand signals from officers directing traffic. With no driver to roll down a window and no quick way to reach the company, responders were left waving at a car that could not understand them.

San Francisco officials documented dozens of these interference reports in the first couple of years of commercial robotaxi service. In one widely reported case, a driverless car rolled over a fire hose during an active firefighting operation. In others, autonomous vehicles stopped in intersections and would not move while emergency crews tried to get through. The 30-second answer rule and the two-minute geofencing window are direct answers to those failures: they put a hard clock on how fast a company has to respond when seconds count.

California has been building this framework in stages. Section 38751 sits alongside earlier rules under Section 38750 that govern testing and deployment permits, collision reporting and insurance. Earlier in 2026 the state also moved to let police issue citations to autonomous vehicles for certain violations, closing another gap where a car with no driver could not be ticketed the way a human could. The July 1 requirements are the next layer, focused squarely on emergencies.

Where Robotaxis Operate and Who Is Affected

If you live in California, the odds you will encounter a driverless car are rising fast. Waymo runs paid robotaxi service across large parts of San Francisco, Los Angeles and the Phoenix area in neighboring Arizona, and has been expanding its service zones and adding freeway driving. Other companies continue testing fleets on California roads. For drivers, cyclists and pedestrians in those cities, sharing space with a car that has no one behind the wheel is now an everyday reality rather than a novelty.

The people most affected by the new law are the first responders who deal with these vehicles during emergencies, but the benefit flows to everyone on the road. A faster link to a human operator means a blocked ambulance can get moving sooner, a fire crew can clear a robotaxi off a hydrant without a long delay, and an officer managing a crash scene can have a stalled autonomous vehicle moved aside. Because the rules are tied to DMV permits, a company that wants to keep its cars on California streets has a strong reason to make the system work.

California is the largest and most closely watched market for self-driving cars in the country, so its rules tend to set the template other states study. Arizona, Texas and Nevada have all welcomed robotaxi operations, and the way California handles emergency response is likely to shape how those states write their own requirements.

What to Do If You Share the Road With a Robotaxi

For ordinary drivers, the practical advice has not changed much, but the new law adds a useful backstop. Treat a driverless car the way you would any cautious, unpredictable driver. Give it room, do not assume it sees you the way a human would, and avoid cutting in front of it sharply, because these vehicles brake hard when their sensors detect something close.

If you are involved in a collision with an autonomous vehicle, the steps mirror any crash. Move to safety if you can, call 911 for injuries, photograph the scene and the vehicle, and note the company name and any identification number on the car. Each operator displays contact information, and under the new rules a live operator is reachable quickly through the emergency line. California law also requires autonomous vehicle companies to report collisions to the DMV, so the incident will be logged with the state.

If a driverless car is blocking a road, behaving erratically or sitting in a dangerous spot, report it to local police, and in a true emergency responders now have a guaranteed fast channel to the company. You do not need to approach or touch the vehicle yourself.

The bigger picture is that California is trying to keep its safety rules in step with a technology that is scaling quickly. Robotaxi fleets are growing, freeway service is expanding, and more cities are on the list. The July 1 requirements will not stop every awkward encounter between a self-driving car and an emergency crew, but they put firm deadlines and real penalties behind the basic expectation that someone in charge can always be reached. For a technology that removes the driver, making sure a human is never more than 30 seconds away is a sensible place to draw the line.

Sources:

• FOX 11 Los Angeles, New California laws taking effect July 1, 2026
• California Vehicle Code Section 38751 explainer
• California DMV, Autonomous Vehicle Regulations
• Washington Times, California ticketing of autonomous vehicles