In Washington, an inaccessible website can draw two claims at once: a federal ADA Title III claim and a parallel Washington Law Against Discrimination (WLAD) claim that — unlike the ADA — allows actual money damages with no statutory cap. That dual exposure, plus the Ninth Circuit’s nexus rule, is what makes Washington distinct.

Washington’s distinct angle: WLAD adds money damages

Most states only give plaintiffs the federal ADA to work with, and ADA Title III is limited to injunctive relief and attorney fees — a private plaintiff gets no damages under federal law. Washington is different. The Washington Law Against Discrimination, RCW 49.60.030, declares a civil right to “the full enjoyment of any of the accommodations, advantages, facilities, or privileges of any place of public resort, accommodation, assemblage, or amusement,” free of discrimination based on disability.

Critically, RCW 49.60.030(2) gives any injured person a private civil action to enjoin the violation, recover actual damages, and collect “the cost of suit including reasonable attorneys’ fees.” There is no statutory cap on damages for public-accommodation claims — the cap in RCW 49.60.225 applies only to real-estate transactions. That changes the math: a plaintiff can plead the ADA for the injunction and fees, then stack a WLAD count for damages on top — the same structural reason California’s Unruh Act makes California ADA cases so expensive, and it raises the settlement value of a Washington demand letter.

This page is general information, not legal advice. Whether WLAD reaches your specific website is a fact-specific question — consult a qualified Washington attorney.

The Ninth Circuit nexus rule: who is actually exposed

Washington sits in the Ninth Circuit, and that defines how the ADA reaches a website here. In Robles v. Domino’s, the Ninth Circuit held that ADA Title III covers a website or app when there is a “sufficient nexus between the allegedly discriminatory goods or services and an actual, physical location” — Domino’s pizza shops were the physical place of public accommodation, and the inaccessible site impeded access to them. The court also rejected the argument that the absence of formal web-accessibility regulations was a due-process problem, and the U.S. Supreme Court declined to review the decision in 2019, leaving the nexus rule the law across Ninth Circuit states (Perkins Coie analysis; Seyfarth’s ADA Title III blog).

What this means in plain terms:

  • A Washington business with a physical presence — a Seattle restaurant, a Spokane clinic, a Tacoma store, a Bellevue dealership — has a clear ADA nexus and is squarely exposed.
  • A purely online Washington business has a stronger federal defense here than in New York, where some courts entertain “standalone” website theories. The nexus requirement is a real, defensible limit under federal law.
  • But WLAD does not depend on the federal nexus test. The legislature directed in RCW 49.60.020 that the statute “be construed liberally for the accomplishment of the purposes thereof,” and the definition of a place of public accommodation in RCW 49.60.040(2) sweeps in any place “kept for gain, hire, or reward” where services are sold to the public. The Washington Supreme Court applied that breadth in Floeting v. Group Health Cooperative, 192 Wn.2d 848 (2019), holding a public accommodation liable for the full “full enjoyment” standard rather than a narrow denial-of-service test. Because WLAD reaches “services offered to the public” without the ADA’s physical-nexus requirement, the state claim can survive even where the federal one is thinner — so “we’re online-only” is not a complete answer in Washington.

Policy 188: why the state’s own benchmark matters to you

Washington tells you exactly what standard it considers reasonable, because it imposes one on itself. Policy 188 — Washington’s accessibility policy issued by WaTech’s Office of the Chief Information Officer, now carried forward in the USER-01 technology standard — requires that IT used by state agencies meet WCAG 2.1 Level AA (accessible.org overview; WaTech accessibility).

Two clarifications that matter:

  • Policy 188 does not apply to private businesses. It binds executive-branch state agencies, boards, and commissions — not your company. Anyone telling you Policy 188 makes your private site illegal is wrong.
  • It still sets the bar everyone points to. When the state of Washington adopts WCAG 2.1 AA as its own conformance target — and Washington public entities also face the DOJ’s 2024 Title II rule requiring WCAG 2.1 AA — it becomes very hard for a private defendant to argue that 2.1 AA is an unreasonable expectation. For the conformance target itself, see WCAG 2.1 AA explained and the POUR principles the guidelines are built on.

Who’s getting sued — and what they’re sued over

