In Nevada, your ADA website risk turns on one distinctive fact: the Ninth Circuit requires a “nexus” between your website and a physical place of public accommodation before federal Title III applies. That gives online-only Nevada operations a real threshold defense you won’t find in every circuit. It does almost nothing for the casino-resort, restaurant, or shop whose site is plainly tied to its premises.

Nevada’s distinct angle: the Ninth Circuit nexus rule

Most website-accessibility lawsuits ride on a single question: is a website itself a “place of public accommodation” under Title III of the ADA, or does it only count when it connects to a brick-and-mortar location? The federal appeals courts are split, and Nevada sits in a circuit that requires the physical connection.

Nevada is in the Ninth Circuit, whose controlling decision is Robles v. Domino’s Pizza, LLC, 913 F.3d 898 (9th Cir. 2019). A blind plaintiff who used a screen reader sued Domino’s over a website and app he couldn’t use. The court held the ADA applied — but its reasoning was narrow: the nexus between the website/app and Domino’s physical franchises was “critical,” because the inaccessibility impeded access to the goods and services of a physical location (Justia — full Ninth Circuit opinion). In a now-frequently-cited footnote, the court expressly declined to decide whether the ADA covers a website where the inaccessibility does not impede access to a physical location. The Supreme Court declined to review the decision, leaving Robles as binding law in Nevada.

That is the opposite of the Seventh Circuit’s posture, where a website is a public accommodation in its own “electronic space” with no storefront required — see our Illinois ADA lawsuit guide for the contrast, and the ADA website lawsuit overview for how the circuit split works. In Nevada, the threshold question — is this site even a “place”? — is a live, winnable argument for the right defendant.

This is general information, not legal advice. Circuit law evolves, district courts apply Robles unevenly, and your facts control. Consult a qualified Nevada attorney before relying on any defense.

What the nexus rule means for a Nevada business

The nexus rule cuts two ways:

  • If you’re online-only in Nevada — a SaaS product, a digital service, a web-only brand with no Nevada storefront — Robles gives you a genuine argument that Title III may not reach your site at all, and its footnote leaves the pure-online question unresolved in this circuit.
  • If you have a physical location — and Nevada’s economy is built on them — your website is tied to that place, and the nexus exists. The defense that helps online-only companies does nothing for a Las Vegas Strip resort booking rooms online, a Reno restaurant taking reservations, a Henderson dental practice, or a dispensary with online ordering and in-store pickup.

The takeaway for the typical Nevada business is sobering: the circuit’s rule narrows who can be sued, but it doesn’t shrink the target on a normal premises-plus-website operation — which describes most of the state’s hospitality, gaming, retail, and tourism economy.

Nevada’s own law: NRS 651 and a private right to sue

Federal Title III isn’t the only exposure. Nevada’s public-accommodation statute, NRS 651.070, entitles all persons to “the full and equal enjoyment of the goods, services, facilities, privileges, advantages and accommodations of any place of public accommodation, without discrimination” on grounds that expressly include disability (NRS Chapter 651). Critically, NRS 651.090 gives an aggrieved person a private civil action: a court may award actual damages, grant temporary, preliminary, or permanent injunctive relief, and award costs and reasonable attorney’s fees to the prevailing party (NRS 651.090).

A claimant may file a complaint with the Nevada Equal Rights Commission under NRS 651.110, but that route is permissive, not a mandatory prerequisite to suing (NRS Chapter 651). The statute mirrors the ADA’s public-accommodation concept rather than imposing a separate WCAG number — but it means a Nevada plaintiff has both a federal and a state path, and the fee-shifting in NRS 651.090 makes even modest cases worth a lawyer’s time. (Again: general information, not legal advice.)

Nevada’s state WCAG policy: WCAG 2.2 AA as the recognized benchmark

Here’s a Nevada-specific detail that settles arguments about which standard applies. The State of Nevada commits its own electronic and information technology — web pages and PDFs in the state Content Management System — to WCAG 2.2 Levels A and AA, plus the WAI-ARIA 1.0 suite, under ADA Technology Accessibility Guidelines administered by the Office of the CIO and the Division of Enterprise Information Technology Services (EITS) (State of Nevada Digital Accessibility Statement). Those guidelines reach Nevada departments, agencies, boards, and commissions — and Nevada’s program traces back to a 2018 All-Agency Memo from the Office of the CIO directing agencies toward conformance.

This doesn’t directly regulate a private Nevada business. But it cements a recognized WCAG benchmark across Nevada’s public sector — one higher than the WCAG 2.1 AA that DOJ adopted for state and local government under its April 2024 Title II web rule. For a private business, WCAG 2.1 Level AA is the practical floor courts and the DOJ reference; moving toward 2.2 AA tracks where Nevada itself has gone.

