Accessibility Deep Dive

Context

I am the oldest of two in my family. It’s really just me and my sister. Besides my wife my sister is probably one of the people I am closest too. When we got older we were pretty much inseparable. We played music together, we got really close.

One thing I forgot to mention was the fact that she was born with this really interesting disease called biliary artresia. Basically your liver has these bile-ducts that help with blood filtration and other things and when she was born those were absent.

Long story short she had multiple surgeries to help with her situation. Growing up I knew my sister was sick but I didn’t really have any context behind any of it. It wasn’t until I got older and I did research about my sister condition was when I really cared.

I started looking at life differently. Everything from the food I made, to the way I drove I really wanted to make the time my sister spent on this planet comfortable.

I feel that for a lot of us we hear/see the word accessibility and we feel a bunch of different emotions. Like 'This is a good thing!'. For some of us it might be 'I want to help but I don't really understand...'.. And for most of us we struggle with the later.

I think that in order for us to really understand how to build a rich web experience I think we need to know how the web looks like and feels like for some of our friend with accessibility needs.

Goals

  • build empathy for people with accessibility needs
  • identify the 4 main accessibility issues
  • build familiarity with accessibility tools

The Need

There are 3 billion (and counting) people using the internet.

In America alone there are 57 million Americans with a disability (2012)

consider the following statistics from the Census Bureau’s survey taken on July 25, 2012

  • 19.9 Million (8.2%) have difficulty lifting or grasping. This could, for example impact their use of a mouse or keyboard.
  • 15.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.

According to the Pew Internet Project Survey conducted by Princeton Survey Research Associates International 54% of adults living with a disability go online.

So it’s about time we start creating web applications that will accommodate for these people. As people who are soon going to be moving into the development field You have the ability to be the change needed in our community.

The internet is a free service that should be accessible to everyone regardless of skin color, socio economic background, and on top of that physical ability.

We all have become developers for the greater good of those around us. We entered this field because we will have the skill set to solve problems most people can’t even begin to understand. I think one of the easiest and best places to start is going to be making sure we can make the internet accessible to our fellow brother and sister.

I believe that we need to not view these people like they were an edge case but instead we begin to advocate for their experience. If the internet was meant for everyone then we should make it for everyone.

Tim Berners-Lee the creator of HTTP/HTML tweeted in front of 90million people during the London Olympics ‘this is for everyone’

The computer will always do exactly what you tell it to. Maybe its time we start telling them to do the right thing.

Identifying the 4 main accessibility issues.

So here are the top 4 accessibility things to look out for on the web.

  • Visual
  • Hearing
  • Mobility
  • Cognition

Now making sure we help accommodate these users allows us to really gear and tune our UI for everyone.

if you’re interested on how some people with mainly visual needs interact with the web check out this video.

What we’re going to do is break you off into groups of 4-5 and you are going to go to different stations. Each station is going to define the Accessibility issue.

With each issue it will walk you through what the issue is at hand. In some case it will walk you through and experiment to give you context as to what it feels like to use the web with a specific accessibility tool. And then it will also go through some code and or code explination.

Visual

Section 1

We will be talking about color blindness and screen readers in the section.

If you’re wondering what color blindness is here is a definition I found online.

Color blindness, also known as color vision deficiency, is the decreased ability to see color or differences in color. The most common cause of color blindness is due to a fault in the development of one or more of the three sets of color sensing cones in the eye.

Experiments

Tools you will need:

  • chrome vox, a screen reader
  • I want to see like the colour blind, a chrome extension that emulates color blindness

Experiment #1

Once you’ve downloaded the chrome vox screen reader. Imagine that you’re blind and you want to read this article on CNN. Look at the article first and read it.

Once you’ve done that try going through the article with your eyes closed using the chrome vox extension installed. Once you’re done with that answer the following response questions

Navigation Tip: hold command + control and then press the down-arrow key to navigate up and down the page.

Experiment # 2 (optional)

Utilize the color blind extension and visit your favorite websites like Facebook or Instagram and experience how the color change effects your user experience.

Code tip!

