In Oregon, 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. That gives Oregon defendants — especially web-only ones — a threshold defense that plaintiff-friendly circuits don’t allow. It does not make the typical Oregon business immune.

Oregon’s distinct angle: the Ninth Circuit nexus rule

Every ADA website case turns on one question: is a website itself a “place of public accommodation” under Title III of the ADA, or does it count only when tied to a physical location? Oregon sits in the Ninth Circuit, which wrote the leading nexus opinion — Robles v. Domino’s Pizza, LLC, 913 F.3d 898 (9th Cir. 2019). There the court held Domino’s website and app were covered because their inaccessibility “impede[d] access to the goods and services of its physical pizza franchises,” making the nexus to those stores critical (Venable on Robles). The Supreme Court declined to review the decision in 2019, locking the rule in across the circuit (Seyfarth’s ADA Title III blog). The Ninth shares this approach with the Third and Sixth; the First and Seventh treat a website as a public accommodation on its own (ABA circuit-split summary).

For an Oregon business, Robles cuts two ways:

  • Web-only in Oregon — a SaaS product or direct-to-consumer brand with no storefront — gets a genuine threshold argument that Title III may not reach the site at all, because there’s no physical place for it to connect to. That motion-to-dismiss path is foreclosed in the First and Seventh Circuits, so a web-only operation has a “no nexus” defense an Illinois defendant doesn’t have.
  • A physical location — which most Oregon businesses have — supplies the nexus, and Robles works against you. A Portland coffee roaster, a Bend outfitter, or a Salem dental office whose site shows hours, takes bookings, or sells in-store goods has exactly the connection Robles describes.

The instructive contrast is California, which shares the same nexus rule but adds the Unruh Civil Rights Act — reaching any “business establishment” regardless of a physical place, with a statutory-damages floor of no less than $4,000 per violation under Cal. Civ. Code § 52(a). That’s why web-only firms safe under Robles still get sued there. Oregon has no Unruh equivalent, so here the nexus question is the whole ballgame on the federal track (compare our California guide).

This is general information, not legal advice. Circuit law evolves and your facts control — consult a qualified Oregon attorney before relying on any defense.

Oregon’s own law: ORS 659A and a private right to sue

Federal Title III isn’t the only exposure. Oregon’s civil-rights statute makes it unlawful for any place of public accommodation to deny a person with a disability full enjoyment of its goods, services, and facilities — ORS 659A.142 (disability) and ORS 659A.403 (general public accommodation).

The remedy is ORS 659A.885: an aggrieved person may sue in Oregon circuit court for injunctive relief, compensatory damages or $200 — whichever is greater — plus punitive damages, with the court required to award reasonable attorney fees to a prevailing plaintiff. That fee-shifting is the operative detail: it makes even a modest claim worth a plaintiff’s lawyer’s time, and it runs in state court where the Ninth Circuit nexus rule doesn’t bind the judge the same way. (Not legal advice — consult an attorney.)

The 2024 Title II rule and Oregon’s 2027 deadline

The development reshaping the standard everyone is measured against lands on Oregon’s public sector first. On April 24, 2024, the DOJ finalized a Title II rule adopting WCAG 2.1 Level AA for state and local government websites and mobile apps (ADA.gov fact sheet). An April 20, 2026 interim final rule extended the compliance dates by one year (Federal Register):

  • April 26, 2027 for larger Oregon entities — the State of Oregon and cities or counties of 50,000+ (Portland, Salem, Eugene, Gresham).
  • April 26, 2028 for smaller Oregon cities and counties and for special districts — the state’s school, water, fire, and port districts.

This doesn’t directly regulate a private Oregon business, but it cements WCAG 2.1 AA as the recognized benchmark across Oregon’s public sector — and its scope reaches anything “provided or made available” through vendors. So if you sell software or services to an Oregon city, county, university, or special district, that obligation flows into your contract. See our WCAG 2.1 AA explainer.

Who’s getting sued — and where Oregon fits

Nationally, website accessibility litigation rebounded in 2025 — Seyfarth counts roughly 3,117 federal website filings, about 36% of all ADA Title III cases, concentrated in plaintiff-friendly venues like New York, Florida, and Illinois (Seyfarth ADA Title III tracker). Oregon is not a top filing state — the Robles nexus posture is a real reason filers route federal volume elsewhere.

