Our team often says that “accessible design is just good design.” Indeed, if you look at the bigger picture, the goal of creating products is to help people create things, find things, watch things—in short, to accomplish things. Why would any product team want to make it more challenging for a user to accomplish their goals? That’s why we encourage teams to use the accessibility design guidelines to influence early design choices. Like most things worth doing, designing with accessibility in mind takes practice and work. But it’s key to designing a robust user experience for all.

Develop and iterate

Throughout the design and development of a product, there are many opportunities to get additional input from diverse users. Any type of evaluative research, like usability studies, can be made more inclusive by testing with people with and without disabilities. At this stage, teams can gain more specific insights on the actual experience for the user. For example, an application could present a notification for a longer period so that it doesn’t disappear too quickly for someone with a learning disability or someone who was simply too distracted to read it. While design guidelines can help a product with fundamental accessibility, nothing substitutes for actually watching a person using a screen reader, switch access device, or other assistive technology to truly understand the quality of the user experience.

After a product launches

Once a product launches, teams can use feedback surveys, app ratings, customer support calls and emails to get a wealth of qualitative input. And filtering this feedback by users with accessibility needs can continue to paint the picture of their full experience.

This is also the perfect time to stop and understand what benefits were gained from designing inclusively from the beginning, and to apply lessons learned to the next product development cycle. Over time, it can become second nature to design inclusively.

Products are a product of user feedback

Returning to our researchers in Jakarta: After they came back from their trip, they worked to bring awareness to their findings by sharing insights and solutions with other teams at Google, including the Next Billion Users group to help them think about accessibility for people in emerging markets. Rachmad’s comments about how it can be difficult finding help for assistive tools informed the creation of a new Google support team dedicated to helping people with disabilities who have questions on assistive technology or accessibility within Google’s products. On a product level, the Jakarta team provided valuable input for the group behind Lookout, an app coming soon to the U.S. that helps people who are blind and visually impaired learn about their surroundings. Once available, people like Rachmad will hear cues from their Android phones, helping them gain more independence.

Focusing on accessibility from the beginning can influence product direction as well as develop robust insights that teams can learn from and build upon in future work—all in an effort to effectively build for everyone.  If you’re interested in helping shape the future of accessibility at Google, sign up to participate in future user studies.



Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here