Robotaxi Regulations in 2026: Uber vs. Waymo in D.C.

Table of Contents

Uber and Waymo clash over robotaxi regulations

D.C. Robotaxi Bill Stakes

  • What’s happening: Washington, D.C. is considering a bill that would allow commercial robotaxis, but only after meeting high testing thresholds and paying sizable fees.
  • Who wants what: Waymo broadly supports the bill as written; Uber opposes it and is pushing a “hybrid” model that would require robotaxis to run through ride-hailing networks alongside human drivers.
  • Why it matters: The bill’s structure could determine whether D.C. becomes a multi-operator market—or one where the first compliant entrant gains a meaningful head start.
  • A proposed D.C. bill would open the door to commercial autonomous vehicles, but with steep fees and strict testing rules.
  • Uber is lobbying against the bill, warning it could displace human drivers and effectively advantage Waymo.
  • Waymo broadly supports the proposal—and has already met key testing thresholds in D.C.
  • A packed D.C. Council hearing revealed a wider industry split over costs, safety, and market access.

Step 1: Overview of the D.C. Bill and Industry Response

Washington, D.C. has become a proving ground for how U.S. cities might regulate robotaxis—especially as public patience thins after high-profile operational failures elsewhere. The D.C. Council is evaluating a proposed bill that would allow autonomous vehicles to operate commercially in the District, and the early reaction from industry has been unusually polarized.

On one side, Waymo appears to view the bill as workable and, importantly, predictable. On the other, Uber is actively opposing it and pushing an alternative structure that would tether robotaxis to ride-hailing networks that still rely on human drivers. Beyond those two, much of the autonomous vehicle (AV) sector is signaling discomfort with the bill’s cost and compliance burden.

That tension is playing out against a broader 2026 backdrop: regulators are increasingly focused on reliability in “extraordinary events” and emergency-scene behavior. Recent incidents—like Waymo vehicles becoming immobile in heavy traffic and Zoox issuing a software recall after a robotaxi struggled around smoke at an emergency scene—have sharpened the political appetite for tougher rules.

Bill element (as described in reporting/testimony) What it requires Why it’s a flashpoint
Mandatory testing threshold 180 days and 250,000 miles of testing Sets a high bar for newcomers; raises questions about whether out-of-jurisdiction miles should count
Application fee $1 million Seen by many developers as a barrier to entry, not just an administrative cost
Permit fee $5 million Favors well-capitalized operators; increases the cost of experimenting in a new city
Per-mile tax $0.15 per mile Could discourage “deadheading”/circling, but also raises operating costs and pricing pressure
Market access dynamics Early compliance can translate into earlier launch A first mover can shape rider habits, city relationships, and operational learning loops

Step 2: Uber’s Opposition to the D.C. Bill

Uber’s argument against the D.C. proposal is not framed as a blanket rejection of autonomy. Instead, it’s a targeted critique of how the bill could shape the market—and who benefits first. In correspondence to the D.C. Council, Uber has warned that the bill, as written, could accelerate displacement of for-hire human drivers while giving Waymo an early, structural advantage that looks like a de facto monopoly.

Uber’s posture also reflects a strategic reality: it is both a ride-hailing platform built on human drivers and a company trying to “play both sides” of the robotaxi transition. That dual identity makes D.C.’s choices unusually consequential. If the District creates a framework that favors independent robotaxi operators, Uber risks being relegated to a distribution layer—or cut out entirely if robotaxi companies go direct.

Concerns About Human Driver Displacement

A central pillar of Uber’s opposition is workforce impact. Uber argues the bill would displace for-hire human drivers—an issue that resonates politically in a city where labor voices and public-interest groups show up in force when transportation policy is on the table.

This is not merely rhetorical positioning. “Job killer” warnings about robotaxis have become a recurring theme in public debate. Uber is effectively aligning itself with that concern: if robotaxis can operate freely and scale, the demand for human-driven ride-hailing trips could drop, and the transition could happen faster than regulators—or workers—are prepared for.

Uber also links job displacement to market structure. If only a small number of companies can clear the bill’s hurdles quickly, the first entrants could lock in demand, partnerships, and political goodwill before competitors (or hybrid models) have a chance to mature.

Lobbying for a Hybrid System

Uber’s proposed alternative is a “hybrid” system: robotaxis would be required to operate on a ride-hailing network alongside human drivers. In practice, that would mean autonomous fleets would need to plug into platforms like Uber (or similar networks) rather than operating independently.

