If your Arizona business has a physical location and a website, ADA Title III very likely applies to your site. Arizona sits in the Ninth Circuit, which requires a nexus between a website and a brick-and-mortar place of business for the ADA to reach online services — a rule that makes storefront businesses the prime targets here.

The Arizona angle: the Ninth Circuit nexus rule

Arizona is governed by the U.S. Court of Appeals for the Ninth Circuit, and that single fact shapes web-accessibility risk in the state more than anything else. The Ninth Circuit does not treat every website as a “place of public accommodation.” Instead, it asks whether there is a nexus — a connection — between the website and a physical place where a business offers its goods and services.

The leading case is Robles v. Domino’s Pizza, where the Ninth Circuit held that the ADA applies to a website and mobile app because they were a conduit to the goods and services of Domino’s physical restaurants. The U.S. Supreme Court declined to review that decision, leaving the nexus standard in force across the circuit (ADA Title III blog).

The flip side matters just as much in Arizona. In Earll v. eBay and Cullen v. Netflix, the Ninth Circuit found that purely online services with no connection to an “actual, physical place” were not covered by Title III (3Play Media; National Law Review). For an Arizona business, the practical takeaway is sharp:

  • Have a storefront, office, clinic, or restaurant? Your website is almost certainly covered. The nexus is your physical location.
  • Online-only with no physical place in Arizona? The nexus argument is weaker — though plaintiffs still file, and the law continues to evolve. Don’t treat it as immunity.

This is meaningfully different from places like New York, where courts have been willing to treat standalone websites as public accommodations without any physical tie. In Arizona, the storefront is the hook.

This page is general information, not legal advice. For your specific situation, consult a qualified Arizona attorney.

Arizona’s own law: the Arizonans with Disabilities Act

Beyond the federal ADA, Arizona has its own statute. The Arizonans with Disabilities Act (AzDA), codified at A.R.S. Title 41, Chapter 9, prohibits discrimination on the basis of disability in the “full and equal enjoyment of the goods, services, facilities, privileges, advantages or accommodations” of any place of public accommodation (A.R.S. § 41-1492.02).

Two features set Arizona apart from California’s plaintiff-driven model:

  • Enforcement runs through the Attorney General. Unlike California’s Unruh Act, the AzDA’s civil-penalty mechanism is brought by the Arizona Attorney General, who may seek up to $5,000 for a first violation and $10,000 for any subsequent violation (A.R.S. § 41-1492.09). The same statute provides that “a determination in a single action, by judgment or settlement, that the covered person or entity has engaged in more than one discriminatory act shall be deemed a single violation,” and it directs the court to weigh “any good faith effort or attempt to comply” when fixing the penalty (A.R.S. § 41-1492.09).
  • Private complaints go through the Civil Rights Division first. A person who believes they were discriminated against files with the Arizona Civil Rights Division; if conciliation fails, they can pursue a civil suit in superior court (LegalClarity).

Because Arizona lacks a state statute with the automatic, per-visit statutory damages that fuel California’s volume, most Arizona web cases still ride on federal ADA Title III, where remedies are injunctive relief plus attorneys’ fees — not damages. That fee-shifting is exactly what makes demand letters and quick settlements attractive to plaintiffs’ firms.

Arizona’s statewide WCAG standard

Arizona has a clear, published technical benchmark for government sites. The Arizona Department of Administration — Strategic Enterprise Technology Office (ADOA-ASET) maintains statewide IT policy P800, which requires state agency websites — and organizations that receive state funding — to conform to WCAG 2.0 Level AA (Equidox; Arizona accessibility policy, az.gov).

P800 doesn’t bind a private Scottsdale boutique. But it matters for two reasons. First, if you contract with the State of Arizona or take state grant money, conformance can be a condition — and a VPAT or conformance report is often requested in procurement. Second, it establishes the state’s own accepted standard, which informs what “reasonable” accessibility looks like. Layered on top, the DOJ’s 2024 Title II rule sets WCAG 2.1 Level AA as the federal requirement for state and local government websites (ADA.gov) — so Arizona cities, counties, and school districts now have a hard federal deadline regardless of P800’s 2.0 baseline.

For private businesses, the practical target is WCAG 2.1 AA: it satisfies the state’s 2.0 benchmark and adds the mobile, touch, and low-vision criteria that 2.0 missed.

Who’s getting sued in Arizona

Arizona isn’t a top-five filing state — that crown belongs to New York (1,021 filings) and Florida (961) in 2025 (ADA Title III blog). But it sits inside a national surge: 3,117 federal website accessibility lawsuits were filed in 2025, up 27% from 2,452 in 2024 (UsableNet). Demand letters, which never hit a court docket, run well above the filed-case count.

