What if design projects started by thinking about accessibility first? I don’t mean the basics like ALT text for graphics, following coding standards, and creating correctly structured information hierarchies. Building in accessibility at the code level is the only way to remove many of the barriers people with disabilities experience. But if our design thinking started with the idea of making a product that focuses on key tasks and is flexible, would that create a better user experience for everyone?
Empathy is what separates us from the rest of the animal kingdom. We have an ability to imagine things the way that others see them and how it makes them feel. We don’t even have to have a disability ourselves. Accessibility is NOT a checklist. Accessibility is about usability. Accessibility is a paradigm shift. Accessibility is a personal issue.
How shall we design accessible GUIs? Which are the main problems, which are the right paths and techniques for doing this? The article is a story about an experience, about the development of an accessible GUI and an analyses of the procedures.
Because of limited awareness around Deafness and accessibility in the web community, it seems plausible to many of us that good captioning will fix it all. It won’t. Before we can enhance the user experience for all deaf people, we must understand that the needs of deaf, hard of hearing, and big-D Deaf users are often very different.