One big thing that can effect users is that sometimes forms utilize radio buttons. The issue with the visually impaired is that many times those radio buttons are difficult to click. What we can do to help improve the experience for our friends is to allow the parent object to be clickable too. Often times it’s just a matter of wrapping your radio button in a label tag. check out the following Codepen don’t mind the JS look at the css and the html

These are some easy changes we can implement for application to be more accommodating.

Section 2: Discussion

1) What was the biggest difference between both experiences 2) What was the most frustrating thing for you? 3) Could you get the screen reader to read the whole article for you?

Mobility

Mobility is an issue where the user typically has difficulty using a mouse or a trackpad. The first and easiest thing we can do as developers is making sure we are making our application completely usable with just a keyboard.

Section 1

Video

Watch this video from Dinosaur.js here go up to the 10 minute mark

Experiment

Got to enterprise car website and tab around.

1) what was your experience like tabbing around?
2) How was the focus?
3) Did you tab into the drop down field?

Code Tip

Never adjust the focus on your application. Without the focus there is literally no way for a user to know where they are in your application. Now if your design team doesn’t like the blue line on your focus you can always adjust the focus to be whatever your hover is.

.some-input-field:focus{
  background-color: yellow;
}

Code tip

One thing you want to consider is utilizing the tabindex attribute. What’s great about this is if you set the tabindex of something to zero it acts like a stop sign that makes the screen reader and or tab focus move to a specific part of the page.

consider the following article (make sure to inspect the html)

If you’re tired of reading watch this video instead.

Discussion

1) Do you see a benefit to using tabindex?

2) What did you notice about the auto-trader website while only using tab interaction?

3) Run the axe-core extension on this webpage. What are some of the errors you found on this web app?

Cognition

Cognitive issues is defined by webaim as this:

The concept of cognitive disabilities is extremely broad, and not always well-defined. In loose terms, a person with a cognitive disability has greater difficulty with one or more types of mental tasks than the average person. There are too many types of cognitive disabilities to list here, but we will cover some of the major categories. Most cognitive disabilities have some sort of basis in the biology or physiology of the individual. The connection between a person’s biology and mental processes is most obvious in the case of traumatic brain injury and genetic disorders, but even the more subtle cognitive disabilities often have a basis in the structure or chemistry of the brain.

A person with profound cognitive disabilities will need assistance with nearly every aspect of daily living. Someone with a minor learning disability may be able to function adequately despite the disability, perhaps even to the extent that the disability is never discovered or diagnosed. Admittedly, the wide variance among the mental capabilities of those with cognitive disabilities complicates matters somewhat. In fact, one may reasonably argue that a great deal of web content cannot be made accessible to individuals with profound cognitive disabilities, no matter how hard the developer tries. Some content will always be too complex for certain audiences. This is unavoidable. Nevertheless, there are still some things that designers can do to increase the accessibility of web content to people with less severe cognitive disabilities.

With that being said this topic is a little more abstract.

Article

Read this article regarding cognition accessibility here.

Experiment

Dyslexia is a reading disorder characterized by trouble reading despite intelligence.

Checkout this document that replicates what it looks like to have dyslexia

Code Tip

A lot of what you are going to do as web developer to help combat this is organizing your data in a way that is decreeable and engaging for the user. Some things we can do to help draw attention to our document:

  • Using proper headings, and lists
  • Using more white space in your design
  • “Chunking” content into more manageable pieces
  • Making forms manageable by breaking them into multiple, sequential steps
  • Providing a logical reading order
  • Being consistent with fonts, colors, and locations of page elements
  • Offering keyboard access
  • Consider offering content in multiple formats

Discussion

1) What steps can we take to consider people with cognative issues?

2) Can you think of any website you know that would be difficult to use for someone with cognitive issues?

Wrap up

Now that we are more aware of what is going on in the world of Accessibility what are we going to do to make sure we are committing ourselves to making the web a better place for everyone?

I do really well with small attainable goals. In the last couple minutes of our time together set up a github gist and write down 3 actionable commitments you can do in your next coming projects to accommodate for accessibility issues?

When you have done that please submit them to @yungjhun via DM.