State Law Summary
In Oregon, website accessibility is currently undergoing a major shift. The state has moved from a general "best effort" approach to a strict, timeline-driven mandate for public entities, while private businesses face increased scrutiny under both federal law and specific Oregon consumer protection statutes.
State and Local Government (Title II)
Oregon is currently in a high-intensity "Execution Phase" to meet new federal and state requirements.
- The 2026 Deadline: Following the DOJ's 2024 ruling, Oregon public entities (including state agencies, cities like Portland, and universities like OSU/UO) must be fully compliant with WCAG 2.1 Level AA by April 24, 2026. Smaller municipalities (under 50,000 residents) have until April 2027.
- ODHS-OHA Operational Policy 010-029: This is one of the most rigorous state-level policies. It mandates that the Oregon Health Authority (OHA) and Department of Human Services (ODHS) adhere to WCAG 2.2 Level AA—a step above the federal 2.1 requirement—for all digital content, including social media and internal documents.
- The "Procurement Barrier": As of 2025, Oregon agencies have begun implementing new contract language. Vendors and web developers bidding on state projects must now provide an ACR (Accessibility Conformance Report). If a product isn't accessible, the vendor is often legally required to provide a remediation roadmap before the contract is signed.
Website Compliance Rules
Private Businesses (Title III)
While Oregon doesn't have a standalone "Website Accessibility Act" for private companies, it uses other state levers to enforce digital inclusion.
- BOLI Enforcement: The Oregon Bureau of Labor and Industries (BOLI) oversees "Public Accommodations." In Oregon, the definition of a public accommodation is broad. If a website is the primary way an Oregonian interacts with a business (booking a hotel in Bend, ordering from a Portland shop), BOLI and Oregon courts increasingly view that site as a protected space under state civil rights laws.
- The "Nexus" Trend: Oregon courts generally lean toward the "nexus" theory (linking a website to a physical location), but for e-commerce-only businesses, the risk is still high due to the Oregon Unlawful Trade Practices Act (UTPA).
- New for 2026 – Consumer Protections: Senate Bill 430 and House Bill 3167 (effective Jan 1, 2026) regulate "look-alike" websites and "hidden fees." While these are consumer protection laws, they overlap with accessibility because they mandate "clear and conspicuous" digital disclosures, which are difficult to defend if the site isn't screen-reader friendly.
Damages & Penalties
Technical Standards in Oregon
If you are developing or auditing a site for the Oregon market, the state-endorsed "Gold Standard" includes:
| Category | Standard | Key Oregon Focus |
|---|---|---|
| Technical | WCAG 2.1 / 2.2 AA | Moving toward 2.2 for all state-funded projects. |
| Language | ORS 183.750 | The "Plain Language Law" requires state-related info to be easily understood (no jargon). |
| Documents | PDF/UA | Oregon agencies are currently auditing and purging non-compliant PDFs. |
| Testing | Manual + Assistive | State agencies (like OHA) now use native screen-reader users for final site sign-offs. |
Strategy Tip: The "Archived Content" Trap
One unique detail in Oregon's 2026 roadmap is the treatment of archived content. Content created before April 24, 2026, that is kept solely for reference (and clearly marked "Archived") may be exempt. However, if that old PDF is still used to "apply for or participate in" a service (like a classic car registration form), the exemption is void and it must be remediated.
Would you like me to find the specific contracting playbook used by Oregon state agencies so you can see the exact language they require from web developers?
Comments
Log in to add a comment.