DEV Community

Cover image for How Domino's Could Topple the Accessible Web – Part 1: Public Accommodations
Ben Myers
Ben Myers

Posted on • Updated on

How Domino's Could Topple the Accessible Web – Part 1: Public Accommodations

This post is the first in a three-part series on web accessibility in American case law, and the impact Robles v. Domino's Pizza could have on that landscape. This first entry focuses on the ways courts interpret public accommodations.

You can also read this post on my blog.

What's Happening

Last year, 2,285 web accessibility cases were filed in the US. That's about six cases a day, and it's almost three times as many cases as 2017.^1 As the number of cases rises, so too does the media attention, and no case has quite stolen that spotlight like Robles v. Domino's Pizza has.

Guillermo Robles has had a storied three years. As a blind man who navigates the web using a screenreader, he found he was unable to order pizza from Domino's. He filed a suit against Domino's in September 2016, alleging that Domino's website and mobile app were incompatible with his screenreader. The Central District of California dismissed the case on the grounds that the law was not concrete enough to hold Domino's accountable. The Ninth Circuit Court of Appeals overturned that dismissal in January 2019, asserting that the law does, in fact, hold the pizza chain accountable for inaccessible websites and apps. Most recently, in July, Domino's petitioned to bring the case to the Supreme Court. They're backed by the U.S. Chamber of Commerce, the Restaurant Law Center, and the National Retail Federation.^2 Businesses really, really want to see this case go their way.

This case could have a lasting impact for many disabled users of the internet. The Supreme Court has not yet seen a web accessibility case, meaning lower courts have been left to figure this out for themselves. Specifically, courts have been grappling with two big questions:

  1. Does American law require websites to be accessible?
  2. If so, which standards of accessibility are websites held to?

The courts' many responses to those questions have led to a lot of confusion, ambiguity, and frustration. However, understanding where these courts are coming from is vital to understanding the future of disabled users' access to the internet.

Let's look at that first question:

Does the Law Require Web Accessibility?

No federal law mentions web accessibility. As a result, courts turn to the next best thing: the Americans with Disabilities Act. Title III of the ADA forbids public accommodations from discriminating against disabled Americans:

"No individual shall be discriminated against on the basis of disability in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation by any person who owns, leases (or leases to), or operates a place of public accommodation."

Disabled plaintiffs argue that websites count as public accommodations and, as a result, cannot be inaccessible.

What is a Public Accommodation?

It's here that a definition of "public accommodation" would be really nice. Title III, however, does not provide one. Instead, it offers a long list of examples of public accommodations, including hotels, restaurants, banks, travel services, zoos, laundromats, and many more. This list is well understood to be nonexhaustive.^3 Crucially, however, it does not mention websites.

So, Are Websites Public Accommodations?

Courts are divided on this question, but their opinions can be roughly grouped into three categories:

  1. Yes, websites are public accommodations.
  2. No, websites are not public accommodations.
  3. Websites are sometimes public accommodations.

These opinions conflict a lot, meaning there are many cases with inconsistent rulings.


Opinion #1: Yes, Websites Are Public Accommodations

Amongst courts, the opinion that websites are inherently public accommodations is the most fringe. These courts, namely the First and Seventh Circuit Courts of Appeals, maintain that websites are public accommodations just by virtue of providing a service.

The courts argue that there is precedent for nonphysical spaces counting as public accommodations. They wipe the dust off an old case, ADA-wise: the Carparts Distribution Center, Inc. v. Automotive Wholesaler's Association of New England case from 1994. In Carparts, the First Circuit ruled that the ADA covered phone-based services. They noted that Congress had included travel services in the list of example public accommodations. At the time, the travel services industry was largely telephone-based, so the First Circuit reasoned that obviously Congress intended to include nonphysical spaces such as telephone lines.

In their Carparts ruling, the First Circuit noted that:

"It would be irrational to conclude that persons who enter an office to purchase services are protected by the ADA, but persons who purchase the same services over the telephone or by mail are not. Congress could not have intended such an absurd result."

—First Circuit Court of Appeals, Carparts Distribution Ctr. v. Automotive Wholesaler's Ass'n.

The Seventh Circuit court has applied this reasoning to an insurance company that sold its services online:

"The defendant asks us to interpret 'public accommodation' literally, as denoting a physical site, such as a store or a hotel, but we have already rejected that interpretation. An insurance company can no more refuse to sell a policy to a disabled person over the Internet than a furniture store can refuse to sell furniture to a disabled person who enters the store."

—Seventh Circuit Court of Appeals, Morgan v. Joint Admin. Bd.

Netflix, Scribd, and Blue Apron have all found themselves at the receiving end of courts of this opinion.


Opinion #2: No, Websites Are Not Public Accommodations

If the First Circuit's Carparts ruling seems like a bit of a stretch to you, you're not alone.

Courts of this opinion, such as the Third, Fifth, and Sixth Circuit Courts, point to the ADA's full wording: "place of public accommodation." Nonphysical spaces such as websites, they argue, aren't places, and therefore they aren't covered by Title III. To claim that they are covered would be to vastly expand the scope of the law:

