The Future of Self-Driving Cars is Here. Is Seattle Ready?

California DMV Can Now Ticket Self-Driving Cars: What That Means for Public Safety and When Self-Driving Cars Might Reach Seattle

Self-driving cars are no longer a concept of the future; they’re becoming part of today’s transportation landscape. California’s Department of Motor Vehicles recently moved to assert enforcement authority over autonomous vehicles (“AVs”), including the ability to issue citations when self driving cars violate traffic laws or fail to meet regulatory requirements. You can read more about the announcement here: California DMV.

While this change is taking place in California, its impact extends far beyond state lines. As autonomous vehicle technology continues to evolve, states like Washington are closely watching how safety, accountability, and regulation develop. These changes affect public safety expectations, liability questions, data access, and how other states — including Washington — regulate and adapt to autonomous technology.

Below, we’ll walk through what California’s new enforcement authority means, how it could affect Washington, and what Seattle residents should know as self-driving vehicles become more common. Our goal is to help you stay informed so you can make confident decisions for yourself and your family.

What the California change means:

• Accountability and enforcement: The DMV’s ability to cite autonomous vehicles creates a concrete regulatory lever to penalize unsafe behavior or regulatory noncompliance by companies operating AVs. That should increase incentives for operators and manufacturers to prioritize safety and compliance.
• Data and transparency pressure: Enforcement is more effective when regulators can access vehicle logs, sensor data, and incident reports. Expect increased pressure on companies to share data with authorities after crashes or significant events — which helps investigators, injured parties, and the public understand causes.
• Faster identification of systemic problems: Citations and regulatory findings can reveal recurring software, sensor, or design issues that warrant recalls, software patches, or operational changes.
• Limits on deterrence: A citation regime still depends on detection, investigation, and timely access to evidence. If companies control data or if investigations lag, enforcement may be less effective in preventing harm.
• Insurance and liability signals: Greater regulatory scrutiny makes it clearer to insurers, plaintiffs, and courts how responsibility may be assigned between vehicle operators, fleet managers, OEMs, and third‑party software providers.

Public safety implications:

• Potential safety upside: Where regulators actively monitor and sanction unsafe deployments, the overall safety baseline should improve. Citations can prompt fixes before smaller issues become widespread hazards.
• Incident response and investigation: Improved enforcement coupled with mandated reporting can speed investigations into crashes, benefiting injured parties and the public.
• New kinds of risk: Autonomous systems introduce novel failure modes (software bugs, sensor blind spots, unreliable mapping). Enforcement must be technically informed to distinguish human‑level driving faults from system failures and to require meaningful mitigations.
• Pedestrian and cyclist protection: Regulators can require stricter performance standards in complex urban environments where vulnerable road users are common, reducing risks in busy city streets.
• Equity and accessibility: As AVs expand, regulators need to ensure safety rules protect all road users and do not concentrate risk in underserved areas.

What this means for Washington:

• Cross‑jurisdiction effects: California’s enforcement model sets a precedent other states may emulate. Washington regulators will watch and may adopt similar enforcement tools or data‑sharing rules.

When are self-driving cars coming to Seattle:

• Local testing and deployments: Autonomous vehicle testing has been ongoing in multiple U.S. regions. In Washington, limited testing and pilot programs are in the works.
• In September, 2025, Waymo began public testing activity in the Seattle area.  However, the city does not yet allow unmonitored, commercial driverless (no one onboard) robotaxi service. Local rules currently require permits and either a trained human test driver in the vehicle or other specific safety controls for any testing on public streets.
• Seattle Department of Transportation requires a Street Use permit for autonomous-vehicle testing; SDOT’s permit document (version 1.0) makes clear testing may require a test driver in the vehicle, and it states that “remote driving, non-testing operations, or deployment are not currently allowed in Seattle or by this permit.” 
• The Washington State Department of Licensing (DOL) runs a self‑certification program for companies testing AVs in Washington and publishes a list of self‑certified entities (including Waymo, Zoox, NVIDIA). DOL also sets statewide reporting and insurance requirements. 
• WSDOT is actively planning for “cooperative automated transportation” (CAT) and is working on infrastructure, data and pilot frameworks to support safe testing and future deployments statewide. That shows state agencies are preparing, but not mandating immediate citywide driverless service. 

What that means in practice for Seattle residents:

• You will see more testing, mapping, and small pilots (often geofenced, often with safety drivers or remote monitoring). Public, on‑demand driverless robotaxi service across the city requires additional local approvals, safety validation and (in some cases) changes to permit or municipal rules. 
• Companies may be laying the groundwork (mapping streets, partnering with local agencies, running tests), but a wide rollout depends on successful testing, insurer and city approvals, and any state/local policy changes. News coverage suggests companies are aiming to expand to many cities in 2026–2027, but timing for full driverless service in Seattle remains uncertain.