Hybrid Model: Benefits and Frictions
Uber’s “hybrid” pitch is easy to summarize—harder to make work cleanly in practice.

  • Potential upside (Uber’s view): keeps a role for human drivers during the transition and prevents a single robotaxi operator from going direct-to-consumer and dominating early.
  • Trade-off for AV developers: “either put their robotaxis on ride-hailing apps like Uber or employ human drivers alongside fleets of robotaxis that took years and hundreds of millions of dollars to develop.”
  • Trade-off for drivers and riders: a hybrid mandate could slow displacement, but it can also blur accountability (who is responsible for service quality and incident response—the fleet operator or the platform?) and may reduce the efficiency gains that make robotaxis attractive in the first place.

Insiders cited in reporting suggest this hybrid approach has little chance of becoming law. But the implications are significant. If such a requirement existed, AV developers like Waymo would face two unattractive options: distribute their robotaxis through ride-hailing apps—ceding customer ownership and margin—or employ human drivers alongside fleets of robotaxis that took years and hundreds of millions of dollars to develop.

From Uber’s perspective, the hybrid model preserves relevance and leverage. It keeps the platform at the center of trip demand, maintains a role for human drivers, and slows the emergence of a fully autonomous, vertically integrated competitor that could bypass ride-hailing intermediaries.

Step 3: Waymo’s Support for the D.C. Bill

Waymo stands out as one of the few major companies that generally likes the D.C. bill. That doesn’t necessarily mean Waymo views it as light-touch regulation; rather, the bill’s structure appears compatible with Waymo’s current operational posture and readiness in the District.

Waymo has been testing autonomous vehicles in Washington, D.C. with human safety operators. Crucially, it has already surpassed the bill’s mandatory testing thresholds—positioning it to move faster than rivals if the legislation passes without major changes. In a market where regulatory timing can be as decisive as technology, that head start matters.

Waymo’s support also lands in a moment when robotaxi operators are under pressure to demonstrate reliability, especially around emergency response and unusual traffic conditions. Federal scrutiny has intensified, and local officials—such as San Francisco’s mayor—have publicly urged tougher rules after robotaxi disruptions. In that environment, a clear, enforceable framework can be an asset for the best-prepared operator.

Waymo Meets Local Thresholds
Why Waymo can plausibly support a “strict” bill:

  • The bill’s key gate is local testing: 180 days and 250,000 miles.
  • The article’s reporting notes Waymo has already surpassed those thresholds in D.C. while testing with human safety operators.
  • Practical implication: if the bill passed “as written today,” Waymo could enter with at least a six-month head start, while competitors argue for portability (counting miles from other jurisdictions).

Meeting Testing Requirements

The D.C. bill includes a 180-day, 250,000-mile mandatory testing requirement. Waymo has already exceeded both in the District while operating with human safety operators. If the bill passed “as written today,” that would give Waymo at least a six-month head start entering the market.

That advantage is not abstract. In platform markets, early entry can shape rider habits, municipal relationships, and operational learning loops. It can also influence how regulators interpret “normal” robotaxi behavior—what kinds of service areas are acceptable, how incident reporting works in practice, and what performance benchmarks become politically salient.

Other AV developers have argued that testing miles accumulated in other jurisdictions should count toward D.C.’s mileage threshold. Waymo’s position is strengthened precisely because it doesn’t need that concession: it has already done the local work.

Implications of a Potential Monopoly

Uber’s critique—that the bill could hand Waymo a de facto monopoly—hangs over Waymo’s support, even if Waymo does not frame it that way. The concern is less about formal exclusivity and more about practical barriers: if compliance costs and testing requirements are high, only a handful of companies may be able to enter quickly, and the first mover could dominate mindshare and operations.

The D.C. bill’s structure includes significant financial and operational hurdles, and industry voices have warned those hurdles could tilt the playing field toward the most capitalized and most locally advanced operators. In that sense, Waymo’s readiness becomes a competitive moat created partly by regulation.

At the same time, the monopoly argument is politically double-edged. Regulators want safety and accountability; they also want competition and consumer choice. The bill’s final shape may hinge on whether the Council believes strictness ensures trust—or inadvertently narrows the market to one or two winners.

Step 4: The D.C. Council Hearing and Stakeholder Involvement

The D.C. Council hearing on the proposed autonomous vehicle bill underscored how robotaxi regulation has become a multi-stakeholder fight, not just a technical one. Representatives from Lyft, Tesla, Uber, and Waymo attended, alongside dozens of disability rights and accessibility advocates, local business and industry groups, highway safety organizations, government officials, labor unions, and think tanks.

The breadth of participation matters because robotaxis touch multiple policy domains at once: transportation, labor, disability access, public safety, taxation, and urban planning. The hearing also revealed a key dynamic: while the public debate often frames “the industry” as a unified bloc pushing for permissive rules, the testimony suggested the opposite. Waymo appeared relatively aligned with the bill, while much of the rest of the industry pushed back on specific provisions.