But “fewer filings” isn’t “no filings,” and Oregon’s real exposure is the pre-suit demand letter that never hits a docket. Coverage of the 2025 ADA litigation landscape describes Portland-area businesses receiving these claims, with counsel demanding fees and a settlement to make it go away — leveraging ORS 659A.885’s fee provision, not a jury verdict. Filed federal claims land in the U.S. District Court for the District of Oregon (Portland, Eugene, Medford, Pendleton); state claims run in circuit court. The sectors mirror the national pattern — e-commerce, restaurants, hotels, and any site with online ordering or booking — and the barriers are the usual ones the DOJ flags in its web accessibility guidance: missing alt text, unlabeled forms, weak color contrast, and keyboard traps. If a letter has arrived, read what to do after an ADA demand letter and how serial plaintiffs operate.

How an Oregon business reduces exposure

In Oregon the Robles nexus rule is a defense you raise after you’re sued, not a shield that keeps the suit away — and it does nothing for the store-plus-website operations that are most of the state’s defendants, nor for an ORS 659A.885 claim. An Oregon defendant actually faces three separate fronts: a federal Title III suit in the District of Oregon, a private ORS 659A.885 action in circuit court, and an administrative complaint filed with the BOLI Civil Rights Division, which an aggrieved person can lodge within one year of the alleged discrimination under ORS 659A.820 — no lawyer required to start it (BOLI public-accommodations complaint). What closes all three is the same thing: a site that survives a real assistive-technology test, evaluated against the WCAG 2.1 AA success criteria the DOJ adopted for Title II.

  1. Test the way a BOLI investigator or plaintiff’s expert would. A free scanner is the starting line, not the finish — DOJ’s web guidance frames accessibility around concrete barriers (missing alt text, unlabeled forms, low color contrast, keyboard-only navigation), and the failures that generate an ORS 659A complaint are usually the ones no automated tool flags: a checkout that traps a screen-reader user, a booking form with no programmatic labels, a focus order that scrambles a Portland restaurant’s reservation flow. A manual accessibility audit walks the site with NVDA, JAWS, and VoiceOver to surface exactly the “denial of full and equal access” ORS 659A.142 turns into a cause of action.
  2. Fix the source, not the symptom — because ORS 659A.885 prices each gap. An overlay widget that promises instant compliance leaves the underlying HTML, ARIA, and JavaScript broken, and that broken code is what an expert documents. Manual remediation corrects it directly: real text alternatives, contrast that meets the standard, keyboard operability with a visible focus indicator, and properly labeled forms. The economics are Oregon-specific — because ORS 659A.885 stacks a compensatory-damages-or-$200 floor, punitive damages, and mandatory plaintiff fee-shifting onto every claim, each unfixed barrier is a line item a demand letter can convert into billable hours. Deleting the barrier first is the cheaper move; see why overlays don’t deliver compliance.
  3. Build the good-faith record Oregon’s forums actually weigh. Keep dated audit and remediation logs and publish an accessibility statement that names WCAG 2.1 AA and gives users a way to report barriers. In Oregon that paper trail works on every front: it rebuts the thin, copy-paste claim a serial filer routes through ORS 659A.885, it gives BOLI’s Civil Rights Division evidence of remediation if a complaint is filed, and it’s the conformance proof an Oregon public-sector buyer demands under the Title II vendor obligation when you bid on a city, county, or special-district contract.

For a small Oregon business, that program costs less than one round of District of Oregon litigation — or a single contested BOLI proceeding. Find out where your site stands with a free accessibility scan, then let [EXPERT_NAME] and the [AGENCY_NAME] team remediate the issues by hand.

The bottom line for Oregon

Oregon’s specifics cut in different directions. Robles gives web-only operations a threshold defense few circuits offer — a real reason serial filers route federal volume elsewhere. But it does nothing for the Portland restaurant or Eugene clinic whose website is plainly tied to its premises, and ORS 659A.885 hands those defendants a second front: state-court damages, a $200 floor, and fee-shifting a federal-only state never imposes. The 2024 Title II rule settles which standard applies — WCAG 2.1 AA. The one variable you control is whether the site meets it. That’s fixable, and it’s what Curbcut remediates by hand — file by file, not behind a widget.