Skip to main content
Menu

Main navigation

  • About
    • Annual Reports
    • Leadership
    • Jobs
    • Student Programs
    • Media Information
    • Store
    • Contact
    LOADING...
  • Experts
    • Policy Scholars
    • Adjunct Scholars
    • Fellows
  • Events
    • Upcoming
    • Past
    • Event FAQs
    • Sphere Summit
    LOADING...
  • Publications
    • Studies
    • Commentary
    • Books
    • Reviews and Journals
    • Public Filings
    LOADING...
  • Blog
  • Donate
    • Sponsorship Benefits
    • Ways to Give
    • Planned Giving

Issues

  • Constitution and Law
    • Constitutional Law
    • Criminal Justice
    • Free Speech and Civil Liberties
  • Economics
    • Banking and Finance
    • Monetary Policy
    • Regulation
    • Tax and Budget Policy
  • Politics and Society
    • Education
    • Government and Politics
    • Health Care
    • Poverty and Social Welfare
    • Technology and Privacy
  • International
    • Defense and Foreign Policy
    • Global Freedom
    • Immigration
    • Trade Policy
Live Now

Cato at Liberty


  • Blog Home
  • RSS

Email Signup

Sign up to have blog posts delivered straight to your inbox!

Topics
  • Banking and Finance
  • Constitutional Law
  • Criminal Justice
  • Defense and Foreign Policy
  • Education
  • Free Speech and Civil Liberties
  • Global Freedom
  • Government and Politics
  • Health Care
  • Immigration
  • Monetary Policy
  • Poverty and Social Welfare
  • Regulation
  • Tax and Budget Policy
  • Technology and Privacy
  • Trade Policy
Archives
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • Show More
June 29, 2012 4:43PM

The ADA and the Internet

By Julian Sanchez

SHARE

Law professor Eric Goldman points to a "really terrible" ruling in a case called National Association of the Deaf v. Netflix that "has potentially ripped open a huge hole in Internet law" by concluding that Internet sites are "places of public accommodation" for the purposes of the Americans with Disabilities Act, simply ignoring a boatload of precedent concluding just the opposite. As Goldman explains, this is apt to unleash a costly and innovation-stifling flood of litigation:

Could YouTube be obligated to close-caption videos on the site? (This case seems to leave that door open.) Could every website using Flash have to redesign their sites for browsers that read the screen? I'm not creative enough to think of all the implications, but I can assure you that ADA plaintiffs' lawyers will have a long checklist of items worth suing over. Big companies may be able to afford the compliance and litigation costs, but the entry costs for new market participants could easily reach prohibitive levels.

And then there's linkages with other civil rights statutes, such as Title II of the Civil Rights Act of 1964 (an anti-discrimination law) and state laws, that use similar language as the language interpreted in this ruling. If all of those statutes are back in play too, the range of obligations imposed on websites--and the opportunities for aggressive plaintiffs' lawyers--expand exponentially. Expect lots of consumer claims that a website discriminated against them based on an impermissible criterion. It's safe to say that the legal rules at issue in this case could have billions of dollars of impact between the web coding obligations and the potential litigation frenzies.

That wouldn't be terribly surprising: The ADA has certainly led to its share of costly unintended consequences in the physical realm. But there are a few reasons why the statute seems particularly ill-suited for application to the Web.

At the risk of belaboring the obvious: Web sites are not "places" at all, except in a metaphorical sense: They are streams of information transmitted to users. (There is, of course, some physical place where the server is located, but that place is typically not physically open to the public.) The court treats this as a kind of trivial semantic distinction rendered moot by the advance of technology, even suggesting that it would be "absurd" to exempt Netflix and Amazon from the rules written for the local cineplex and bookshop. But there are actually quite a few crucial distinctions between Internet sites and traditional brick-and-mortar businesses, which make it a rather surprising leap to insist that a statute designed for literal "places" naturally extends to the metaphorical digital "sites" that serve similar functions.

