Monday, 12 January 2009

Accessibility - or why we designed our site to exclude you

"Hello are you responsible for the websites?" - I always dread this question, which out of the 80 web platforms I'm involved in are they talking about, what do they mean by responsibility?

"Well I work on the websites, what is your issue and how can I help?"

"Excellent, well I'm calling from the RNIB, Royal National Institute for the Blind"

"Oh yes, how can I help you sir?"

"Well I can't see your videos"

"... You're blind and you want to know why you can't see our videos?"

The above is a true story, well I only actually said the last part in my head. Was quite a mundane problem, whereby they needed to download a plugin to view the video. But true story none the less.

Earlier this week I had a similar call, this time from a blind user telling me the difficulty he was having with viewing our sites using a 'screen reader' program (which reads out text on websites to allow blind visitors to use the sites). All the hard work we had done to build up a multimedia rich website had made our sites very difficult to enjoy from his point of view. He also had issue with the Central decision to break up our content over a number of pages, by doing this we sneaking increase our page impressions to our sites as we are forcing users to click through multiple pages to view on piece of content. Good way to increase pay impression or good way to alienate visitors? Probably both

It's such a glaringly obvious problem but gets overlooked all the time, not everyone is as smart as you are so they won't do what you want them to. Not everyone uses your browser, has your insider knowledge, or even has the same speed connection as you. This is not a problem that only beginners face, in fact many professionals overlook the accessibility and testing part of websites. Developers working in a central office which we will call Cuckoo Wharf (to be anon) released a national web platform that had not been tested for cross browser compatibility this is when web content works not just on Microsofts Internet Explorer (still the leading browser across the world) but also Mozzila's Firefox, Google's Crome, Apple's Opera.

What's most worrying was the developers at Cuckoo Wharf had only optimized the sites for use in their browsers which wasnt Internet Explorer (you know the world's leading browser) is it too much to ask that we don't alienate the majority.

In the defence of Cuckoo Wharf - accessibility is one of the hardest and most tedious parts of working on the interwebs. People use the web in various different ways, what you believe to be clear and logical seems invisible to others. Unfortunately the closest thing to an answer to this problem is to test, test and test. Let people use your website, ask them what they think of something, see if they can complete a simple task such as finding a section of the site. Good rule of them, is to ask the least web savvy person you know (they're easy to find they'll be the ones on the most money) if they can find something its probably easy to find.

No comments:

Post a Comment