Tuesday, March 09, 2010

Accessibility and your responsibility to the network

By (almost) anyone's count, stats, vibe, gut, whatever... 'social media' is becoming the dominant form of media across the world.

We are collectively and globally spending more of our time taking part in it than we do passively receiving all the other broadcast media put together.

And with that position of dominance comes responsibility.

In large traditional media companies (such as the ones I spent much of my life working in) there is a demand for legal compliance. The big boys sign-up to W3C etc. They also make an effort to make their output e-accessible.

They need to be seen to be meeting the needs of disabled users - whether those users have difficulty, seeing, hearing, moving etc. They see a box they need to tick.

But there appears to be little thought for the needs of these users in many of the most mainstream of social tools, technologies and platforms. (image - an open door - via Ben Zvan)

APIs are of course usually available - which offers opportunities for those with the skills and the inclinations to create tools to improve accessibility. They result in great stuff like Accessible Twitter and EasyYouTube for example, but by no means the whole solution. There aren't enough of them solving the whole range of issues, for a start.

You never see accessibility buttons easy to find on your sign in to Facebook etc. And many a sign-in process includes some unfriendly CAPTCHA processes, too.



I don't have solutions - I do think it's going to take a motivated crowd response to sort out. But I also think, like so much else about a networked world, we all have to take responsibility for each other.

I often say that one extra node on your network doubles its value (that's group forming network theory, folks).

Conversely, if the barriers of accessibility preclude one extra node from joining your network you are halving its value. That's a sobering thought.

Or as Stowe Boyd puts it: "I am made greater by the sum of my connections, so are my connections."

CitizensOnline (the charity which I serve as a trustee) is trying to do something about access to the web - and I'll update you as soon as I'm able on the detail of that. Dr Gail Bradbrook has started a blog on this Fix The Web issue. She's also set up a poll you can take part in:

But in the meantime you could start doing your bit by providing captions for your videos, titling your photographs descriptively and usefully and limiting the abbreviations you use in your status updates (hat tip to Joseph C Dolson)

I'm not going to get this right myself every time. Expect howlers. How do I embed a description in the flickr-hosted image with this post, for example? But I do know it's in my interests - and that of the network - to try.

Reblog this post [with Zemanta]

1 comment:

  1. Interesting point which hasn't received as much attention as it probably should have done in the midst of Facebook redesigns and Twitter implementing new features.

    To be honest, probably the most effective route to providing accessibility is to ensure that the makers and developers of any software are informed and motivated - one side effect of building for 'blind' search spiders is that a lot of accessibility issues are the same for users and search spiders. After all, many companies are actively trying to cut their costs by restricting their marketing/targetting/site access to traffic from their nationality - so whilst accessibility compliance might be something which comes up, the cost of making a non-revenue driving change is always challenging, no matter what value we can put on another node joining.

    But if we can tackle the infrastructure and code, then it's not something which will challenge the non-technically aware...

    Incidentally, along with Youtube introducing captions and transcriptions, to solve the image issue you just need to provide a decent description in the Alt attributes. I can't remember if Blogger features that if you're hotlinking to an image as you've done above, or whether you'd need to save and upload it yourself, but I suspect it does...

    If you work towards accessibility and SEO optimisation, and also try to write in language which is accessible to people, you should have most bases covered. Then it's time to start worrying about accessibility on mobile devices!

    ReplyDelete