How Council Hearings Shape Bills
How a council hearing typically shapes a bill (and where it can stall):
1) Draft bill introduced → sets initial thresholds (fees, testing miles/days, caps, taxes).
2) Public hearing → companies, advocates, unions, safety groups, and officials give testimony and submit written comments.
3) Council questions & revisions → provisions often change here (e.g., whether out-of-jurisdiction testing miles count; how fees/taxes are structured).
4) Committee action → the bill can be amended, advanced, or held.
5) Full council vote → final passage depends on political trade-offs (safety, access, jobs, competition).
Checkpoint to watch: if stakeholders can’t agree on testing portability and cost barriers, the bill often gets rewritten rather than passed “as is.”

Representatives from Major Companies

The presence of Lyft, Tesla, Uber, and Waymo put brand-name weight behind competing regulatory visions. Tesla’s senior policy adviser, India Herdman, echoed concerns heard from multiple AV developers—especially objections to the bill’s mandatory testing requirement and its fee and tax structure.

Tesla and others argued that testing miles accumulated in other jurisdictions should count toward D.C.’s mileage threshold. That request signals a broader industry preference: portability of compliance. Companies want to avoid re-running expensive, time-consuming validation in every city, particularly when they believe their systems have already been tested elsewhere.

Uber’s participation, meanwhile, was notable for its emphasis on market design—how rules could shape who controls demand and whether robotaxis must integrate with ride-hailing networks. Waymo’s posture was comparatively straightforward: it is positioned to comply and enter quickly.

Advocacy Groups and Public Testimony

Disability rights and accessibility advocates were a prominent presence, reflecting a core pro-robotaxi argument: autonomous vehicles could expand independence and mobility for people who face barriers with traditional transportation. That perspective often clashes with labor-driven concerns about displacement, but it also reframes the debate away from novelty and toward civil participation.

Highway safety organizations and government officials added another layer: operational reliability. Recent robotaxi incidents—vehicles blocking streets after losing power in heavy traffic, or software confusion around emergency-scene conditions—have made “what happens when things go wrong” a central question, not a footnote.

The hearing’s mix of voices suggests the Council is being asked to balance competing public goods: safety, access, jobs, and innovation—under conditions where the technology’s edge cases are increasingly visible.

Step 5: Concerns Raised by Other AV Developers

While Uber and Waymo have become the headline antagonists, the D.C. bill is also triggering broader industry anxiety—particularly among developers that are not yet positioned to meet D.C.’s requirements quickly or absorb its costs easily.

The takeaway from reporting around the hearing was blunt: Waymo is one of the few companies that generally likes the bill. Much of the rest of the industry does not. That matters because D.C. is not just another city; it is a symbolic and regulatory bellwether. A strict framework in the nation’s capital can influence how other dense urban jurisdictions write their own rules.

Objection raised (as reflected in testimony/reporting) Who it tends to help What policymakers are trying to achieve Likely trade-off
180-day, 250,000-mile mandatory testing requirement is too rigid Developers without a large D.C. testing footprint Local proof of readiness before commercial service Slower entry; favors the operator already closest to compliance
$1M application fee and $5M permit fee are too high Smaller or less-capitalized developers Ensure only serious operators deploy; fund oversight Barrier to entry; can narrow competition
$0.15-per-mile tax increases operating costs Operators worried about unit economics Discourage empty miles/circling; create public revenue Higher prices or reduced service coverage
Testing miles from other jurisdictions should count Multi-city operators seeking portability D.C.-specific validation and accountability Less duplicative testing vs. less local assurance

Testing Requirements and Fees

Developers have objected to the bill’s 180-day, 250,000-mile testing requirement, as well as its financial demands: a $1 million application fee and a $5 million permit fee. The bill also includes a $0.15-per-mile tax.

Tesla’s India Herdman articulated these concerns publicly, reflecting what multiple AV developers have been saying: the combination of long testing timelines and high fees can function as a barrier to entry, not just a safety filter. Companies also argued that miles driven in other jurisdictions should count toward the D.C. threshold—an attempt to reduce duplicative compliance.

From a policy standpoint, these provisions appear designed to force seriousness: only operators willing to invest heavily should deploy. From an industry standpoint, they risk narrowing the field to the few players with the deepest pockets and the most mature local programs.

Impact on Industry Dynamics

Strict local rules can reshape competition in two ways: by slowing everyone down, or by advantaging the company that is already closest to compliance. In D.C., Waymo’s existing testing footprint means the bill could accelerate its entry relative to peers, even if the rules are demanding in absolute terms.

That dynamic feeds consolidation pressure. When compliance requires multi-million-dollar fees and extensive local testing, smaller developers and less-capitalized entrants may be forced to delay, partner, or exit. Even large players may prioritize only a handful of markets where the regulatory return on investment is clearest.

