ADA Compliance: Websites Need to Be Accessible Too

by Emily Ayoob, 30 11 2019

In recent years, a new kind of ADA compliance lawsuit has emerged. Indeed, plaintiffs have started targeting websites—including websites operated by non-U.S. entities—for failure to comply with the Americans with Disabilities Act (“ADA”) of 1990.

The Americans with Disabilities Act was enacted in 1990 to prohibit discrimination against disabled persons and to ensure that disabled persons enjoy equal rights and opportunities. In particular, Title III of the ADA provides that “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.” The ADA itself, which was enacted before the Internet became widespread, only lists physical places as examples of “places of public accommodation.” That has not stopped plaintiffs from bringing claims against websites. In doing so, they benefit from the support of the Department of Justice (“DOJ”), which has stated, in guidance it has issued on the ADA, that it has interpreted the ADA to cover websites operated by public accommodations.

Courts have also been receptive to such claims, agreeing to hear them despite defendants’ objections. There is, however, a split among courts as to which websites fall within the scope of the ADA. Some courts have ruled that places of public accommodation do not need to be physical places, and that, therefore, websites themselves could be places of public accommodation. For instance, in National Federation of the Blind v. Scribd Inc., the United States District Court for the District of Vermont found that a digital library offering reading subscription services via a website was a place of public accommodation. The court (and others like it)’s rationale is that Congress, in enacting the ADA, intended for the Act to have broad coverage so that disabled people would be able to fully participate in all aspects of society, and that, although when the ADA was enacted in 1990, the Internet was only in its infancy, it has now become central to many aspects of society. On the other side of the split, some courts require a strong nexus between the website and a physical place of public accommodation for the website to be covered by the ADA. For instance, earlier this year, in Robles v. Domino’s Pizza, LLC, the United States Court of Appeals for the Ninth Circuit noted that “Domino’s website and app facilitate access to the goods and services of a place of public accommodation—Domino’s physical restaurants,” and therefore ruled that the ADA applied to the website (and – it must be noted – the mobile app). The court emphasized that the nexus between the website and the physical place of public accommodation was “critical” to its analysis.

Although many of the cases brought so far have focused on Title III of the ADA, new cases are now being brought under Title I. Title I prohibits discrimination on the basis of disability in the context of job application, hiring, advancement and dismissal of employees, and terms and conditions of employment. For instance, in Kasper v. Ford Motor Co., a case filed earlier this year, the plaintiff is alleging that the defendant violated Title I by failing to offer disabled people a proper accessible alternative to their online job application process.

For the time being, the exact standard websites should adhere to in order to be in compliance with the ADA remains unclear. The DOJ has not yet made available any guidance on website compliance with the ADA and may not do so in the near future. The DOJ has recently reiterated, however, that the “absence of a specific regulation does not serve as a basis for noncompliance” with the ADA. As a result, businesses operating a website have little choice but to turn to privately created standards, the most commonly relied-upon standard being the Web Content Accessibility Guidelines (“WCAG”) 2.0. WCAG 2.0 contains guidance on how to make websites perceivable, operable, and understandable for people with disabilities, as well as robust (i.e. able to withstand changes in technology). At least one court—the United States District Court for the Southern District of Florida in Gil v. Winn Dixie Stores, Inc.—has ordered a company to ensure that its website conforms with WCAG 2.0. The DOJ has nonetheless specified recently that “noncompliance with a voluntary technical standard for website accessibility [such as WCAG 2.0] does not necessarily indicate noncompliance with the ADA,” thereby affording some flexibility to websites on how they comply with the ADA. However, it is generally considered best practice for all websites to meet basic accessibility criteria, not just because of the threat of an ADA lawsuit, but because it simply sends a more positive message to all consumers. In addition, compliance with basic accessibility guidelines should be standard practice, as the skills, effort and/or tools required to meet such guidelines should be minimal for most developers.

In sum, in the absence of further clarification by the DOJ, Congress, or the Supreme Court on which websites fall within the scope of the ADA, and on what compliance with the ADA exactly entails for a website, it is advisable for any website that could potentially have US-based visitors to comply with WCAG 2.0 in order to mitigate the risk of ADA compliance lawsuit.

Back to blog