And what you can do about it
As designers and developers, we work hard to understand the context of the problem we’re solving and who we’re solving it for. But does that lens include those with disabilities? Consider the 4.9 percent of U.S. adults that have a vision disability and the one in 12 males that have some form of colorblindness. Are they able to experience our application as we intend? While color contrast is a good place to start, designers and developers can do more to make an application accessible.
According to the Centers for Disease Control and Prevention (CDC), one in four adults living in the United States have some form of disability, and according to the World Health Organization (WHO), 1.3 billion people worldwide have a significant disability. Difficulties with cognition, motor, vision, and/or hearing functions can create challenges in accessing and processing information, particularly within software applications.
Consider the People
Before writing the code, think about your application’s intended audience while prioritizing accessibility from the start. Maybe you’re already thinking about your personas, their jobs to be done, their needs and frustrations, and how your product will make their lives easier. Great start. Then ask, “but can my application be used by anyone?”
The ability to use an application regardless of age, culture, economic situation, education, gender geographic location, language, and race speaks to a greater movement of accessibility — that of inclusivity, e.g. creating experiences that anyone can use.
Consider the Context
Melissa* is a portfolio manager with Multiple Sclerosis (MS). She often gets tingling or numbness in her hands which makes using a mouse painful and difficult.
Inclusive and accessible experiences are designed for flexibility and adaptability. Someone like Melissa needs keyboard functionality enabled that allows her to work without reliance on a mouse. Similarly, a user could have a temporary need for a mouse alternative due to an injury or recovery period where they can’t use their dominant hand to do everyday tasks.
Consider the Device
Brendan* is a hybrid worker who commutes to the office by train three days a week. At the office, he uses his desktop exclusively, but on the train, he works from his phone. Brendan is colorblind and has difficulty seeing different shades of red, green and yellow. For Brendan to work most effectively, he needs his application to work seamlessly on his desktop and his smartphone, designed so he can perceive positive (green) and negative (red) results easily.
A mobile device used in bright sunlight compromises the color contrast and makes it more difficult to see. Giving users the option to view in light or dark mode makes the experience more inclusive. Mobile screen sizes vary widely so information on the page should be kept to a minimum, tap regions should be generous, with font scaling available. Choose gestures like tap, swipe, and pinch, over more complex interactions. Also, minimize data entry.
Consider the Implications
The amount of web accessibility lawsuits brought to federal court citing the Americans with Disabilities Act (ADA) Standards for Accessible Design reached a new record in 2022, up 12% from 2021. Around the globe, there is a demand for equality and an increase in legislation confirming that accessibility is a human right. Even if your organization does not require compliance, solving for accessibility and including the basic tenets of accessibility make for good usability and a more inclusive and user-friendly experience for anyone using your product.
Strive for:
- Easy to understand content
- User-friendly design
- Experience equity
- Versatility
Now Consider the Tech
Ready to start making your application more inclusive and accessible? Think about additions and adjustments in the code that allow for keyboard access, screen readers, color choices, and more.
Check out these tools and resources to get you started:
- ACT Rules Implementation in Test Tools and Methodologies | WAI | W3C
- Selecting Web Accessibility Evaluation Tools | Web Accessibility Initiative (WAI) | W3C
- ARIA Authoring Practices Guide
In Conclusion
Inclusive, accessible design starts with thinking comprehensively about the product experience from the beginning, and considering multiple scenarios for flexibility, adaptability and equity. It provides equal access to information, products and services, and reduces barriers to and within employment.
As a developer, what can you do today to make your application more accessible?
*Example users referenced are based on personas and not representative of a particular individual.
Sources
https://www.cdc.gov/ncbddd/disabilityandhealth/infographic-disability-impacts-all.html
https://www.oberlo.com/blog/mobile-usage-statistics
https://enchroma.com/blogs/beyond-color/interesting-facts-about-color-blindness
https://www.oberlo.com/blog/mobile-usage-statistics
Authors: Juli Duffer (Senior Director, UX Design), Gregory Haislip (Director, UX Specialty), Anirudh Ojha (Principal UX Lead), Justin Haislip (Director, UX), Augusto Cruzalegui (Director, UX), Jim Barraud (Director, UX), Bill Decker (Principal UX Lead), Frank Marchese (Director, Visual Design) and Paul Grenier (Lead Software Engineer)
Editors: Gregory Levinsky (Marketing Content Specialist) & Josh Gaddy (VP, Director, Developer Advocacy)