First, information streams, unlike actual places, are intrinsically made of speech. That certainly doesn't mean the First Amendment is some kind of blanket get-out-of-regulation-free card for businesses engaged in online commerce, but it does mean that expressive rights will often be implicated when changes to the virtual "place" or "service" are demanded, in a way they are typically not when a shop is required to install a wheelchair ramp. Online, the boundary between being compelled to act and being compelled to speak is especially porous. Again, that's not an absolute bar to regulation, but it seems odd to assume that Congress must have intended to create such broad causes of action against what are essentially publishers of information, when the examples used to define "public accommodation" very conspicuously don't include any producers of content. "Places of exhibition entertainment" are covered, but not the content of the entertainment itself—which is why the ADA doesn't require DVD makers to provide caption tracks (though most do) or books and periodicals to run large-print editions. As the court observes, Congress probably could not have anticipated Netflix or Amazon when it passed the ADA in 1990—yet it presumably had at least a passing familiarity with the concept of magazines and videotapes. It does not seem terribly mysterious that Congress nevertheless declined to invite the routine conflict with expressive rights that would predictably result from shoehorning publishers of information under the same regulatory rubric as physical businesses.

Second, physical businesses and their customers—disabled customers in particular—are inherently constrained by distance and the costs of transit in a way virtual "places" are not, which importantly changes the cost-benefit calculus for all concerned. Outside major metropolitan areas, there may be only one or two businesses of a particular type local to some disabled persons, which for practical purposes means they must be able to access that facility if they are to avail themselves of the relevant class of goods or services at all. Conversely, since physical businesses are generally competing only for the patronage of the local population, owners may be more likely to conclude that it doesn't make economic sense to invest in accessibility aids that will only be needed by a handful of customers.

Things are obviously quite different online. As a general rule, any site on the Web is accessible from anyplace else, which means the inaccessibility of any particular site is less likely to represent a significant practical reduction of the choice set of any individual disabled user. One common argument for imposing the ADA's universal obligations on physical businesses is that it may be unrealistic to expect the disabled in particular to simply "go somewhere else" if the nearest business can't accommodate their needs. That argument has less traction in a landscape without distances. But what if none (or very few) of the businesses in a particular sphere implement some particular desired accommodation? Online, that's much more likely to be evidence that it would be unduly costly or burdensome to do so—and therefore beyond the ADA's requirements—because sites are typically competing for a national (if not global) pool of hearing and visually impaired customers.

The suit against Netflix is actually an excellent illustration. The National Association of the Deaf is arguing that Netflix runs afoul of the ADA by failing to provide closed-captioning for all of the movies it makes available to "Watch Instantly" online, among other things. Now, there are something like 35 million hearing impaired people in the United States, and more than a million who are functionally deaf. One can imagine the manager of the lone local theater deciding it's not worth even a relatively small investment to accommodate a handful of disabled potential patrons. It's much harder to believe that Netflix is just arbitrarily dragging its heels in making its offerings more appealing to such an enormous potential market: To the extent it's feasible to do at a reasonable cost, they have ample incentive to be doing it without legal prodding—an incentive magnified by the speed with which Web businesses that get complacent fall to more innovative competitors eager to spot those missed opportunities for improvement. (Anyone remember Altavista and Friendster?)

As Netflix's attorneys point out, the real holdup isn't, in fact, a lack of will so much as an inability to act unilaterally: They're obliged to negotiate with the copyright owners of the movies they stream. The court correctly responds that this specific argument doesn't affect whether Netflix is classed as a "public accommodation": Rather, it's a defense they could raise after that determination is made to show they're complying with the ADA as far as they're able. But there are reasons to think there would nearly always be such a defense, because the nature of the online economy should generate far stronger pressure for someone to step in and serve disabled users unless it's infeasible or prohibitively costly—and for incumbent businesses to preempt any new entrants who'd exploit their failure to do so. Congress judged the ADA necessary based on the history of brick-and-mortar businesses where the constraints of space and distance might be thought to attenuate those pressures. Assuming, without further legislative guidance, that the same regulatory regime is appropriate where those constraints are absent is a bit like applying a statute prohibiting animal cruelty in stables to car manufacturers: Cars and horses may serve many of the same social functions, but they differ in the key respect that provided the rationale for regulation. This may be one reason Congress declined to augment its illustrative list of "public accommodations" to include any purely virtual spaces when it extensively amended the ADA in 2008.