The Ninth Circuit nexus rule shapes who gets sued in Arizona more than in non-nexus states: a plaintiff’s strongest case is one where an inaccessible website plainly routes customers to a physical Arizona location, so the targets skew toward businesses with both a storefront and a transactional site:

  • Retail with physical stores — Phoenix, Tucson, Mesa, and Scottsdale shops whose online catalog and checkout fail a screen reader. This is the deepest pool nationally (e-commerce is roughly 69% of 2025 filings), and in Arizona the brick-and-mortar location is precisely the nexus that defeats a Martinez/Earll “online-only” defense. See our ecommerce accessibility guide.
  • Restaurants and hospitality — menus, online ordering, and reservation flows: the exact fact pattern the Ninth Circuit allowed to proceed in Robles, so it transfers cleanly to any Arizona restaurant with a location and an ordering page. See restaurant accessibility.
  • Healthcare and clinics — Arizona’s large retiree and snowbird population means patient-portal, scheduling, and intake pages serve an unusually high share of older users who actually rely on assistive technology, making barriers easy to encounter and document. See healthcare accessibility.
  • Hotels, resorts, and real estate — Arizona’s tourism and relocation economy runs on hotel booking engines and real-estate listing sites, both of which tie online services directly to physical properties in-state.

Nationally, e-commerce is the single most-sued category — about 69% of digital accessibility lawsuits in 2025 (UsableNet 2025 trends). And the entry barrier keeps dropping: roughly 40% of 2025’s federal ADA filings were filed pro se — self-represented plaintiffs, many using AI to find barriers and draft complaints (UsableNet / Seyfarth Shaw). For an Arizona storefront, that means a single inaccessible product page is enough to draw a letter, with or without a law firm behind it.

How an Arizona business reduces exposure

Because the Ninth Circuit hangs liability on your physical-location nexus rather than on per-visit damages, the Arizona strategy is different from California’s “count every barrier” math: here the goal is to break the nexus complaint’s core allegation — that your storefront’s website denied equal access — and to bank the kind of dated, good-faith record that A.R.S. § 41-1492.09 expressly tells a court to credit. That is a code problem, not a widget problem.

1. Audit the nexus pages first, against WCAG 2.1 AA

In a nexus jurisdiction, the pages that matter most are the ones that connect a customer to your physical Arizona business — store locator, hours, online ordering, reservations, appointment booking, the route a Robles-style complaint walks through. Start a real accessibility audit there, then work outward. A credible audit pairs automated scanning with manual testing on a keyboard and a screen reader, because the criteria plaintiffs actually plead are the ones scanners miss: programmatic structure (WCAG 1.3.1), name/role/value for custom controls, form labels and instructions, and visible keyboard focus. If you also bid on State of Arizona contracts or take state grant money, this same audit feeds the VPAT / conformance report that P800-driven procurement asks for — so one pass covers both your litigation exposure and your eligibility to sell to the state.

2. Remediate the code so the nexus pages pass

Manual remediation means rewriting the HTML, CSS, and JavaScript so the barrier is gone on the exact paths a tester would walk: meaningful alt text on product and location imagery, 4.5:1 text contrast, every control keyboard-operable through checkout and booking, labeled fields, and ARIA applied correctly rather than bolted on. This is the step accessibility overlays skip: those widgets paint over your code at runtime without fixing the underlying defect, the FTC ordered overlay vendor accessiBe to pay $1 million for misleading accessibility claims, and overlays have been named in lawsuits themselves. Curbcut is deliberately anti-overlay for exactly this reason — see overlay vs. manual remediation.

3. Document and monitor — Arizona credits good faith by statute

This step does more in Arizona than almost anywhere else, because A.R.S. § 41-1492.09 instructs the court to weigh “any good faith effort or attempt to comply” when it sets a penalty — and an honest, dated record is how you prove it. Publish an accessibility statement naming your WCAG 2.1 AA target and a barrier-report contact, keep timestamped audit and remediation records, and run ongoing monitoring so a new page, PDF, or booking widget can’t quietly reopen a barrier on a nexus page. That same paper trail also answers a Civil Rights Division conciliation request — the AzDA’s first stop before a superior-court suit — with evidence rather than a scramble.

If a demand letter has already arrived, don’t ignore it — read what to do after an ADA demand letter and loop in counsel quickly. Many resolve before a suit is ever filed.

The bottom line for Arizona

Arizona’s exposure runs on a different engine than California’s. There is no $4,000 per-visit bounty here; instead, the Ninth Circuit’s nexus rule turns a physical Arizona location plus an inaccessible website into Title III liability, the Arizonans with Disabilities Act adds Attorney-General-driven penalties of up to $5,000/$10,000 that explicitly reward good-faith correction, and the state’s own P800 / WCAG 2.0 AA policy sets the accepted benchmark. The response that fits that structure is to fix the nexus pages by hand and keep dated proof you did — an overlay widget delivers neither the fix nor the record A.R.S. § 41-1492.09 credits. Start with a free accessibility scan to see what a tester would find on the pages that connect customers to your storefront, then have the Curbcut team audit and remediate the real barriers.