The need to make websites, mobile apps, and other online properties accessible to all is only going to increase as time moves on. Smart business owners will do well to get in front of this issue and make sure that their websites are ADA compliant now so that all their customers have the equal access to the resources they offer. Not just because they want to avoid a lawsuit or government action, but because it’s the right thing to do.
Absent the adoption of specific technical requirements for websites through rulemaking, public accommodations have flexibility in how to comply with the ADA’s general requirements of nondiscrimination and effective communication. Accordingly, noncompliance with a voluntary technical standard for website accessibility does not necessarily indicate noncompliance with the ADA.
In January of 2017 the federal government moved forward with the adoption of WCAG 2.0 AA as the standard for federal agency sites, leading many in the accessibility community to believe that a full adoption of the WCAG 2.0 Level AA standards by the DOJ for websites both public and private would be forthcoming. As of the writing of this post, that has neither occurred nor been added to the DOJ’s agenda, likely due to the installation of a new administration and other legislative priorities.
Case law has been the most helpful in illuminating the implications of the ADA for websites.There have been lawsuits involving companies like Expedia, Hotels.com, Southwest Airlines, and Target as defendants and primarily featuring accessibility organizations as plaintiffs. These cases had mixed results, but each helped clarify the ADA's jurisdiction on the web.
Another important consideration is that the ADA does not allow businesses to simply provide an alternative such as a phone number. Lastly, include accessibility issues as part of your website and mobile strategy. When new technologies are implemented or pages added, part of the process should include the implications for persons with disabilities.
In response to the members’ concern about the proliferation of website litigation lawsuits, DOJ said: “Given Congress’ ability to provide greater clarity through the legislative process, we look forward to working with you to continue these efforts.” DOJ is essentially putting the ball back in the Congressional court, where little is likely to happen.
That’s good news if you are one of the many Americans who have a visual, hearing, or mobility disability that makes it difficult to access some information on the web. If you are a business owner who hasn’t made provisions to ensure that your website and other online assets are ADA compliant, you could be looking at a host of legal and financial penalties.
Leading web developers have been pioneering accessibility and publishing standards since 1994. In 1999, the Web Accessibility Initiative (WAI) and the World Wide Web Consortium (W3C) created the Web Content Accessibility Guidelines (WCAG). In essence, the people who determine how the internet is written came together to advise web developers on how to make websites accessible not only to people with disabilities, but to all web users, including those with highly limited devices.
Tags: 2.0, 2.1, 2010, accessibility, ADA, Advanced Notice of Proposed Rulemaking, ANPRM, attorney general, Congress, Department of Justice, Due Process, effective communication, House of Representatives, Interpretation, Jeff Sessions, June, Legal Action, litigation, motion to dismiss, public accommodations, September 25, Staffed Telephone, Standards, Statutory Authority, Title III, WCAG, Web Content Accessibility Guidelines, website
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.
While legal considerations might be your biggest worry, making your site more accessible is simply good customer service. More than 39 million Americans are blind and another 246 million have "low vision," Another one million are deaf in the U.S. Add to that people with mobility issues that prevent them from using their hands and that's a huge portion of the country's buying power.
Up-to-date standards are offered for checking compliance, and it provides a cost-effective way to scan a site for compliance. There's services out there where it'd cost more than $150 (the current cost of a 1 site 1 year license) for the size of the sites I'm working with. I'm very happy to see this offering in the first place, and it's even nicer to see how thorough it looks to be. Of course, it's not perfect so I'd love to see more of the WP.org listing fleshed out (the developer author/contributor mention is missing, etc.), I'd love to see the free version on GitHub (or similar for community development assistance [I have a few things I'd help with] which is very nice to see in a WP.org listing to show there's support / ongoing development for the plugin), and of course I'd love to see the server-side checker come to feature-parity with WAVE (currently WAVE is showing a few things the server-side checker doesn't have [color contrast, etc.]) Keep up the great work!
VERY useful. I searched for a plugin that had WAVE scanning integrated and this plugin came up. I was a bit hesitant because there were only a few reviews and the price was higher than most plugins. However, if the plugin worked, it would save me $1,000 from requesting a WAVE scan of my entire site. In short, this plugin is amazing. It is super-detailed. That makes it a bit longer to learn and master. However it makes it amazingly useful. If you take compliance seriously, this is the plugin for you. I am not a developer, but understand more about coding than the average content creator. I was able to understand this plugin, though it took several hours. Don't take that as a bad thing. It was necessary, and I learned a TON about ADA compliance in the meantime. When I had a question, the author was super-fast and helpful. I highly recommend this plugin.
Technology is changing, and many website designers are using creative and innovative ways to present web-based materials. These changes may involve new and different access problems and solutions for people with disabilities. This Chapter discusses just a few of the most common ways in which websites can pose barriers to access for people with disabilities. By using the resources listed at the end of this Chapter, you can learn to identify and address other barriers.
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).