Blog September 2008

Avatar

BBC Radio Spam

I don’t listen to Radio 1 very much now (not live at least, although I download a few of their podcasts) but I’m not so sure they’ve got the hang of this Facebook thing yet...

Radio 1.jpg 

If I’m honest I’m not entirely sure why the Webbists at Radio 1 feel it’s necessary to pick an arbitrary gig to promote on Facebook: surely that’s the Kings of Leon’s responsibility? But the biggest irritant is their apparent need to notify me for every Radio 1 page I become a “fan” of.

What’s more irritating (which is Facebook’s problem) is that I can’t mark a specific update as spam. I don’t mind receiving updates Chris Moyles’ or Scott Mills’ shows as I quite like them, but I don’t want to receive the same thing three (or more) times.

It gets worse though, as both shows have had events in the past two weeks that should have, but weren’t broadcast as updates.

It’s not a big thing I know, but what is the point of having a presence on a social network you don’t understand if you’re not going to engage with it.

Selling accessibility

The first interesting and well conceived Vitanim article in a long while caught my eye today, arriving as it did at just the right time. “How do you get your line manager to buy into accessibility?” is basically the question it answers.

The problem I’ve recently faced as a Web developer who reports directly to a line manager or director (as apposed to working for an agency and dealing only with your project manager) is figuring out how I can take the ideals I built on as part of my agency experience and apply them to working for a company directly.

As a Web developer working for an agency, and especially one with a project manager you’re able to make judgements based on your own skills and experience, because the marketing professional who has hired your company affords that company a certain level of trust: they don’t need to know the nuts and bolts, just that it works for them.

These judgements are largely invisible to the client and are often to do with a perceived level of quality: of code, logic, markup or data structure. An agency developer may choose to sacrifice certain “flashy” functionality for the sake of accessibility or use CSS and XHTML for layout rather than dropping images in place of text, sacrificing time but gaining flexibility in the long run.

Contrast that with working directly for an organisation that doesn’t necessarily have a marketing department and that level of trust changes. It doesn’t lessen, but rather tightens. Although your manager will trust you to develop pages with your own judgement in play, because you’re working for them (whether as a contractor or a permanent employee) you’re expected to whistle to their tune. And that’s fine: they’re paying your wages after all.

But what do you do when your manager doesn’t care about accessibility? It can be costly (under the time = money rule if nothing else) and the benefits are mostly to do with gaining kudos amongst a community that will probably never buy the product or service your employers are selling. So do you tell him he’s wrong? Do you ignore him and carry on, choosing to justify yourself if and when the time comes, or do you try and work accessibility into your practice without throwing it his face?

Although it could possibly go a bit further into providing provable key points that professionals can understand, the Vitamin article on accessibility shares some great starting-point links, one of which being Google’s easy-to-follow Webmaster Guidelines page.

If you’re planning to march into your manager’s office any time soon, preaching the gospel according to Tim, stop, breathe and read Accessibility In Suit and Tie.

Reject the unexpected

When designing a new Website it can often be tempting to think outside the box, but there are pitfalls that need to be avoided to ensure your users aren’t left terminally confused.

Despite all this 3.0 talk, the Web technology is still in its infancy, and like all the technologies we take for granted, it needs time to mature.

Consider TV advertising. In the 50s it was simplistic and brash because advertisers simply didn’t know how people would respond to the medium and so subtlety went out the window. Now we see ads often of breathtaking quality but are left unsure of what we’re actually being sold, because advertisers have the confidence in the savviness of its audience.

The Web is less than 20 years old, and most of its users are still not savvy enough to handle change. They need logos and menus to be where they expect them to be, and they need sites to behave in a way they expect.

Sometimes the temptation to create revolutionary sites that function in new and innovative ways or employ subtle navigation techniques can be all-consuming. We all want a site that is different from the competition, but in the relative early stages of this medium, can we afford to lose users?

I’m not suggesting that all users are stupid, but they do need guidance because many of them are still - even if subconsciously - afraid that clicking the wrong thing could break their computer or result in the payment for an item they never ordered.

It can be very easy to patronise this audience and dumb down your Website in the process, so we as designers and developers need to take great care in balancing usability with innovation.

For now I think the golden rules have to be:

  • keep the logo top left
  • put the menu where it can always be seen no matter how long the page becomes
  • request information via online forms only when that information is needed (ie: don’t ask for an email address unless you’re going to email that person)
  • use sitemaps, search boxes and breadcrumb trails where appropriate
  • avoid too much mouse movement (that means getting rid of that pull-down menu...you know who you are!)