Finally, and perhaps most importantly, users are constrained to take physical spaces more or less as they find them. The owner can make changes in the physical environment; the user or patron cannot. If a theater does not provide wheelchair ramps or wheelchair-friendly viewing spaces, there is not a whole lot a disabled patron can realistically do to change that fact at a reasonable cost. Websites are quite different: How they're experienced is, in practice, always a collaborative fact determined partially by the code served by the site itself, and partially by the end-user's browser. If you are experiencing this post as a string of written characters in medium-size on a screen, that is not because of any natural fact about the Cato blog as a "place," but because you have a computer system configured to interpret the binary stream transmitted by Cato's servers in that way. Your current browser could easily be reconfigured to display it as much larger text; your operating system probably has an option to deliver that text as a computer-generated audio; and with the right browser and peripherals, you could render it as Braille or a series of odors instead. Even assuming a site's content is rendered in the statistically "normal" way, the fact that this content is delivered to a highly configurable computing environment under the end-user's ultimate control means it will usually be vastly simpler for adjustments necessary to compensate for special needs to be made client-side rather than server-side.

This is self-evident for at least some cases: Given the widespread availability of browsers and operating systems that can speak written text out loud—however imperfectly—nobody thinks it would make sense to require every individual Web site to provide a spoken audio file corresponding to each page of text. As of 2012, voice recognition software is not nearly good enough to allow automated on-the-fly rendering of movie captions, but that doesn't mean provision by the provider of the audio-video stream is the only alternative. There are online repositories like the Internet Movie Script Database and (probably more useful in this context) OpenSubtitles.org, providing crowdsourced, time-synched captions for popular movies—combining a client-side solution with a community-based third party resource.

With physical facilities, it will often be obvious in advance which adaptations for disabilities must be provided by the owners of the facility itself (wheelchair ramps; wheelchair-accessible bathroom stalls) and which are more properly the responsibility of the disabled patron and third-party companies (the wheelchair itself). With Web sites, this will not necessarily be nearly as clear in advance, but there's ample reason to expect that client-side solutions will often be simpler and less costly. Applying the ADA to the Web effectively locks in a presumption in favor of server-side solutions that is highly unlikely to be optimal. Especially given the speed at which Internet technologies and platforms evolve, it seems far more sensible to stand back and let businesses and online communities determine the most appropriate locus for adaptation as new services and platforms arise.

Related Tags
Constitutional Law, Technology and Privacy, Robert A. Levy Center for Constitutional Studies

Stay Connected to Cato

Sign up for the newsletter to receive periodic updates on Cato research, events, and publications.

View All Newsletters

1000 Massachusetts Ave. NW
Washington, DC 20001-5403
202-842-0200
Contact Us
Privacy

Footer 1

  • About
    • Annual Reports
    • Leadership
    • Jobs
    • Student Programs
    • Media Information
    • Store
    • Contact
  • Podcasts

Footer 2

  • Experts
    • Policy Scholars
    • Adjunct Scholars
    • Fellows
  • Events
    • Upcoming
    • Past
    • Event FAQs
    • Sphere Summit

Footer 3

  • Publications
    • Books
    • Cato Journal
    • Regulation
    • Cato Policy Report
    • Cato Supreme Court Review
    • Cato’s Letter
    • Human Freedom Index
    • Economic Freedom of the World
    • Cato Handbook for Policymakers

Footer 4

  • Blog
  • Donate
    • Sponsorship Benefits
    • Ways to Give
    • Planned Giving
Also from Cato Institute:
Libertarianism.org
|
Humanprogress.org
|
Downsizinggovernment.org