"Here, to fall within the scope of the ADA as presently drafted, a public accommodation must be a physical, concrete structure. To expand the ADA to cover 'virtual' spaces would be to create new rights without well-defined standards."

—District Court for the Southern District of Florida, Access Now, Inc. v. Southwest Airlines, Co.

Full disclosure: the Southern District of Florida actually sided with Opinion #3 in the Southwest Airlines case. This line just happens to be a very succinct explanation of Opinion #2.

These courts often explicitly reject the Carparts ruling as an overreach:

"In arriving at this conclusion, the First Circuit disregarded the statutory canon of construction, noscitur a sociis. [...] The doctrine of noscitur a sociis instructs that 'a ... term is interpreted within the context of the accompanying words 'to avoid the giving of unintended breadth to the Acts of Congress.'' [...] The clear connotation of the words in §12181(7) [the list of examples of public accommodations] is that a public accommodation is a physical place. Every term listed in §12181(7) and subsection (F) is a physical place open to public access."

—Sixth Circuit Court of Appeals, Parker v. Metropolitan Life Ins. Co., citations omitted

Other cases that have made similar arguments and have been used as precedents within these courts include Ford v. Schering-Plough Corp. and Weyer v. Twentieth Century Fox Film Corp..

Additionally, the ADA has been amended several times since the rise of the internet. If Congress really did intend for the ADA to cover nonphysical spaces such as websites, surely they would have included that in one of the amendments, right?^4


Opinion #3: Websites Are Sometimes Public Accommodations

The most frequent court opinion about websites as public accommodations kind of sidesteps the question altogether by claiming that websites can be extensions of public accommodations.

"While there is some disagreement amongst district courts on this question, it appears that the majority of courts agree that websites are not covered by the ADA unless some function on the website hinders the full use and enjoyment of a physical space."

—District Court for the Southern District of Florida, Gomez v. Bang & Olufsen Am., Inc.

This is the principle of nexus: if a website has a significant connection to the goods and services offered by a physical public accommodation, then the website is seen as an extension of the public accommodation. In that case, it would be subject to Title III. After all, Title III forbids obstructing access to the goods and services "of any place of public accommodation," not "in any place of public accommodation."

The first federal trial on web accessibility to be carried out in full was Gil v. Winn-Dixie in 2017. Winn-Dixie offered digital coupons on their website that were only redeemable in their brick-and-mortar stores. Additionally, Winn-Dixie gave customers the option to refill their prescriptions online, but the refills also had to be picked up in-store. The Southern District of Florida determined that the Winn-Dixie website therefore had a nexus to the brick-and-mortar franchises. Thus, the website's incompatibility with screenreaders was a violation of the ADA.^5

Nexus does go the other way. In Earll v. eBay, Inc., for instance, a deaf plaintiff sued eBay since she couldn't use the site's phone-based vendor verification service. The Ninth Circuit determined that, since eBay doesn't have any consumer-facing, brick-and-mortar locations, eBay is not a public accommodation and is not subject to Title III.^6 Netflix, Viacom, Facebook, and Southwest Airlines have also been defended with a similar argument.

Much like it did during the Winn-Dixie case, the Ninth Circuit applied the nexus argument to Domino's this January when overturning the district court's dismissal of Robles's case:

"Domino's website and app facilitate access to the goods and services of a place of public accommodation — Domino's physical restaurants. They are two of the primary (and heavily advertised) means of ordering Domino's products to be picked up at or delivered from Domino's restaurants. We agree with the district court in this case — and the many other district courts that have confronted this issue in similar contexts — that the ADA applies to Domino's website and app, which connect customers to the goods and services of Domino's physical restaurants."

—Ninth Circuit Court of Appeals, Robles v. Domino's Pizza


Takeaways

The Robles v. Domino's Pizza case is just one of many court cases centered around whether American law requires websites to be accessible. The number of web accessibility-related lawsuits is only going to go up from here as courts continue to give mixed opinions on the matter.

By appealing the Ninth Circuit's decision, Domino’s Pizza is giving the Supreme Court the opportunity to affirm, finally, whether websites are inherently public accommodations, whether they're inherently not public accommodations, or whether they count as public accommodations if a nexus is present.

However, while the question of whether the ADA covers websites is important, it's not the only question Domino's is contesting. Stick around for Part 2, where we'll cover magic checklists and due process.

Footnotes

^1 The National Law Review, When Good Sites Go Bad: The Growing Risk of Website Accessibility Litigation

^2 The Washington Post, Do protections for people with disabilities apply online? Domino’s asks high court.

^3 That is, to an extent. The twelve subcategories listed are pretty fixed, but enough of the subcategories include "or other X" clauses that this list is pretty open to interpretation.

^4 District Court for the Eastern District of Virginia, Carroll v. Northwest Federal Credit Union

^5 District Court for the Southern District of Florida, Gil v. Winn-Dixie

^6 Ninth Circuit Court of Appeals, Earll v. eBay, Inc.

Top comments (0)