Monday, July 31, 2006
Web Standards vs. Flash

As technology presents us with more options for creating web sites, there seems to be two very different and contradictory directions site design is going. One is rich media driven, with Flash at its core, and the other is web standards stressing usability, accessibility and compatibility.

Well done, highly interactive, rich media sites are incredibly engaging, and the direction big money is pushing the web, but they are rarely standards compliant and often are bashed for poor usability and accessibility. These sites communicate their messages effectively to their intended audiences. Mission accomplished.

Web standards are based on are undeniably sound basic principles: separation of content, structure and presentation; and accessibility, usability and compatibility. For sites whose audience requires these benefits, web standards makes total sense. My problem with most compliant sites I see today is they are visually similar and boring. I read somewhere, someone describing them as decorated not designed. It’s true.

Enter stage left, common sense.

The reason all the standards compliant sites look similar is because it is very difficult to mark-up a web page that has an intricate design with many images and requires pixel level accuracy. This can be done in a fraction of the time using tables and spacer gifs, and render properly in all browsers. And besides, there are just as many hacks and workarounds in standards development as old school HTML.

Why use Flash in a self-gratuitous intro sequence, or fancy navigation menu that creates a technological obstacle to a site that doesn’t need the benefits of Flash anywhere else? Many a site has been built using Flash that can be just as good without it. This misuse is what has given Flash such a bad rap with the user centered design people.

Let’s not let the tail wag the dog. Making a site using web standards just for the sake of doing so, or using Flash where it is not needed are both equally inappropriate, especially at the expense of your client.

Surely there’s common ground and a practical approach. Sites should be developed based on their purpose and intended audience. If that demographic can use and enjoy the site, fine. Others outside of that group are not important. Writers write books to a certain audience. Movie directors make movies that are not for everyone. Web producers should have that right too and not be criticized.

Choose the technology or methodology carefully based on the benefits of its use and the cost of using it. Each project has specific requirements and they should dictate the most suitable way to go, not personal preference, or trends.

Left Brain

James Bielefeldt | 7/31/2006 1:21:27 PM (Central Daylight Time, UTC-05:00)