Skip to main content

Designing for Accessibility

The software world has starting being more inclusive. After serving only the geeks and the techies, a lot of the software that is produced in this world has started looking at how it can be mor euseful.

One of the key constituencies of software usage is people with disability. The ADA (Americans with disability Act) has forced a lot of the software developers to look at this issue. The software world has also responded sensitively and with care making as much of the software usable by people with disability.

One of the key components that we are looking at in this are people with visual impairment.

Over a period of time, a lot of the software has made sure that the user experience is adjusted in such a way that is is intuitive. Google has been a front runner in this and a lot of others are also not left behind.

Text

The size and the font typology is very important. Choose those aspects with ADA in mind.

Media like Images


A lot of the media , including video and images , have been adjusted to be consumed by people with disability. Most of the videos contains a transcript and a readover text. This helps people with hearing disability to read through the text

All the images and the shades of the pages are toned to make sure people with color blindness understand the intent of an image

Finally, all images are now accompanies with alternative text that helps with the image descriptions

Overall User Journey

Visually impaired people use screen readers all the time. 

Design for a user experience based on how the screen reader interprets the site. You might be surprised on how the screen readers perceive our site and hence the user experience becomes very tedious for visually impaired.

More to come on how to start with making a site ADA compliant.

Comments

Popular posts from this blog

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile:  http://djrusso.github.io More reading from his paper here:  https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision.  I liked the approach of principles for developing systems that are anti-fragile. It i...

The cost of delayed decisions in Enterprise

Large enterprises have started their IT journey in earnest. However, they are miles behind what is happening.  Some of them have been trying to learn faster by creating research programs or separate business unites to try out and learn a few exotic ideas that have not yet gained acceptance in the industry or enterprise. Enterprises have moved record collection and data to IT long back and were pioneers in that. However, since the advent of personal computers, they have been left behind. Internet and mobile have left them far behind. For example, Network security, big data, mobile apps. social applications are solved problems that the enterprise choose to ignore.