Unlike New York or Florida, Washington has not produced a single headline serial filer who churns out hundreds of website complaints — but the WLAD damages remedy gives plaintiffs a reason to file in Washington rather than only sending demand letters. Federal accessibility complaints land in one of two district courts depending on geography: the U.S. District Court for the Western District of Washington (W.D. Wash.), covering Seattle, Tacoma, Bellevue, and the I-5 corridor where most defendants sit, and the Eastern District (E.D. Wash.) in Spokane and Yakima. Plaintiffs frequently plead the federal ADA count alongside a WLAD count in the same complaint precisely because RCW 49.60 supplies the money damages the ADA can’t (and many file in King County Superior Court to keep the case in state court, where the WLAD remedy is on home turf). Physical-accommodation ADA litigation in W.D. Wash. is already well established — a wave of suits over Seattle hotel reservation systems shows the same nexus theory that powers website claims (KIRO 7 coverage of seven Seattle hotel ADA suits).

The volume context is national, and it is large: plaintiffs filed over 4,000 digital-accessibility lawsuits in 2024, roughly two-thirds against businesses under $25 million in revenue, and more than 1,000 of those (about a quarter) named sites that had an accessibility overlay installed (UsableNet 2024 year-end report) — which is exactly why a widget is no protection. In Washington the high-nexus targets are predictable: restaurants with online ordering, healthcare providers with patient portals (a Floeting defendant was itself a Washington health cooperative), ecommerce shops, and dealerships and clinics with booking flows. The barriers cited are the same recurring failures — images with no alt text, forms a screen reader can’t complete, insufficient color contrast, and content you can’t reach by keyboard — and under both the ADA and WLAD a plaintiff has to show a barrier, not a dollar of out-of-pocket harm, to state a claim.

How a Washington business reduces exposure

In most states the cost-benefit of cutting corners is bounded — federal ADA Title III caps a plaintiff’s recovery at an injunction plus fees. In Washington that ceiling is gone: every unremediated barrier is also a potential uncapped actual-damages count under RCW 49.60.030(2), so the WLAD math is what should drive each step here.

  1. Audit against WCAG 2.1 AA — and audit for what a WLAD plaintiff will plead. Start with a real accessibility audit that combines automated scanning with manual keyboard and screen-reader testing (NVDA, JAWS, VoiceOver). Automated tools catch only a fraction of WCAG failures and miss exactly what plaintiffs cite — illogical reading order, mislabeled custom controls. In Washington that gap matters more than elsewhere: because Floeting reads “full enjoyment” broadly, a barrier that merely frustrates a disabled user (not just one that blocks a sale) can support the state count, so the audit has to surface friction an automated scan would shrug off.
  2. Remediate the real code, because an overlay leaves the WLAD count live. This is the step overlays skip. Remediation means changing the HTML, CSS, and JavaScript so the barriers are gone: meaningful alt text, contrast meeting 4.5:1 for body text, keyboard-operable controls with visible focus, properly labeled forms. Curbcut does this by hand, file by file — we’re explicitly anti-overlay. In Washington that stance is not just best practice: a widget that doesn’t touch the source code leaves the uncapped WLAD damages exposure exactly where it was, and a widget is one of the things UsableNet found in over 1,000 of 2024’s suits. See overlay vs. manual remediation for why.
  3. Document and monitor — and route Washington customers to a fix, not a filing. Publish an honest accessibility statement naming WCAG 2.1 AA as your target (the same target Policy 188 / USER-01 sets for the state itself) and giving users a clear way to report barriers. It isn’t immunity, but it shows good-faith effort and gives a Washington customer a path to resolution before a plaintiffs’ firm offers them a WLAD damages theory. Then keep it that way with accessibility monitoring, since a new untagged PDF or third-party booking widget can reintroduce a barrier — and a fresh damages count — overnight.

If a demand letter has already arrived citing the ADA or WLAD, don’t ignore it — many resolve before a complaint is filed. Loop in counsel and begin remediation immediately.

The bottom line for Washington

Washington is one of the few states where an inaccessible website carries a price tag, not just an injunction: the WLAD’s uncapped actual-damages remedy rides on top of the federal ADA, and the Ninth Circuit’s Robles nexus rule means any business with a Seattle, Tacoma, Spokane, or Bellevue footprint is reachable through its website in W.D. Wash. or King County Superior Court. An overlay leaves that damages count untouched — and, per UsableNet, is itself a documented lawsuit magnet. The defensible move is to remove the barriers a plaintiff would plead under both statutes. Find out where you stand with a free accessibility scan, then let Curbcut audit and remediate the real code to WCAG 2.1 AA.

For primary sources, see the Washington State Legislature’s RCW 49.60, WaTech accessibility, ADA.gov, and the W3C Web Accessibility Initiative.