Accessibility Also Helps Those Who Live Without A Disability

The implementation of accessibility or accessibility features are often times opposed with the reason that it costs way too much time and money for helping a few people. However, when finally things get implemented, it turns out that it helps many more people than to whom it was designed originally. To take a simple example, though not from the world of technology: ramps were built on curbs and building entrances to aid people who use a wheel chair. In many countries, actual legislation demands it based on disability related accommodation. However, all of a sudden people found out that it is the greatest thing also for those who walk with a stroller, a shopping cart, or on ice, during the winter, for that matter.

The first, probably most obvious reason to make technology accessible is because we do it for ourselves. While we might not need any accommodation now, in our aging years we may not be able to work with things the same way as we did before. One of the true sign of aging is the increasing symptoms of many disabilities at the same time. We might have to turn up the volume a bit, increase the font size, and type a little slower. If we build in all these accessibility features into our software and hardware, we are doing a service to ourselves.

Accessible design also helps increasing productivity. Very often accessibility is associated with certain standards. For example, when coding a web application, according to the Web Content Accessibility Guidelines (WCAG), it is required to use valid code. This means that once a browser finds an error in our code, it tries to correct the mistake and display information the way it was meant to be displayed. This way when we make small mistakes in the code, we won't even notice it when displaying a page. This way it is easier to build slack as opposed to structure into our design process, not on purpose, of course. Following accessibility standards results into a more structured workflow, which will help in error prevention, and implementing other, not accessibility related standards.

Part of accessibility is predictability and usability. It is not enough to make information available in its strictest sense: meaning to put it out there and let the user find it. Information should be presented in a well-organized manner, and functionality should be usable in order to access this information. Once we embrace predictability and usability, all of a sudden we do not only help people with disabilities, but also create a more user friendly experience for all of our users. This ultimately helps us stand out among our competitors.

When we create web applications or design web pages, our goal is to reach an audience. The larger this audience is, the better we can sell our products, or the more people we can reach with our information. When we include people with disabilities in our marketing plan, which means in average one out of five people, not only these people will benefit from it, but we will as well, indirectly, as we have access to a much wider segment of people, essentially, to all people.

And finally, while we look at all the advantages we can gain by creating accessible technologies. Remember, if you can't find a reason at any time for making something accessible, and it is not listed above, the simple reason should be that it is just the right thing to do, we do not have the right to exclude anybody from information which others might benefit from, and we do not have the right to make this choice arbitrarily.