Neil asked:
Let's break it down. What are disabilities? With over 15% of the world's population experiencing some form of disability, it's safe to say everyone knows someone with one. They just might not be aware of it, since not all disabilities are visible. Usually when developers think of disabilities, they think of the most extreme cases people who are completely blind, completely deaf, or in a wheel chair. And while extreme cases certainly exist, they aren't a big percentage of the 15%. You're asking the wrong questions With all the different types of disabilities, there's no way for you to somehow "experience" them yourself so you can directly relate and empathise. I've seen (and tried) to do the most extreme experiments. I've tied a piece of cloth around my eyes and tried using websites with a screen reader. I've done no mouse days, where I refrained from using the mouse and only relying on my keyboard. Trust me, you'll end up frustrated and angry, and not necessarily because of the inaccessible websites. But because it's something new and way out of your comfort zone. The few minutes you will last with a blindfold on will not give you any sort of understanding of what a blind person goes through every day. I've never learned how to swim (and can't to this day). But if I tried to learn, I certainly wouldn't get together with other people who can't swim and say "alright, let's figure this out!" I'd go to someone who has the technique down. Ask better questions And you'll get better answers.
The best way to get answers to these questions is to speak with people with disabilities and learn from them how they tackle these challenges every day. Invite people with disabilities to talk to your team. Involve users with disabilities in your UX testing process to see how they use your own product. Now you're learning to swim with the fish. The key is, you shouldn't try to understand disabilities, but to relate to people. People care about people, not about abstract concepts or memorising a list of conditions. The last thing I will say is that no one expects you to know everything about every disability. But having the courage to ask, be curious, accepting, respectful and to take this seriously is non-negotiable. |
Join fellow like-minded product owners looking to learn and contribute to authentic conversations on accessibility and inclusive design packed into just 5 minutes a day.
Does this sound familiar? The meeting was scheduled for 9:00 but somehow at 9:06 Zoom still says "Waiting for host to start the meeting." When it finally starts, the organiser casually mutters "sorry, previous thing ran long" while fumbling with screen sharing. It's okay though, because they'll happily steal those minutes back by running fifteen minutes over the scheduled end time. Everyone waiting lost those first minutes. And everyone with a follow-up commitment will nervously look at the...
It's very tempting to hand over responsibility over accessibility to other people. If you're a developer, it's the designer's job. If you're the designer, the developer needs to implement accessibility. If you're the product owner, it's the tester's job to make sure everything works with assistive technology. This is easy. Because if someone else accepts responsibility, then we're off the hook. I see two problems with this: 1. Someone else must always be willing to accept the responsibility...
Accessibility. 13 letters. We thought it was such a lenghty word that we use the numeronym a11y to write it out. It has all these definitions floating around, each one just slightly different than the next. I think the reason why we can't settle on just one is simply because, like the word itself, accessibility is a loaded concept. It's just like a bulky piece of luggage you lug around and when you finally set it down on the floor and start to unpack, it'll likely fill the room. The...