A flexible approach to accessibility
February 14, 2007
Accessibility is now commonplace. Designers, developers, business owners and even advertisers are now seeing the business benefits of accessible websites.
Eyes used to glaze over when we mentioned accessibility. Now those same eyes are passionately telling us all about it. Accessibility is now as important as interaction, branding and aesthetics and fortunately today we can have them all.
Now I am going to contradict myself. Sort of.
Imagine you have a web standards compliant website. It has pleasing aesthetics, semantic markup and good usability and accessibility. Users will enjoy this website and so will search engines.
Now say you want to use Flash on part of your website. Many of us know that Flash and accessibility are like oil and water. However when Flash is used in the correct context it is a brilliant tool for enhancing a website’s usefulness and capacity to communicate but it royally ruins your accessibility rating.
At this point you have three options:
- Proceed with your idea and don’t worry if it is not accessible.
- Proceed with your idea and make your best effort to provide an accessible alternative.
- Bin your idea because every byte of your website has to be accessible.
I like the sound of point two.
If due to accessibility obligations you choose not to use the technology that best suits your content, isn’t that an accessibility problem in itself? By denying users the most appropriate delivery of content aren’t we denying them of the best user experience possible?
Remember not for a moment am I saying we should exclude certain users. That would be lazy, foolish and inherently against Tim’s notion of the Web.
Rather than following wonky guidelines to the letter in an effort to include everyone equally, we need to push forward where we can but at the same time never leave anyone completely behind.
For example. A sophisticated graph is nothing more than a table of data, or an interactive map from Point A to Point B is nothing more than an ordered list of directions.
So what’s stopping us? We can have our cake and eat it too. Sort of.
I would like to clarify that I am not limiting my comments to Flash. PDFs or JavaScript that doesn’t degrade gracefully are just as problematic.
I want to emphasise that I am an accessibility advocate. I understand and support the WAI and believe that accessibility is truly at the heart of any well designed website but so are a lot of other things.
Comments on this article »
-
I totally agree with you, option 2 is always the best way to go.
Oh how I dispise those “accessibility” nuffs who take it to far.
Written by Benjamin on the February 15, 2007
-
Agreed, a combination of accessibility and latest web technology is the path to a great website. If they built a bike with 100% accessibility guidelines it would be solid steel, have huge tyres, safety belts, rollcage and bumper bars.
Written by Doogs on the February 17, 2007
-
It will slowly happen. Its a great relief to see a few forward thinkers working together and bridging a long-neglected gap in web technology.
The trick is to…
1. Employ Flash websites using progressive enhancement…
http://www.adobetutorialz.com/articles/2282/1/Developing-Flash-websites-using-progressive-enhancement2. Which allows for deeplinking…
http://www.asual.com/swfaddress/3. And implements the back button…
http://exanimo.com/as2/StateManagerSo that websites WITH Flash work basically like sites WITHOUT, only better!
Of course, this is quite a bit of work and only suits certain types of projects. But with a little practice, I expect the development of such sites could become very streamlined!
Written by Graham on the February 19, 2007
-
Thanks for those references Milty.
I was not aware that functionality existed with Flash. Hopefully more Flash developers will employ them.
Do you know if it is possible for Adobe to build some of this functionality into Flash, which would make it easier for developers to deploy?
Written by admin on the February 20, 2007
