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.
This past September marked the first time a judge ruled that the ADA applies even to businesses without a physical location. Scribd, an e-book subscription service is considered to provide "a place of public accommodation." Their services are not accessible to blind persons because they cannot be read with a screen reader. The judge reasoned, "Now that the Internet plays such a critical role in the personal and professional lives of Americans, excluding disabled persons from access to covered entities that use it as their principal means of reaching the public would defeat the purpose of this important civil rights legislation."
Yes, in time non-ADA compliant websites will be penalized in the search engines. It's already on their radar. But for now they are still negatively affected, just in an indirect way. Live traffic behavior (user experience) is now factored into Google's algorithm and is a ranking signal. Negative user interactions absolutely have negative affects on rankings.
It’s well-known that the Americans With Disabilities Act (ADA) requires brick-and-mortar businesses be accessible to all patrons. This includes considerations like wheelchair accessibility and Braille or large print for blind and low-vision patrons, among other things. The ADA references “public accommodations,” and outlines 12 categories that essentially covers all types of public-facing businesses. However, the legislation does not address public-facing websites.
On July 26, 2010 (on the anniversary of the Americans with Disabilities Act) President Obama stated that ADA accessibility must also apply to the Internet. With that declaration, the Justice Department was tasked with setting rules for ADA accessibility for the Internet and websites. Since that time, the Justice Department has formulated recommended rules for ADA website accessibility. Those rules will soon be refined and officially released in the near future. Until then, there is a set of guidelines currently in place (http://www.w3.org/WAI/WCAG20/quickref) for websites to become ADA accessible. Even with these guidelines in place, many hospitality businesses have not yet complied with the guidelines. Now is the time to begin the process of making your current website ADA accessible or to consider a new website design that is ADA accessible.
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.
In a society in which business is increasingly conducted online, excluding businesses that sell services through the Internet from the ADA would ‘run afoul of the purposes of the ADA’” in that it would prevent “‘individuals with disabilities [from] fully enjoy[ing] the goods, services, privileges, and advantages, available indiscriminately to other members of the general public.
When the law was enacted in 1990, it did not specifically address website accessibility for the disabled, but this has become a much-discussed topic in recent years. In 2006, Target settled a class action lawsuit alleging Target.com was inaccessible to the blind, in violation of the ADA, and in 2015 both Reebok and the NBA were hit with a class action lawsuit that alleged their websites did not accomodate the blind and visually impaired.
The WCAG guidelines were updated from version 2.0 to 2.1 in June 2018. The updates in 2.1 cover changes in technology that have occurred since the previous version, and also address areas that were underrepresented in 2.0. What does this mean for you? Not a lot right now. The compliance level targeted is still WCAG 2.0 Level AA, and the 2.1 success criteria are in addition to those already existing in 2.0.
It isn’t a problem by default, a lot of it comes down to how it is built. I’d suggest either considering a highly accessible contingency option, or build those components in such a way that there is a level of accessibility baked into it. If you need help with that testing or review email us at questions at yokoco.com and we’ll be able to let you know the cost for us to lend a hand.