Washington State has a layered accessibility framework: federal ADA on top, state Washington Law Against Discrimination (WLAD) in the middle, and procurement-driven WCAG requirements for vendors selling to state agencies at the base. Demand letter volume is lower than California or New York, but the compliance requirements cut deeper into specific industries.
This page covers the actual legal obligations in Washington, who gets targeted, and what a defensible compliance program looks like.
The Washington legal framework
Three layers:
Federal ADA Title III, 42 USC 12181, applies to Washington businesses the same way it applies elsewhere. The Ninth Circuit covers Washington, so Robles v. Domino's and related decisions are binding law. Commercial websites of public-accommodation businesses are subject to ADA Title III under Ninth Circuit authority.
Washington Law Against Discrimination, RCW 49.60, prohibits discrimination in places of public accommodation under state law. Washington courts have extended places-of-public-accommodation analysis to commercial websites in a manner similar to California's Unruh Act, though without Unruh's statutory damages floor. WLAD allows compensatory damages and attorney's fees.
Washington procurement rules, specifically OCIO Policy 188 and the Washington State Consumer Accessibility standards, require Washington state agencies to procure only accessible technology. This makes WCAG 2.1 AA conformance effectively mandatory for any technology vendor selling to Washington state agencies, regardless of demand letter activity. The obligation flows through procurement contracts, not through litigation risk.
Who gets sued in Washington
Washington demand letter volume is significantly below the top-three filing states. The filings that do happen concentrate in:
The Western District of Washington, particularly the Seattle division. Eastern District filings exist but are rare.
Retail, hospitality, and professional services websites with operations in the Puget Sound region.
Individual plaintiff actions, more than the industrial-volume firm pattern seen in California and New York. Washington has plaintiff firms active in ADA website matters but not at the scale of California or SDFL.
Some federal court filings in Washington are brought by plaintiffs whose residence is arguably out of state, raising personal jurisdiction questions. This is a jurisdiction where challenging the forum choice has occasionally produced favorable defense outcomes, unlike California where the Unruh Act makes forum-shopping irrelevant.
Washington demand letter characteristics
A Washington demand letter typically runs two to three pages. Characteristics:
Federal ADA and Ninth Circuit authority, including Robles v. Domino's and Reed v. CVS Pharmacy Inc. (9th Cir. district court decisions).
WLAD citations, often naming RCW 49.60.030 and 49.60.215 (places of public accommodation).
A Washington resident plaintiff, typically with specific city-level residence listed.
A shorter list of alleged WCAG violations than in top-three jurisdictions, commonly three to eight items.
A settlement demand in the seven-to-eighteen-thousand dollar range.
A response window of twenty to thirty days, often longer than Florida or California.
Response approach
The standard response framework applies. Two Washington-specific moves matter:
First, personal jurisdiction deserves more attention in Washington than in California or New York. If your business has no Washington operations, no Washington customer list, and the alleged plaintiff website visit is the sole nexus, a personal jurisdiction challenge is a real option. Washington courts have dismissed some cases on these grounds where the defendant had no other Washington contacts.
Second, if your business is subject to OCIO Policy 188 via state procurement contracts, your compliance program documentation should be immediately available. Demand letter plaintiffs often do not realize this, and showing a contract-driven compliance program with existing documentation often convinces a plaintiff firm that settlement economics do not work.
The compliance program that handles both layers
A Washington compliance program has to satisfy both demand letter defense and procurement contract obligations, which means it has to be genuinely documented, not merely asserted.
The documentation stack:
A written accessibility policy targeting WCAG 2.1 Level AA, dated and signed. For Washington state vendors, this policy should reference OCIO Policy 188 compliance alongside ADA and WLAD.
A public accessibility statement with conformance target, conformance status, feedback channel, and known limitations. Statements for Washington state vendors should include procurement-friendly language naming Washington accessibility standards.
An audit record showing formal WCAG 2.1 AA evaluation. For vendors with state contracts, third-party audits are significantly stronger evidence than self-audits. Self-audits with tools like axe-core are acceptable for non-vendor defense.
A remediation log with dated entries tied to WCAG criteria. Vendors should retain this log for the life of their state contract plus two years.
Training records showing the engineering and content team have received accessibility training at least annually.
Vendor records for any third-party accessibility-affecting component on the site.
A user feedback log capturing reports from the channel listed in the statement.
An incident log covering demand letters, complaints, and internal escalations.
A change-management log showing accessibility review is part of the release process.
For vendors with Washington state agency contracts, retention and production of these records is a contract obligation, not optional. For non-vendor defendants, the records produce the same good-faith-effort settlement-reduction pattern seen in other Ninth Circuit states.
What to do
If you operate in Washington without state contracts and have received a demand letter:
Respond within the stated window. Use the response template.
Publish an accessibility statement if you lack one. Use the statement template. Include language naming WCAG 2.1 AA and your WLAD-compliance intent.
Begin the nine-document record.
Consider whether you have a genuine personal jurisdiction defense. If your business has zero Washington nexus other than a generally accessible website, engage Washington counsel early.
If you hold or pursue Washington state agency contracts:
Treat the nine-document record as a contract deliverable, not a defense option. It needs to exist, be current, and be producible on thirty-day notice.
Invest in a third-party audit at least annually. Self-audits do not meet procurement expectations.
Assign a named accessibility owner on your side who signs the policy and is the contract contact for accessibility matters.
Washington is a jurisdiction where the legal and procurement obligations are stronger than the demand-letter risk would suggest. A business that only thinks about demand letters will miss the contract requirements and a business that only thinks about contracts will miss the litigation exposure. Both layers are real, and the same nine-document record satisfies both.