The Americans with Disabilities Act (ADA) prohibits discrimination against individuals with disabilities. A disability in this context is a physical or mental impairment that limits one or more major life activities.
Title III of the ADA prohibits discrimination on the basis of disabillity in “places of public accommodation.” When the ADA was signed in 1990, the focus of Title III was the standards required for business’s physical locations in order to accommodate individuals with disabilities. The internet was not a large part of peoples’ lives at that point; accessibility of websites wasn’t even considered. However, as the internet has become more and more widespread, Title III is being interpreted to include websites as places of public accommodation.
ADA compliance for a website is tricky. You can’t just add a plugin that automatically makes your website ADA compliant – and there are disagreements in what even qualifies as full ADA compliance for a website.
The Department of Justice generally uses the Web Content Accessibility Guidelines (WCAG) as a guide to gauge whether a website is accessible. Websites should meet the guidelines for all Level A and AA requirements to be considered accessible.
However, even when following the WCAG, it may be difficult to discern if you’re actually meeting specific criteria or not – whether it’s because of the wording in the document or the ever-changing trends in website design and browser capabilities.
If your website is found to be inaccessible to individuals with disabilities, you’re not in compliance with the law, which means you could face lawsuits.
There are other factors to consider as well. Many Americans have a disability of some sort that affects how they experience your website. This could be a visual impairment like colorblindness, or a hand injury that prevents the use of a mouse. They may have a neurological condition that makes reading a quickly rotating hero difficult or they may have an intellectual disability and need clear instructions in order to understand how to fill in the input fields on your website’s forms.
This segment of your users may be larger than you think, and if your website is not accessible to them, they will struggle to access or understand the information they need on your site—and may even turn to competitors with more accessible websites.
The overall goal of creating an accessible website is preventing barriers – to content and information, and limiting confusion and frustration. By striving to create an ADA-compliant and accessible website, you’re ultimately benefiting all users by ensuring your site is easy to understand and easy to navigate.
It can be easy to dismiss any A/B test code as simply temporary, and therefore doesn’t need to be ADA compliant. After all, it’s only running on your site for a short period of time.
However, consider the user who gets segmented into an inaccessible test variation.
Regardless of how temporary your test may be, it is live code running on your site that users will be coming in contact with—and it should be functional for all users.
Ideally, your team will follow all WCAG guidelines with every A/B test you build. However, in creating A/B tests there are accessibility issues that tend to crop up more than others. Here is our advice for designers and developers when building A/B tests.
Keeping your website tests ADA compliant can feel overwhelming, especially if accessibility isn’t something your team has considered much in the past. However, the benefits—both to your company’s reputation and abidance of the law—and to your users, in having an easy to navigate the website, regardless of what test experiences they may find themselves in—make ADA compliance worth the time and effort.
At Blazer, we partner with ambitious brands and leaders that refuse to settle for less.
Blazer is the consulting firm that helps brands prove what drives customer value, and builds teams that deliver on it.
16 W. Martin St., 9th Floor, Raleigh, NC 27601
16 W. Martin St., 9th Floor, Raleigh, NC 27601