Why You Should Give a S*** About Accessibility
Tags: a11y, javascript, frontend
Published: 2018-01-31 18:51:52

---
title: Why You Should Give a S*** About Accessibility
published: true
description: Why You Should Care About Accessibility
tags: accessibility, a11y, javascript, front-end
---

## 57,000,000 Americans have a disability.

According to a 2012 Census report, 56.7 million Americans have some form of disability. As developers and designers, it is our responsibility to create websites and applications that cater to everyone. It is also our social responsibility to make the web accessible to more than just 80% of the population and to educate the public (especially other engineers and designers) about these issues.

> Consider impairments that impact accessibility of online websites, applications, and documents. This survey estimates the number of people with specific impairments as follows:
> 19.9 million (8.2%) have difficulty lifting or grasping. This could, for example impact their use of a mouse or keyboard.
> 5.2 million (6.3%) have a cognitive, mental, or emotional impairment.
> 8.1 million (3.3%) have a vision impairment. These people might rely on a screen magnifier or a screen reader, or might have a form of color blindness.
> 7.6 million (3.1%) have a hearing impairment. They might rely on transcripts and / or captions for audio and video media [(source)](https://www.disabled-world.com/disability/accessibility/websitedesign/).

## How Accessibility Impacts Business

Ignoring accessibility can create a loss in potential profit each year. Imagine something as small as text color choice alienating half of your potential customers. Even age-related conditions such as presbyopia (loss of the eyes’ ability to focus) hinders the capability to read small text or see colors with low-contrast.

Top companies such as [Target](https://www.w3.org/WAI/bcase/target-case-study), [JetBlue](http://dignifiedflyingfordisabled.blogspot.com/2012/04/jetblue-airways-fined-for-inaccessible.html), and [Scribd](http://www.forbes.com/sites/ericgoldman/2015/03/26/scribd-must-comply-with-the-americans-with-disabilities-act/) have been fined/sued over inaccessibility.

>“The case, brought by the California Council of the Blind and three blind JetBlue customers, is about access barriers on JetBlue’s website and the inaccessibility of JetBlue’s airport check-in kiosks to people with visual impairments. JetBlue has designed its website in a way that prevents blind customers from independently and privately accessing information and using the site’s features. JetBlue’s airport kiosks cannot be used by blind customers because the machines do not have audio output or an accessible means to input information.” (source)

### The NFL Color Rush

Another example of accessibility negligence is the 2015 NFL Color Rush campaign. To celebrate the league’s 50th anniversary of the first-ever TV game shown in color, the Bills were wearing all-red and the Jets were wearing all-green. Ironically, the NFL failed to account for the [8% of men who are red/green color-blind](http://www.forbes.com/sites/ericgoldman/2015/03/26/scribd-must-comply-with-the-americans-with-disabilities-act/).

![NFL color rush image](https://cdn-images-1.medium.com/max/1600/1*c5tt25Dr6_XJvFgvnDAy6g.png "What red/green color-blind fans saw on their TV.")

Afterward, the NFL released a [statement](http://www.cbssports.com/nfl/news/nfl-we-didnt-account-for-color-blindness-with-color-rush-jerseys/) claiming they “did test the jerseys this summer on field and on television. The standard television test did not account for color blindness for fans at home, that became apparent.”

Hopefully, this instance highlights the importance of color choice and awareness of inclusive design.

## What We Can Do About It
Use the Web Content Accessibility Guidelines Checklist (WCAG)
Use this for accessibility compliance — WCAG 2.0 is the current inclusive web standard. WCAG applies to all web content, including single page and dynamic web applications, multimedia, and mobile websites.

### Use those tools!

There are a variety of websites and browser plugins to help you check for accessibility.

My favorites are:
* Chrome Developer Accessibility Tools
* WAVE (Web Accessibility Evaluation Tool)
* ChromeVox Screen Reader
* SEE Chrome Plugin

## 10 General Design & Development Considerations
* Use headings (h1, h2) properly
* Use ARIA landmarks (marking sections of a web page)
* Add labels to form fields
* Keep color contrast in mind
* Use live text, not pictures of text (this also helps with SEO!)
* Provide video descriptions and use closed captioning
* Choose dropdown menu that works for all users (someone may be unable to trigger or access a submenu)
* Test websites without a keyboard (many people don’t have a mouse)
* Test sites with assistive technologies on mobile and desktop
* Add proper alt-text to images [(great article about alt-text)](http://webaim.org/techniques/alttext/)

***Accessibility is the new standard of web development and we must not fall behind.***