DevOps

Three Ways to Improve DevOps to Ensure Accessibility

Share this post:

Designing and developing accessible solutions has become critical for organizations – from business processes to product development. With a renewed focus on human-centered design, I am often asked, “How can we effect change in an organization’s DevOps to ensure accessibility is integrated from the outset?”

There are many ways to achieve a positive effect for accessibility, but I will focus on three core strategies that will ensure any web or mobile application is personalized to an individual’s needs, preferences and ability:

  • Make accessibility an integral function of design

The key is to view accessibility as a design challenge and not a constraint. In my experience, I’ve often found that a good user interface design has an innate simplicity that makes it easier to implement accessibility.Empathy map that shows a person (Amy) in the middle of four different grids, depicting what she does, what she thinks, what she feels and what she says.

One method is to integrate accessibility into “personas” that describe specific user needs, tasks they want to accomplish, and their motivations and abilities. Understanding every possible user –people with disabilities, the aging population, or anyone facing a “situational” disability while using a mobile device – helps designers and developers ensure that each feature has a plan for accessibility. Using an “Empathy Map” helps everyone synthesize their observations and draw out unexpected insights.

This also helps DevOps avoid a common problem of running out of time and budget near the end of the development cycle. Too often we hear, “We had to cut something so we cut accessibility. We’ll try get to it next time.”

  • Conduct automated testing early in development

It has become essential to test early in the development process to find and correct accessibility conformance issues. This offers the potential to save valuable time and budget, especially because it can be used as a way to teach your development team how to implement accessibility correctly so they don’t propagate issues throughout their development efforts.

It is well known that bugs are much easier and less expensive to fix when they are caught early. By running automated testing throughout development, teams can identify and remediate accessibility concerns prior to releasing the code to the test team.

Automated testing tools give developers a complete view of accessibility issues, such as alternative text and color contrast, and then recommend the necessary corrections to adhere to accessibility standards and government regulations (WCAG, US Section 508, Americans with Disabilities Act), while increasing usability and customer experience. A bonus result of incorporating automated testing in the development process is that the team may finish testing early and bring the product to market faster.

  • Gather stakeholder feedback

Gathering feedback, especially from persons with disabilities, ensures the solution delivers an optimal user experience.

Often developers who are not familiar with assistive technology, such as screen readers, work hard to guess at the best enablement, but real stakeholders with real disabilities provide critical and valuable feedback.Feedback circle with arrows connecting.

When gathering stakeholder feedback, co-location does not need to be a constraint. I have participated in many feature reviews where we pull together a virtual team of developers, accessibility experts and a person with a disability.

We use screen-sharing technology so a person can walk through the interface using assistive technology. We can hear how, for example, the screen reader interacts with the user interface and discuss the user experience and expectations. If the person using the assistive technology is struggling, the virtual team can guide them through the inaccessible aspects of the user interface.

Changing the Culture of Development

Applying even one of these strategies will have a positive impact on your organization’s ability to create accessible solutions. Employing all three in your organization’s DevOps will effect immediate change in creating more inclusive and usable solutions…for everyone.

Add Comment
No Comments

Leave a Reply

Your email address will not be published.Required fields are marked *

More Inclusive Design Stories
By Tom Babinszki on July 18, 2017

When Should You Think About Accessibility?

Editor’s Note: Tom Babinzski, an Accessibility Advisor with IBM Accessibility Research, is starting a new blog series where he will share tips and tricks for accessible design and development. If you have topics you’d like Tom to address, please leave your thoughts in the comments section. I spend a majority of my time traveling to […]

Continue reading

By Tim Powers on March 8, 2017

Automating Accessibility Testing of Web Applications

IBM has released a new solution that is designed to allow developers and testers to integrate automated accessibility testing within Chrome browser development tools to help deliver an optimized user experience and conform to industry standards. IBM AbilityLab™ Dynamic Assessment Plugin, a browser extension that quickly identifies accessibility issues, and evaluates and recommends potential fixes, including those […]

Continue reading

By Erich Manser on February 21, 2017

Students and Seniors Share Ideas for Creating an Accessible, Self-Driving Vehicle

Continuing our work to create the world’s most accessible, self-driving vehicle, IBM, Local Motors and the CTA Foundation recently held two #AccessibleOlli workshops in the Washington D.C. area. We invited two distinct audiences – students from Carver Vocational-Technical High, a P-TECH school in Baltimore, and an AARP workshop with older adults – to help design a vehicle […]

Continue reading