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

The right business model for your product

How would you decide what is the best business model for your product? Deciding on the right business model is very important for the product. It does not necessarily mean what is the price of your product. There could be no price for your product - though that is a myth. For example, we think google or Facebook is free. However, we are never the customers for Google or Facebook. It is the advertisers that are its customers. What we need to figure out when we decide on a business model are as follows: Who is my target audience? Who is my customer What is the price. How is the support model going to work Who are my partners While we do not absolutely need to price a product, we need to understand how we would make money. For example Open ERP does not price its product. However, its product is not the ERP software but really the hosting, service and training that it offers. While pricing is an important part, what is more important is in realising who is you...

Finding your target audience

The biggest task of the product manager is to find your target audience. Typically it is a very tight rope walk. You define it too narrowly and you would struggle to generalize the product later. You define it too broad and you would struggle to satisfy a lot of people and the product might not take off at all. There is this awesome post by Dave Mcclure on why Niche target segment works. Blog link here . What he says is mostly right and that is what we did as well. We did it mostly by accident. We had to define our niche because we could only talk to those kind of retailers and get data from them to start developing the data. It did have its upside. We were very clear on what we wanted to develop and we are slowly talking to retailers and adding more scenarios. As we are doing this, we are also talking to a slightly different set of retailers. This helps us incrementally build our product while also generalizing the existing features. In our case, we did not fin...

Constructing the Product Roadmap

When I started out in the team, I was tasked out with coming out with a plan so that we can demonstrate the product with real data. The idea was to demonstrate it to our prospect with their own data and win them over. However, when I started working, I found out that what we lacked was not a plan but a vision. I quickly put together a one day workshop with our team and our product owner. When we started talking, we talked about several things and figured out that we needed a plan of various proportions. We needed a plan that could help us one the following: Provide a focus for the long term with near term focus on just one thing Help us talk to prospects on what we are going to do Help us decide on when we would need to focus shift on which function - Engineering , sales etc We also did a quick “Product in a box” exercise so that all of us in a team can practice and imbibe the elevator pitch. We needed this since we had to do this pitch at several levels - Inter...