WCAG 2.2 Compliance and ADA Title III Website Lawsuits
Eugene, OR & Las Vegas, NV — Serving Oregon & Nevada
Optimize Media Marketing
Digital Accessibility

Navigating WCAG 2.2 Standards Amidst the Evolution of ADA Title III Litigation

Randy Bett — Digital Marketing Strategist November 18, 2026 7 min read
Request an audit today.
A laptop and braille display beside an editorial illustration of courthouse columns and scales of justice.
AI-generated editorial illustration of digital accessibility and legal context; not a photograph of a specific lawsuit.

What WCAG 2.2 changes, what the Gomez decision actually says, and how human-led accessibility audits help businesses find and remove digital barriers without promising immunity from litigation.

The Web Content Accessibility Guidelines (WCAG) provide a practical framework for making websites usable by people with disabilities. WCAG 2.2, first published as a W3C Recommendation in October 2023, adds success criteria addressing barriers faced by users with visual, motor and cognitive disabilities. At the same time, website accessibility under Title III of the Americans with Disabilities Act remains a legal question shaped by a business’s circumstances and the governing jurisdiction.

For digital retailers and service providers, aligning with WCAG 2.2 is a useful technical objective—not a certificate of legal compliance. Proactive evaluation can uncover obstacles in ordinary customer journeys, from researching services and finding a location to requesting an estimate or completing checkout. The goal is effective access, supported by documented testing and source-code remediation.

Important distinction: WCAG 2.2 is not automatically a universally codified Title III requirement for every private-business website. The Department of Justice identifies WCAG as helpful technical guidance while explaining that businesses’ ADA duties still apply. Separate rules for state and local government websites under Title II should not be confused with private-business Title III obligations.

Public Accommodations and the Website Nexus Debate

The ADA was enacted in 1990, before the commercial web developed into today’s marketplace. Its categories of public accommodations describe businesses and facilities rather than expressly listing websites. Courts have therefore examined how digital services relate to the goods and services offered by covered businesses, and different jurisdictions have taken different approaches.

A recurring issue is the nexus, or connection, between a website and a physical public accommodation. This does not simply mean whether a visitor can enter a building. Depending on the applicable law and facts, barriers to using online services connected to a physical business can interfere with access to the goods and services of that business. Whether a particular organization and customer journey fall within Title III is a question for qualified legal counsel.

What Gomez v. Bang & Olufsen Actually Decided

In Gomez v. Bang & Olufsen America, Inc., Case No. 1:16-cv-23801-LENARD, Andres Gomez alleged that screen-reader barriers prevented him from using a retailer’s website. The complaint described merchandise information, store locations, custom-installation information and appointment-related services associated with physical stores. These were allegations, not findings that every claimed technical barrier had been proved.

On February 2, 2017, Judge Joan A. Lenard of the Southern District of Florida dismissed the ADA claim without prejudice. The court found that Gomez had not adequately alleged that the website barriers impeded his own use or enjoyment of the physical stores’ goods and services, rather than hypothetically affecting others. He was allowed fourteen days to submit an amended complaint and seek reopening.

The distinction matters: this was a district-court pleading decision, not a final merits ruling granting businesses a blanket exemption for inaccessible websites. Nor was it an Eleventh Circuit holding that settled every website-accessibility question. Read the public judicial record for Gomez v. Bang & Olufsen America, Inc. (opens in a new tab) for the court’s reasoning and the decision’s procedural limits.

Why the Absence of Technical Regulations Is Not a Complete Defense

The Ninth Circuit’s January 15, 2019 decision in Robles v. Domino’s Pizza, LLC illustrates why older district-court reasoning should not be treated as a universal safe harbor. The court held that Title III applied to Domino’s website and app because they connected customers to goods and services of its physical restaurants, including delivery and pickup ordering. The relevant issue was access to those goods and services, not merely physical entry.

Although the Robles district court had accepted due-process concerns arising from the absence of specific technical regulations, the Ninth Circuit reversed. Domino’s had fair notice of its duties to provide effective communication and full and equal enjoyment; the lack of a detailed technical blueprint did not remove those duties. The appellate court distinguished ADA liability from WCAG 2.0 conformance, which could be ordered as an equitable remedy after an ADA violation was established. It did not itself decide the ultimate merits of the ADA claim.

Oregon and Nevada businesses should understand that jurisdiction and the individual facts matter. Operating online is not a reason to assume either automatic liability or automatic protection. Discuss legal obligations, litigation strategy and any claim you receive with an attorney; use technical audits to identify and resolve real barriers rather than relying on a jurisdictional argument as an accessibility plan.

The Digital Barriers That a Useful Audit Should Document

