Using a Screen Reader to surf the web.

Yesterday I wrote about what it's like to consume entertainment as a blind person. It's only fair that I would spend some time looking at surfing the web; it's the way I'm communicating with you right now and it is my main source of entertainment. 

As we get started, take a few minutes to read Accessibility, in Entertainment, for the Blind. Time yourself as you read it. 

 Accessibility, in entertainment, for the blind

Accessibility, in entertainment, for the blind

I just timed myself and it took me 2:53 to read the entire page. If I'd watched the three videos, the total time reviewing the page would be 8:10.

I reviewed the article with a screen reader to see what it is like to review that content as a blind person. I encourage you to listen to the whole thing to have the full experience. 

Did you listen to the whole thing? It's 16:50 long! And that is without watching a single video. 

I've only used a screen reader a handful of times so let's chop off one minute for some of my clumsiness with the tool in the beginning of the recording. Let's also imagine the person using the screen reader is a regular consumer of content on this website and knock off five additional minutes (skipping the time it takes to go through all of the header, links to other stories and footer content). Let's also imagine the person using the screen reader is used to it, so let's have the screen reader reading the content at double time taking the 10:50 down to about 5:25 seconds. But, in these scenarios I haven't watched any of the videos. I'd have to add 5:17 seconds to include all three videos.

With a screen reader and watching the videos my total viewing time would be 10:42. So that's 8:10 reading the content versus 10:42 consuming the content with a screen reader. It takes two and a half minutes longer for someone to consume the content with a screen reader.

Perhaps time seems like an arbitrary thing to focus on, but when we think about how time pressed we all are, every day, adding a few extra minutes to every online tasks would start to add up. 

I've worked in digital communications for 17+ years. I've also worked with teams to implement sites that were highly accessible (university and government sites). I could usually tell the deftness of a developer by whether or not they cared about accessibility standards. 

While my site is serviceable for someone who is using a screen reader, the experience is not ideal.

I am not a developer. I use Squarespace for my website. Squarespace is a Software As A Service (SaaS)-based content management system (CMS), website builder and blogging platform. It seems that Squarespace is one of the better SaaS CMS systems on the market, however, there are some things I noticed when using the screen reader that bother me.

  1. Lack of Image Descriptions. Every article has an image in the header. Instead of using the name of the image, Squarespace has programed the site so the screen reader picks up on the title of the article and indicates that there is an image. There is no field for me to describe the visuals portrayed in the header image or any other image used on the page. Squarespace allows screen readers to parse the caption field, but there is no way for me to enter meta information to describe the image. I can do a better job of describing the images on the front end. This will be redundant for sighted visitors, but helpful for non-sighted visitors. Ideally the experience would work for both sighted and non-sighted visitors
  2. No skip to content short-cuts. There are no "skip to content" shortcuts programmed into the template. There may be keyboard shortcuts that work. I just don't know how the keystrokes to test this. 
  3. Pronunciation matters. The screen reader did a pretty good job of reading and understanding all of the content correctly. The screen reader correctly read Transfatty Lives but it had a hard time with Roobrik and Smartstones (read as smarts-tones instead of smart-stones) and I found Braigo hard to understand. It'd be great if we could enter meta information so the pronunciation could be dictated on words that are unexpected. 
 

I can speculate about the implications all day long, but I encourage you to take a few minutes to hear what it's like to use the internet if you have a visual disability (from someone who is blind).

Web Accessibility in Mind (WebAIM) has a few articles you should read if you are a developer who wants to make your website accessible to those with screen readers (or really anything else). 

My site has lots of room for improvement. My apologies to any visually impaired users of this website. 

P.S. I found this great video by Tommy Edison, a blind gentleman that has a series about what it's like to do things as a blind person. In this instance, Tommy shows what it's like to use a computer to compose an email.