Now you know that some types of content and format on webpages can pose barriers for people with disabilities. The next steps are to develop an action plan to fix web content that is currently inaccessible and implement procedures to ensure that all new and modified web content is accessible. The website accessibility checklist included in this section helps you assess what needs to be done.
The Department of Justice’s revised regulations for Titles II and III of the Americans with Disabilities Act of 1990 (ADA) were published in the Federal Register on September 15, 2010. These regulations adopted revised, enforceable accessibility standards called the 2010 ADA Standards for Accessible Design, "2010 Standards." On March 15, 2012, compliance with the 2010 Standards was required for new construction and alterations under Titles II and III. March 15, 2012, is also the compliance date for using the 2010 Standards for program accessibility and barrier removal.
UPDATE: Since writing this post in August 2017, several important changes have taken place in the laws regarding ADA compliance for websites. On December 26, 2017, the Department of Justice announced that they have withdrawn the Obama-era Advance Notice of Proposed Rulemaking mentioned in this article which intended to require ADA website compliance. The DOJ’s withdrawal announcement stated, “The Department will continue to assess whether specific technical standards are necessary and appropriate to assist covered entities with complying with the ADA.”
The Department of Justice (DOJ) has specifically stated in rulings that websites should be designed so they are accessible to individuals who have vision, hearing, and physical disabilities. There’s a growing body of case law where the DOJ required companies to provide an ADA compliant website and levied hefty penalties when sites failed to measure up.
Meanwhile, the tech community and our courts system were forced to deal with the issue on their own. First, the tech community coalesced around a set of standards via the World Wide Web Consortium, establishing the Web Content Accessibility Guidelines in 2008 and later updating them in 2012 (WCAG 2.0), when they were also adopted as an ISO standard. Today, web designers and developers across the world use WCAG 2.0 to guide their design and development, typically aiming to meet all of the standards under Level AA.
ADA website compliance is about making sure that everyone has equal access to all the elements on your website and apps. That may mean you need to provide alternatives for some of the functions and content on your site in order to meet ADA website compliance standards. Here’s a quick rundown of some of the accommodations that need to be incorporated into your website to meet the ADA guidelines:
The ADA guidelines provide the foundation that organizations need to achieve digital accessibility best approaches, however they are not exhaustive. They do not provide direction for all of the accessibility challenges that people with disabilities face. They also fail to provide detailed technical instructions. With these limitations in mind, there is a ray of hope.

HTML tags – specific instructions understood by a web browser or screen reader. One type of HTML tag, called an “alt” tag (short for “alternative text”), is used to provide brief text descriptions of images that screen readers can understand and speak. Another type of HTML tag, called a “longdesc” tag (short for “long description”), is used to provide long text descriptions that can be spoken by screen readers.
All of that was well and good in 1990, when the then-nascent Internet was not the ubiquitous presence in the lives of Americans that it is today. For example, retail shopping in-person at a mall in 1990 was booming, unlike today where online shopping has completely changed the game for retailers. As time and technologies evolved however, the Department of Justice (DOJ), the entity charged with enforcing the ADA, hinted but never definitively stated that Title III may indeed be applicable to websites.