A meaningful accessibility review connects specific URLs, components and success criteria to what people cannot do. Examples include missing image alternatives, store-locator controls that cannot be operated by keyboard, dialogs without accessible names, unannounced form states, and checkout or estimate-request steps that block assistive technology. The length or detail of a complaint does not prove its allegations; reproducible evidence is what makes a technical finding actionable.

Common barriers worth investigating include:

  • Headings, landmarks, labels and meaningful lists that do not expose the page’s structure clearly.
  • Low text contrast, hidden keyboard focus, overlapping controls or content that fails to reflow at narrow widths.
  • Images without useful alternatives and controls whose visible labels do not match their accessible names.
  • Form errors and status messages that are difficult to find, understand or hear with assistive technology.
  • Third-party maps, booking tools and checkout components whose complete customer journeys have not been tested.
A braille-display user and a developer review a form with clear labels, visible keyboard focus and an explanatory error message.
AI-generated illustration of collaborative remediation: keyboard access, understandable forms and meaningful errors must work together.

WCAG 2.2 Adds Practical Requirements for Real User Journeys

WCAG 2.2 adds nine success criteria to WCAG 2.1 and removes the obsolete Parsing criterion. The additions are not all at the same conformance level. An audit targeting Level AA includes the applicable Level A and AA criteria; it should not present every new criterion as an AA obligation.

Three additions especially relevant to service and checkout workflows are:

  • 2.4.11 Focus Not Obscured (Minimum), Level AA: a keyboard-focused component must not be entirely hidden by author-created content. The enhanced fully-visible criterion is Level AAA.
  • 2.5.8 Target Size (Minimum), Level AA: pointer targets must meet the 24 by 24 CSS-pixel requirement or satisfy an applicable exception, such as spacing or inline text. Larger touch targets can be a useful design recommendation without being confused with this minimum.
  • 3.3.7 Redundant Entry, Level A: information already supplied and required again in the same process should be auto-populated or available for selection, subject to stated exceptions such as security or essential re-entry.

Other additions address dragging alternatives, consistent help and accessible authentication. Existing criteria such as meaningful sequence, keyboard access, contrast, pause/stop/hide and error identification remain important. Passing an automated scan does not establish conformance: tools cannot determine whether every alternative is meaningful or every assisted customer journey is usable.

Turn Audit Findings into Code-Level Remediation

Start with agreed templates and complete user journeys, including mobile and third-party boundaries. Combine automated checks with manual keyboard review, zoom and text-resize checks, and actual screen-reader testing on the operating-system/browser combinations within scope. Record the exact versions and settings used; browser DOM checks and mobile viewport emulation are not substitutes for native JAWS, NVDA or Apple VoiceOver results.

A useful finding names the affected URL or component, describes the user impact, identifies the applicable criterion, gives reproduction steps and suggests a source-level correction. Prioritize barriers that prevent navigation, form completion or access to services. After implementation, retest the affected journey and include regression checks so later content or design changes do not quietly reintroduce the problem.

A practical remediation sequence:

  1. Agree the audit scope, WCAG version/level, representative templates and important customer tasks.
  2. Document reproducible barriers with component-level evidence and the agreed native test matrix.
  3. Correct markup, styling and interaction code rather than relying on an overlay as proof of compliance.
  4. Retest the repaired journeys, preserve accessible phone/contact alternatives and record remaining limitations.

Accessibility Audits for Oregon and Las Vegas Businesses

For Oregon businesses, a review can focus on local service inquiries, location information and appointment requests through our Oregon WCAG 2.2 audit and compliance service. The agreed scope determines which templates, journeys and native combinations are evaluated.

For Las Vegas and Nevada businesses, our Las Vegas WCAG 2.2 audit and remediation program connects technical findings to a prioritized repair plan, with nationwide collaboration available. A documented report should state what was tested, what remains pending and what requires specialist legal advice.

Improving accessibility can reduce avoidable digital barriers and help a business manage risk, but no audit, tool or remediation program can promise that a lawsuit will never be filed. The sustainable objective is a more usable website, backed by credible evidence and ongoing maintenance—not an “impenetrable defense.”

Educational information, not legal advice. Sources reviewed include W3C’s What’s New in WCAG 2.2, the DOJ’s Guidance on Web Accessibility and the ADA, the February 2, 2017 Gomez order and the Ninth Circuit’s January 15, 2019 Robles opinion. Coverage and remedies depend on the law and facts; consult qualified counsel for legal advice.

Find the barriers in your website’s important customer journeys and get an agreed scope for an accessibility audit and remediation plan.

Request an audit today.
Article tags
  • WCAG 2.2
  • ADA Title III
  • Digital Accessibility
  • Website Audits
  • Oregon
  • Las Vegas
Randy Bett
Digital Marketing Strategist — Optimize Media Marketing

Randy is the founder of Optimize Media Marketing and has 15+ years of digital marketing experience helping Oregon home service contractors dominate local search.