Most people think of wheelchair ramps or handicapped parking spaces when they think of the Americans With Disabilities Act. But new laws are broadening the scope of accessibility to include websites. Your website could look good and be functional with lots of great information. But if a disabled person can’t use it you could receive a letter from lawyers threatening to sue under the ADA.

Federal ADA laws already require that websites related to federal, state, or local governments or those that receive federal funding must be digitally compliant for people with disabilities. The Americans With Disabilities act requires business and stores that are “places of public accommodation” to be physically accessible for people with disabilities through such modifications as wheelchair ramps or handicapped parking spaces. At issue is the definition of a website as “a place of public accommodation.”

The law can interpret private businesses as “places of public accommodation” simply by virtue of the fact that they are accessible to anyone with an internet connection. Courts have interpreted this language to mean that the ADA law applies to all commercial websites. Some courts have interpreted this language to mean that a website must be accessible if it has a connection to a physical location, such as the online arm of a brick-and-mortar retail store.

There’s no consensus on what the law actually means right now. But every indication is that they are going to interpret the ADA to apply to commercial websites. This has online business owners worried. The example of the website Scribd and its “NetFlix for books” program wasn’t accessible to screen readers, which meant that the service was inaccessible to blind readers, is a warning sign for business owners.

Scribd’s argument was that Scribd isn’t a physical place and it’s therefore not regulated by the ADA. the judge refused Scribd’s attempt to have the lawsuit dismissed, and they ended up settling. Scribd was required to modify its titles (Section 4) to be accessible by screen readers. They were also required to modify and maintain its website as accessible (section 5).

We’re urging business owners to take steps to make their website accessible. We’re urging people to take steps no matter what type of business they have, but especially one that is accessible to anyone over the internet, as most ecommerce and service-based websites are. This isn’t about a fear of a lawsuit, although that is what’s on people’s minds. It’s about ensuring that your site meets the legal requirements of accessibility.

A plugin like ADA Plugin is a business’s first step to protecting themselves. A lawsuit that forces you to come into compliance won’t have as much “teeth” if you’re already taking steps to make your website accessible. The ADA Plugin runs on a site’s back-end to detect and warn your of compliance issues. It takes a look at each element on your site and compares it to WCAG 2.1.

If your site has issues, a warning pops up when the scan is run, so that you can see what the issue is, what guidelines it is referring to, and suggestions on how to fix it. IF you resolve the issue, the scan remembers and won’t show that warning next time. The plugin is a great way to ensure that your site is moving toward compliance and keep it compliant once you get there.

WCAG 2.1 follows the WCAG 2.0 guidelines that have been the standard for website accessibility. The content listed in the Web Content Accessibility Guidelines covers a wide range of things to consider when making web content more accessible.

WCAG 2.1 extends Web Content Accessibility Guidelines 2.0 [WCAG20], which was published as a W3C Recommendation in December 2008. In the intervening years, web accessibility grew greatly as a topic of both need within the digital community and as a federally mandated requirement of websites associated with federal programs.

WCAG 2.1 builds upon the foundation of 2.0 guidelines in the sense that web content that conforms to WCAG 2.1 also conforms to WCAG 2.0. The creators of the guidelines say that “While WCAG 2.0 remains a W3C Recommendation, the W3C advises the use of WCAG 2.1 to maximize future applicability of accessibility efforts. The W3C also encourages use of the most current version of WCAG when developing or updating Web accessibility policies.”

WCAG 2.1 adds new success criteria, definitions to support them, guidelines to organize the additions, and a couple additions to the conformance section. The Accessibility Guidelines Working Group recommends that sites adopt WCAG 2.1 as their new conformance target, even if formal obligations mention WCAG 2.0, to provide improved accessibility and to anticipate future policy changes.
The following Success Criteria are new in WCAG 2.1 (there are three levels of complaince, A, AA and AAA, which are represented in parentheses):

1.3.4 Orientation (AA)
1.3.5 Identify Input Purpose (AA)
1.3.6 Identify Purpose (AAA)
1.4.10 Reflow (AA)
1.4.11 Non-Text Contrast (AA)
1.4.12 Text Spacing (AA)
1.4.13 Content on Hover or Focus (AA)
2.1.4 Character Key Shortcuts (A)
2.2.6 Timeouts (AAA)
2.3.3 Animation from Interactions (AAA)
2.5.1 Pointer Gestures (A)
2.5.2 Pointer Cancellation (A)
2.5.3 Label in Name (A)
2.5.4 Motion Actuation (A)
2.5.5 Target Size (AAA)
2.5.6 Concurrent Input Mechanisms (AAA)
4.1.3 Status Messages (AA)

These guidelines and the technical language that they are written in is confusing for most people. That’s why we recommend that you
hire agencies who are experienced in working with these guidelines. The creators of ADA Plugin have experience with the guidelines since the first version. The ADA Plugin is always updated whenever there are big changes, so you can know that by using it you are doing two key things: Providing an accessible website to the world, and protecting yourself and your business from lawsuits. Get in touch to learn more!