Who’s getting sued — and where Nevada fits

Nationally, website accessibility litigation rebounded in 2025: plaintiffs filed about 3,117 website cases in federal court — roughly 36% of all ADA Title III filings, a 27% jump over 2024 (Seyfarth’s ADA Title III tracker). That volume concentrates in plaintiff-friendly venues — New York, Florida, Illinois — not in Ninth Circuit nexus states. Nevada is not a top filing state, and Robles’s nexus requirement is a big reason serial filers route their volume to courts where the “it’s not a place” defense is already foreclosed.

But “fewer filings” is not “no filings,” and two Nevada-specific dynamics keep the risk real. First, the state’s economy is unusually public-facing: gaming, hospitality, dining, and tourism are exactly the premises-plus-website businesses the nexus rule does not shield, so a Nevada defendant rarely gets to argue pure-online. Second, Seyfarth reports that 40% of 2025 federal Title III filings came from pro se plaintiffs, up sharply year-over-year (Seyfarth ADA Title III) — self-represented filers who can target a Las Vegas or Reno site without a firm behind them. Claims arrive as suits in the District of Nevada (Las Vegas and Reno) and, more often, as pre-suit demand letters that never hit a docket.

The barriers cited track the usual ones the DOJ describes (ADA.gov web guidance): missing alt text, unlabeled or uncompletable forms, weak color contrast, broken focus states, and content you can’t reach by keyboard — common on the e-commerce, booking, and reservation flows that drive Nevada’s hospitality sites. If a letter has already arrived, read what to do after an ADA demand letter and how serial plaintiffs operate before you respond.

How a Nevada business reduces exposure

In Nevada the nexus rule is a defense you raise after you’re sued — and one that does nothing for the premises-plus-website operations that make up most of the state’s defendants. What actually lowers risk on both the federal Title III track and the NRS 651 state track is the same thing: a site that survives a real assistive-technology test. Three steps, each tied to how a Nevada claim actually plays out.

  1. Audit against WCAG AA. Start with a manual accessibility audit that pairs automated scanning with keyboard and screen-reader testing (NVDA, JAWS, VoiceOver). Automated tools catch only a fraction of failures — and the ones they miss, like illogical reading order, unlabeled controls on a reservation widget, and misleading ARIA, are precisely what a plaintiff’s expert documents to build the “concrete injury” a Nevada claim needs.
  2. Remediate the real code. This is the step overlay widgets skip. Manual remediation rewrites the HTML, ARIA, and JavaScript file by file — real alt text, color contrast at the 4.5:1 threshold, full keyboard navigation with a visible focus ring, and accessible forms with labels and error messaging. Because NRS 651.090 layers actual damages and fee-shifting on top of any federal claim, the cheapest move in Nevada is to delete the barriers before a demand letter turns them into billable hours.
  3. Document the conformance. Keep the audit reports and remediation log, and publish an accessibility statement naming your WCAG target and a way to report barriers. That paper trail supports a good-faith defense, helps moot a federal claim once fixes ship, and rebuts a parallel NRS 651 theory.

A warning specific to the litigation reality here: accessibility overlays do not protect you. They modify source code at runtime, screen-reader users often report they make sites harder to use, and in 2025 the FTC ordered overlay vendor accessiBe to pay $1 million for deceptively claiming its AI tool could make any website WCAG-compliant (FTC final order). Curbcut is deliberately anti-overlay; read whether overlays actually work before you trust one in a Ninth Circuit venue, where a premises-plus-website defendant has no jurisdictional fallback if the widget fails.

For a small Nevada business, that program costs less than one round of District of Nevada litigation — and unlike a widget, it actually closes the NRS 651.090 fee exposure. See where your site stands with a free accessibility scan, then let [EXPERT_NAME] and the [AGENCY_NAME] team remediate the issues by hand.

Authoritative resources for Nevada

The sources that govern a Nevada claim, in the order you’d reach for them:

The bottom line for Nevada

Robles and the Ninth Circuit’s nexus requirement give online-only Nevada operations a threshold defense few other circuits offer — and they’re why serial filers route their volume to New York and Florida instead of the District of Nevada. But that posture does nothing for the casino-resort, restaurant, or shop whose website plainly connects to its premises, and NRS 651.090 hands those defendants a second front: state-court actual damages and fee-shifting alongside the federal claim. Nevada’s own WCAG 2.2 AA policy then settles which standard counts. The one variable you control is whether the site actually meets it — and that’s what Curbcut remediates by hand, file by file, not behind a widget.