Why getting more people with disabilities developing technology is good for everyone

Accessible technology is better for everyone, and accessible technology benefits when the people who rely on it most help build it.

Parapan Athlete Tiana Knight demonstrates Blindsquare, an iPhone app that helps blind people by voicing out what’s around them. Chris So, Toronto Star via Getty Images

By Kristen Shinohara, Garreth Tigwell, The Conversation June 3, 2021

Unless you’re blind or know someone who is, you might not know that blind people use the same smartphones as sighted people. In fact, many blind people use touch-screen smartphones every day. The secret is that smartphones have a screen reader, a tool that allows blind people to use a mix of gestures and taps, along with vibrations or audio feedback, to use their apps.

Screen readers work on desktop computers as well as mobile devices. You can usually find the screen reader in settings under accessibility. On iPhones the screen reader is VoiceOver. It provides a verbal description of what’s on the screen, including buttons to click and other actions available to the user. A well-designed website or app user interface makes the information on the website or app accessible to the screen reader, which makes it accessible to blind users. However, a badly designed website or application will be rendered invisible to a screen reader.

We are researchers who focus on technology design that is usable for people with all kinds of disabilities. We’ve found that more needs to be done to make technology accessible and inclusive, such as improving design tools so they are accessible to screen reader users.

A man checks Facebook on an iPhone using the screen reader VoiceOver. Hyoung Chang, The Denver Post via Getty Images

It’s not just a matter of fairness and inclusion. Accessible technology is generally better for everyone. An app or website that causes problems for a screen reader is likely to be more difficult than an accessible app or website for anyone to use because it will take more time or effort.

Observing people is good; their participation is better

At first, user interface designers found that the best way to create accessible technology was to study how people with different disabilities used touch screens. For example, early researchers reported that blind users sometimes found locating small icons and specific numbers on the on-screen keypad difficult and time-consuming.

To solve this, accessibility researchers used the whole touch screen as an input and navigation control, similar to a game console controller. Instead of having to touch a particular part of the screen, users can tap anywhere in response to audio prompts. These insights would have been impossible to come by without including blind people in the evaluation and design of touch screens.

User interface design best practices have long included users in the design process. Including users with disabilities results in more accessible technology. Yet many technologies are still not accessible out of the box to users with disabilities.

One way to make apps and websites more accessible is to have people with disabilities designing the technologies. But the design process itself is not very accessible to those very people. Few tools in the user interface designer toolbox are themselves accessible. It’s a Catch-22.

Accessible tech requires accessible design tools

Little research has been conducted about how accessible the user interface design process is, including for blind people. Our recent research evaluated the accessibility of prototyping software, which allows user interface designers to create temporary mock-ups of user interface designs to show clients or to test with users. This software is instrumental to the field. Examples include Balsamiq, Adobe XD and UXPin.

Low- to high-fidelity mock-ups of user interfaces allow designers to play around with layouts before committing to a final design.

We found that most popular prototyping software is not compatible with screen readers. Therefore, the prototyping software is not accessible to blind designers who use screen readers.

We tested two common screen readers, VoiceOver on MacOS and Narrator on Windows, with popular prototyping software and documented when and where they provided access to the different buttons and features in the prototyping software.

Although we found some compatibility, such as screen readers identifying a button and indicating that the button could be selected, other aspects were less clear for screen reader users. For example, the prototyping software might not present information that the screen reader could pass on to the user to indicate what a given button does, like change the font size of text. Or it might not clearly allow the screen reader to focus on the button to select it, which is necessary for the user to be able to “click” the button.

A screen shot of a prototyping tool’s four major components: the canvas workspace, navigating layers of content, the individual elements that make up the design and the element parameters. VoiceOver is enabled and its visual caption panel floats on top of the canvas workspace, indicating that a button is selected.

Ultimately, the limited access uncovered in our research is severe enough to conclude that a blind designer would not be able to use the software to create mock-ups of their own.

A better future is accessible

Accessibility is an issue that touches everyone. Providing access to technology is legally required in most cases. In the past, organizations that failed to provide adequate access have faced lawsuits.

But accessibility is also a hallmark of good technology. Many technologies that people take for granted today came about when innovators designed for users with disabilities, including optical character recognition, which allows computers to read printed text.

Building accessibility into the design process is crucial. And while it is useful for designers to be aware of how users with disabilities interact with technologies, the most powerful insights may come from those with disabilities themselves. No matter how much empathy designers glean from researching user behavior and preferences, it can’t replace the benefits of having a piece of technology built by people who actually use it.

The Conversation’s science, health and technology editors pick their favorite stories. Weekly on Wednesdays.
Authors
Kristen Shinohara, Assistant Professor of Computing and Information Sciences, Rochester Institute of Technology.
Garreth Tigwell, Assistant Professor of Computing and Information Sciences, Rochester Institute of Technology.
Disclosures
Kristen Shinohara receives funding from The National Science Foundation.
Garreth Tigwell has received funding from EPSRC.

Source The Conversation The Conversation

 

BlindSquare – Painting a picture of the world through sound. Join our young friend Tuomas, as he prepares to leave home and travel by bus, to meet some friends at a downtown mall in Porvoo Finland. His destination and feedback through his journey guided with information from BlindSquare. MIPsoft Oy. Youtube Nov 29, 2016
  References

Freedom to roam: a study of mobile device adoption and accessibility for people with visual and motor disabilities, Shaun K. Kane, Chandrika Jayant, Jacob O. Wobbrock, Richard E. Ladner. Assets ’09: Proceedings of the 11th International ACM SIGACCESS conference on Computers and accessibility, October 2009. Pages 115–122. doi: 10.1145/1639642.1639663.

Slide rule: making mobile touch screens accessible to blind people using multi-touch interaction techniques, Shaun K. Kane, Jeffrey P. Bigham, Jacob O. Wobbrock. Assets ’08: Proceedings of the 10th international ACM SIGACCESS conference on Computers and accessibility. October 2008. Pages 73–80. doi: 10.1145/1414471.1414487.

A toolkit for facilitating accessible design with blind people, Cynthia L. Bennett. ACM SIGACCESS Accessibility and Computing. Issue 120. January 2018. pp 16–19. doi: 10.1145/3178412.3178415.

Accessibility of High-Fidelity Prototyping Tools, Junchen Li, Garreth W. Tigwell, Kristen Shinohara. CHI ’21: Proceedings of the 2021 CHI Conference on Human Factors in Computing Systems. May 2021 Article No.: 493. Pages 1–17. doi: 10.1145/3411764.3445520.

Design-for-User-Empowerment-Richard-E-Ladner-2723869

Design for user empowerment, Richard E. Ladner. ACM Interactions. Volume 22. Issue 2. March + April 2015. pp 24–29. doi: 10.1145/2723869.

Mobility Menu
   403-240-9100
Call 403-240-9100