DOJ’s September 25 response did not do what the members asked, but it did provide some helpful guidance and invited Congress to take legislative action to address the exploding website accessibility litigation landscape. DOJ first said it was “evaluating whether promulgating specific web accessibility standards through regulations is necessary and appropriate to ensure compliance with the ADA.” (This is helpful – to at least know this issue has not fallen totally off DOJ’s radar.) It continued:
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.”
Basically, there are standards which apply to US federal agencies, and State or Local Government websites (not business/personal websites). While some disability discrimination laws do mention websites, they don’t specify the technical standards required to comply with the law. Regardless of ADA’s lack of stating websites must be fully accessible, the Department of Justice seems to rule on the side of “they should be”.
State and local governments will often post documents on their websites using Portable Document Format (PDF). But PDF documents, or those in other image based formats, are often not accessible to blind people who use screen readers and people with low vision who use text enlargement programs or different color and font settings to read computer displays.
The words in the tag should be more than a description. They should provide a text equivalent of the image. In other words, the tag should include the same meaningful information that other users obtain by looking at the image. In the example of the mayor’s picture, adding an “alt” tag with the words “Photograph of Mayor Jane Smith” provides a meaningful description.
However, this doesn’t mean you should ignore ADA or web accessibility. What we do know, is that all websites should be given a good-faith-effort of becoming easily accessible. This should be the case for any user who may wish to browse your website, regardless of their disability of type of impairment. They deserve it. Making your website accessible benefits an array of individuals and businesses.
For example, you may have thousands of images on your website that need to be checked for the presence of “alt text,” which is a requirement under WCAG 2.0. This is a task for automated testing software, which can perform the job much faster than any human. While automated tools can detect if the images on your website have alt text, however, they aren’t able to determine whether the text is correct and meaningful—which is a job for human testers.
For close to seven years, since July of 2010, the United States Department of Justice (DOJ) has talked about issuing regulations specifically about web accessibility. At that time the US Department of Justice (DOJ) began developing accessibility guidelines for public websites under Title III of the Americans with Disabilities Act (ADA). On December 26, 2017, the Department announced that those regulations were officially withdrawn.
Your company’s website is your primary communications tool and a vital part of your infrastructure. Your clients and customers -- both current and potential -- are coming to you from a wide range of backgrounds, experiences and perspectives. It makes good business sense to have a site that is accessible to as many people as possible to demonstrate to your users and clients that you understand their needs and want to meet them where they are in order to best serve them.
Legal precedent is changing, and ADA compliance related lawsuits are becoming more successful, and the courts are seeing more of them as a result. Title III of the Americans with Disabilities Act pertains to private sector businesses. Lately, those protections are more frequently expanding into digital territory as web and mobile applications become more necessary in our day-to-day lives.
As a web developer, Ryan's work is what makes the magic happen. He spends most of his time creating custom websites, which involves turning the designers' visual mockups into code. It's lucky that he's such a good problem solver, because many of Ryan's projects involve working with clients to create complex custom functions. He's also one of the few developers in the country with extensive experience developing for the HubSpot CMS.
The Department has assembled an official online version of the 2010 Standards to bring together the information in one easy-to-access location. It provides the scoping and technical requirements for new construction and alterations resulting from the adoption of revised 2010 Standards in the final rules for Title II (28 CFR part 35) and Title III (28 CFR part 36).