The result is a paradox: regulation meant to protect the public can also determine which business models survive—independent robotaxi operators, platform-integrated fleets, or some hybrid that emerges from political compromise.

Step 6: Uber’s Acquisition of Delivery Hero

As Uber fights a regulatory battle over robotaxis, it is simultaneously reinforcing its identity as a global ride-hailing and delivery heavyweight. Uber has agreed to acquire Germany’s Delivery Hero in a $14.8 billion deal—one that will take time to clear regulatory hurdles.

Staying Central in Robotaxis
Why this deal belongs in a robotaxi story:

  • Robotaxis threaten to shift value toward whoever controls fleet operations and customer demand.
  • The Delivery Hero acquisition reinforces Uber’s strategy to stay central to demand and logistics across categories (rides + delivery), even if the “driver” model changes.
  • If robotaxi operators go direct-to-consumer, Uber’s hedge is scale: more markets, more orders, more routing and marketplace leverage.

If the deal closes, Uber would gain access to nearly 100 markets across Europe, the Middle East, Latin America, and Asia. The practical effect, as described in reporting: Uber’s delivery footprint would double. That expansion matters for autonomy because it highlights Uber’s broader strategy—own demand, logistics, and marketplace infrastructure across multiple mobility and delivery categories, even as the underlying “driver” model evolves.

Delivery Hero also made a separate agreement to sell its business in 14 markets—where Uber Eats already operates—to New York-based investment firm SSW Partners for $1.6 billion. That carve-out suggests a parallel consolidation and de-overlap process happening alongside Uber’s expansion.

Taken together, the Delivery Hero deal and the D.C. lobbying push show Uber hedging: if robotaxis become a direct-to-consumer service controlled by AV developers, Uber wants to remain indispensable through scale, distribution, and adjacent logistics dominance.

Robotaxi regulation in 2026 is no longer a theoretical exercise. It is being written in response to real deployments, real failures, and real political constituencies. D.C.’s bill—strict, expensive, and highly contested—captures the new reality: cities want autonomy, but only on terms that address safety, reliability, and social impact.

“Emergency scenes are not rare or extreme ‘edge cases.’”
—NHTSA Administrator Jonathan Morrison, in a directive calling on AV developers to address emergency-response shortcomings

The Uber-Waymo split also signals something broader: the industry is fragmenting into competing governance preferences. Some companies want independent operation with clear thresholds; others want integration into existing ride-hailing systems to manage workforce transition and market power.

Evaluating Robotaxi Policy Proposals
A practical lens for evaluating any city’s robotaxi bill (including D.C.’s):
1) Safety & emergency behavior: What must vehicles do at emergency scenes, during road closures, or when sensors/communications degrade?
2) Operational reliability: What happens in gridlock, power constraints, or “extraordinary events”—and how is performance measured?
3) Market access & competition: Do fees/testing rules create a safety filter, or an effective barrier that picks winners early?
4) Workforce & equity: How are job impacts handled, and do accessibility gains (for riders with disabilities, underserved areas) have enforceable requirements?
5) Accountability & enforcement: Who gets cited, who reports incidents, and how quickly can the city pause or constrain operations if problems repeat?

Understanding the Regulatory Landscape

D.C. is not alone in tightening expectations. California has finalized sweeping AV regulations that expand oversight and enforcement, including mechanisms that allow peace officers to issue citations to AVs and require reporting of noncompliance. Federal pressure has also increased, with NHTSA calling for concrete solutions to emergency-scene interaction problems.

In that context, D.C.’s strictness looks less like an outlier and more like an early draft of what dense cities may demand: proof of reliability, clear accountability, and financial commitments that signal operators can sustain safe service.

The Role of Industry Stakeholders

The hearing demonstrated that robotaxi rules will be shaped as much by advocacy groups, labor unions, safety organizations, and local businesses as by engineers and product teams. Disability and accessibility advocates see autonomy as a path to independence; labor groups see it as a threat to livelihoods; city officials see both promise and risk in how robotaxis behave during disruptions.

The next phase of robotaxi deployment will likely hinge on whether regulators can write frameworks that are strict without being exclusionary—and whether companies can prove, in public and under scrutiny, that their vehicles can handle the messy realities of city streets.

This lens is informed by Martin Weidemann’s work building and scaling technology-driven businesses in regulated, multi-stakeholder environments across Latin America, where policy design, operational reliability, and marketplace incentives often determine whether complex mobility and logistics systems can expand safely.

This article reflects publicly available information and public testimony as of the time of writing. Legislative language, fee structures, and compliance thresholds may change as proposals advance and are amended. Company positions may also shift as partnerships evolve and new events influence political priorities.

Related Posts

Scroll to Top