Navigating the History of Website Accessibility & the Law in the U.S.

Image for post
Image for post
There have been attempts to add website accessibility enforcement support over the years. Each has been met with failure.

However, while the United States debates the merits of website accessibility for the general public and Title III of the ADA for today’s digital landscape, the number of lawsuits has soared.

There is no official set of website accessibility standards or criteria set forth by the US Department of Justice for businesses to comply with, other than Section 508 under Title II. In fact, most recently, a new law was signed with regards to Federal agencies only.

The H.R. 5759 21st Century Integrated Digital Experience Act (IDEA) was signed into law on December 20, 2018. (

It is easy to skim this law and believe it pertains to every website, including a simple blog, or is related to Title III of the ADA, which it is not. The House of Representatives tried to nudge the needle with H.R. 620 ADA Education and Reform Act of 2017 ( in an attempt to block the rising tide of ADA lawsuits, but it was poorly conceived and would have created more harm than good to the ADA, so it was blocked by the Senate.

There is no denying the demand for universal and inclusive design and the positive, welcome contributions enabling billions of people through advances in computer technology and software development. Unfortunately, accessibility for websites has not been a priority. It requires new skills and training. It should be built into every development cycle and added to business requirements because it is the right thing to do. Most accessibility testing tools are free to use. WCAG2.1 and Section 508 guidelines, the basis for compliance around the world, are provided for free on the web.

So why are there so many lawsuits? What is causing the confusion in the US? I wanted to be better informed and ready with facts for my clients and friends with websites.

The Americans with Disabilities Act in the USA and Website Accessibility Enforcement

On July 26, 1990, the late President George H.W. Bush signed into law the Americans with Disabilities Act (ADA), which is a civil rights law prohibiting discrimination on the basis of disability.

Its purpose is to protect the rights of individuals with disabilities for employment, access to state and local government services, places of public accommodation, transportation, and more.

On July 26, 1991, the DOJ issued its final rules for following Title II and Title III but neither addressed website accessibility.

Title II of the ADA applies to state and local government entities. It protects individuals with disabilities from discrimination on the basis of disability in services, programs, and activities provided by state and local government entities. What we refer to as Section 508 web accessibility falls under Title II.

Title III prohibits discrimination on the basis of disability in the activities of places of public accommodations. These are businesses that are generally open to the public and there are 12 categories, including schools, recreation, offices, and medical buildings.

Your ecommerce website and public mobile applications fall under Title III.

Section 508 & Title II

In June 2003, in recognition of how the Internet was transforming interactions between the public and governmental entities, the DOJ published , to provide state and local governments guidance on how to make their websites accessible and ensure that persons with disabilities have equal access to the services, programs, and activities that are provided through those websites.

Title III was not included with this update.

The gap between government and public website accessibility began to confuse companies that conduct online business with the government and schools with websites, such as universities that accept federal financial aid.

Website Accessibility Roller Coaster

There have been attempts to add website accessibility enforcement support over the years.

Each has been met with failure.


On September 30, 2004, the DOJ began the process of updating the 1991 regulations based on the relevant parts of the by publishing an (ANPRM) and inviting public comment.

On June 17, 2008, the DOJ issued a Notice of Proposed Rulemaking to adopt the revised 2004 ADA/ABA Guidelines and revise Title II and Title III regulations. The 2008 NPRM addressed the issues raised in the public’s comments to the 2004 ANPRM and sought additional comments.

Neither the 2004 ANPRM or 2008 NPRM included a proposal for web accessibility provisions despite public comments urging the DOJ to issue web accessibility regulations under the ADA.

The went into effect on January 1, 2009.

Among other things its purpose was to make updates to the existing law and carry out the ADA’s objectives of providing:

On July 26, 2010, the DOJ published an ANPRM titled . This was the first attempt to include website accessibility enforcement.

On September 15, 2010 Titles II and II were revised again and called the . They did not include web accessibility.

Hopes were raised when in the fall of 2015, the DOJ released a that included three paragraphs on website accessibility.

This document addressed the realization that it became impractical to separate Title II (Government websites) and Title III (public websites) because they are often blended together. The document states:

It went on to state that they “

That never happened.

In April 29, 2016, the DOJ issued a new SANPR called .

It is one of four ADA rulemaking documents that were removed and are now archived.

This particular document provides real insight into what’s complicating matters and why the government is unable to come up with any formal legislation on website accessibility.

It’s worth reading if you want to understand the history and read the public comments.

Next, the House of Representatives introduced which stalled in the Senate. There were many issues with it, from costs to the lack of what accessibility standards would be enforced and most importantly, the responsibility for resolution fell to the disabled plaintiff, not the business.

On June 20, 2018, 103 members of the U.S. House of Representatives drafted a letter to then Attorney General of the Justice Department, Jeff Sessions, regarding the flood of lawsuits and the ease of litigation when there are no legal standards to follow.

On September 25, 2018, the DOJ responded in a letter to Congressman Ted Budd. It references the withdrawal of the four rulemaking attempts to address website accessibility and the ADA and why.

The DOJ is It references two Executive Orders covering the reduction of regulations and controlling costs.

In addition, this section caught the attention of law firms:

Providing an accessible website or application is strongly recommended. Other countries sorted out how to budget, enforce and advocate full access to the digital world. The US may not have its ducks in a row but that isn’t preventing companies from building accessible websites and creating opportunities for equal access to the web for everyone.

Author’s Notes:

This article is adapted from Website Accessibility & the Law: Why Your Website Must Be Compliant, also written by me.

For Your Reference

Usability & Accessibility Specialist, Creative Vision Web Consulting; Speaker/Writer;

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store