Show 85: Bulletproof

On this week’s show: Paul provides some design advice for developers, Marcus provides so post launch pointers and we review Jeremy Keith’s Bulletproof AJAX book.

Play

Download this show.

Launch our podcast player

News and events

Unfolding the fold

The first news story today is actually not news at all. Well, its news to me (because I wasn’t previously aware of it) but the actual post was made back in December of last year.

The post relates to that most irritating of subjects; “the fold”. I have spoken about the fold many times before. The mythical point at which people have to start to scroll. I say mythical because this point changes depending on your screen resolution, browser type and toolbars.

The reason it is so annoying is because clients are obsessed with it. They are convinced that users don’t scroll (a perception rooted in the early 90s) and no amount of persuasion seems to change their minds.

However, hopefully the post I found this week will help. “Unfolding the Fold” is a post on the ClickTale blog that provides some hard stats about the fold and scrolling in general. It demonstrates that the vast majority of people scroll, with almost all of them scrolling right to the bottom of the page. Their conclusion is that there really is no reason to squeeze all of your content above the fold.

d.construct tickets on sale 10th July

If you are in the UK on the 7th September you should be sure to come to d.construct. d.construct is in my opinion one of the best web design conferences around. The reason I like it so much is that it works hard to maintain a grass root feel that is accessible to anybody.

For a start the price ticket is very accessible at £85 + VAT. Secondly, the whole thing happens on a single day so there is no need for expensive hotel bills if that is a problem. Finally, they have a great mix of speakers with many of the big names you would expect but also a lot of less well known people in order to “shake up the scene”.

The reason I mention it now is because the tickets are going on sale next tuesday (the 10th). Historically they sell out incredibly fast. Although this year they do have a larger venue and so that should help somewhat.

I really want to encourage you to attend this event if at all possible. I will definitely be there and it would be great for us all to meet up.

Fonts licensed for web apps

Talking of d.construct, Richard Rutter (one of the organizers of the event) has posted an interesting blog entry on “font licensing“. Admittedly font licensing, doesn’t sound very exciting but potentially it could be. Richard has spotted a press release from a prominent font provider. This press release talks about a new type of license…

Ascender Corporation announced a new licensing program for font software implementations with server-based applications.

Richard goes on to suggest this might be another move towards browsers supporting downloadable fonts. This would allow us to use whatever font we wished on a website rather than being limited to what the user has on his or her desktop.

Richard does warn that this might just be in reference to Silverlight, because Ascender does work very closely with Microsoft. However, personally within the context of Opera’s move towards downloadable fonts, I am hopefully this might be something more.

A new way to visualize your desktop

Finally today, I wanted to mention a technology called Bumptop. I recently watched a demonstration of the system and was blown away. Basically, Bumptop is a new way to work with files that mirrors much more closing the experience of interacting with your desk in the physical universe. You can stack files, throw them around and even crumple them up in a 3D environment.

When I first watched this demo it felt like a novelty, but the more I thought about it the more potential I saw to organize content in a more dynamic and flexible way.

What I like most about this interface is that it is not trying to teach us a new method of interaction. Instead it is trying to replicate something we are already familiar with. The idea of using metaphors we already understand is a staple of interface design and is what makes things like tabs, desktops and folders so successful.

I think as web designers we could learn from technologies like this. We should be looking to build on established conventions people understand rather than always seeking to do the next big thing or be innovative in someway. Bumptop is innovative but it does so in a way that is instantly accessible to everybody.

Paul’s corner: Design advice for developers

I received this great question from Simon that I thought worth addressing on the show…

I hear lots of questions about the technical and business side of Web design, but what I don’t hear is how do the already technical amongst us become better designers – maybe being a visual thing this just won’t work on an audio podcast, but at least you could give us your top 5 ways to grow artistically.

As has become tradition, I decided to blog on the subject a few days ago but unsurprisingly failed to stick to “5 ways to grow artistically”. Instead I managed to produce a long and rambling essay on “when designers design” which I bore you all with on the show.

Marcus’ bit: Post launch Protocol

Everyone, client and agency, seems to understand the principle of not letting a site stagnate. Content should be regularly updated and, ….and what?

We see a lot of client demands for content management systems that are then often not used for lengthy periods of time. Therefore I thought it could be useful to look at what options there are to a site manager after that big day when the site goes live.

Of course, not everything here will apply to everyone but hopefully some of it will.

News and events

Stories, articles, seminars, fun days, whatever. These are your opportunity to create new content very regularly.

Clients are invariably perfectly happy with their site when it goes live. This is understandable, they have more often than not spent months working on it, tinkering with this, fretting with that and a) they need to spend some time on other aspects of their job (that have been neglected) and b) the site really has never been more up to date!

But what often happens is that a couple of months down the line they realise that new content needs creating but they can’t remember any of the CMS training. The 50 page accompanying manual is too scary so things get left. This happens until we are asked to add the new content because we’re too busy and it’s urgent and often, later on, further CMS training is booked.

News and events provide a steady stream of new content that helps keep the site fresh but also the CMS skills of those looking after the site.

Shortcuts

Updating shortcuts to key content is again a simple way of refreshing a site’s content without putting that much effort in.

Homepage shortcuts tend to link to:

  • Latest news
  • Latest events
  • Repeated main navigation
  • Products
  • Special offers
  • Facilities e.g. login, subscribe etc
  • Important ‘deep’ content
  • Popular topics

I guess the point I’m making here is a lot of these shortcuts can simply be rotated giving a feeling of change on the site. For example, changing a link to a main section on a weekly basis is a simple task and one that does not require the writing of any new content.

Utilising usage stats may be a good way of seeing which areas of the site need further promotion. In fact, use everything at your disposal, stats packages, CMS, content suppliers, agency support contract, internal marketing team etc so that you are as informed as possible.

Imagery

Don’t just update copy. Adding new banner imagery can really rejuvenate a tired looking design. Always look to include appropriate imagery with news articles, events etc.

Communicate

Keep your eyes open to what’s happening within your company/organisation. There may be a new project/department/member of staff etc that might be outside your sphere, that would really add value to the website.

Make yourself (and your role) known to everyone. Send out questionnaires or surveys asking people what they want to see on the site or if they have any pertinent content.

Think big

Finally, don’t lose sight of the main purpose of the site while dealing with the smaller things. It may be that the main purpose of your site is to promote your brand so updating the look and feel of the site regularly may be a lot more important than updated content. In fact, continually evolving the design of a site over time is probably far more cost effective (not to mention the effect it has on keeping the site fresh) than ‘big bang’ redesigns every 3 years or so.

Alternatively, sales leads may be the site’s primary function. In which case, keep in touch with sales and experiment with ways to boost leads.

The other really big area that site owners need to look at is site promotion. This warrants a post of its own so I’ll look at that another time.

Review: Jeremy Keith’s Bulletproof AJAX

I have decided not to do “ask the expert” this week, so we can have a review instead. Unfortunately we don’t have the time to do both segments every week so I have to mix and match from time to time.

The book I want to review is “Bulletproof Ajax” by Jeremy Keith. I read it almost 6 months ago, but haven’t had an opportunity to talk about it on the show until now.

The book is designed to be the sequel to Jeremy’s previous book “DOM Scripting: Web Design with JavaScript and the Document Object Model” which was written as an introduction to Javascript for designers. Bulletproof AJAX is therefore written in a similar tone with the focus on making AJAX accessible to designers rather than providing the technical detail you would expect from a developers book.

I have to confess I found the book a little frustrating at first. As somebody that had bought and learnt Javascript through Jeremy’s first book, I felt a little annoyed that the first 2 chapters seemed to be dedicated to laying the foundations we had already covered in the first book. I am guessing the idea was that people could buy this book in isolation without first owning DOM Scripting, but in my opinion the amount of detail provided in Chapter 1 and 2 wouldn’t make that possible. For me those first 2 chapters felt like padding to make a short book feel slightly more substantial.

However, that criticism aside the rest of the book was definitely worth the very reasonable price tag. Jeremy has an excellent writing style that is clear and engaging. He seems to explain complex topics in such a manner that you wonder what all the fuss is about. You come away from the book thinking this “AJAX stuff” is easy and wondering what all of the fuss is about. Admittedly he only covers the basics, but it is enough to get you producing the kind of AJAX applications most designers would like to build.

But, Jeremy doesn’t shy away from the more complex underlying issues surrounding AJAX. In particular he talks about accessibility and ensuring your applications work with Javascript disabled. He does this through a technique called HIJAX. I will not endeavor to explain to you the details of it here, except to say it relies on the server doing most of the heavy lifting.

From applying the principles taught in this book I have to say the HIJAX approach works very well. All of the complex stuff is handled by the developers on the server side and I get to focus on how the information is returned to the user. AJAX is a funny area that sits between client side and server side and leaves designers and developers wondering who is responsible for what. Using the HIJAX approach taught in this book, the division is much clearer.

So would I recommend this book? As with DOM Scripting it depends on who you are. If you are a designer who has read Jeremy’s first book and would like to start producing AJAX applications then absolutely. However, if you haven’t read his first book then I suggest you do that first, unless you are already confident in producing unobtrusive javascript.

If you are a developer on the other hand then my recommendation is to steer clear. This book is not meant for you and you will find it frustratingly lightweight.

Show 81: Money Matters

This week on Boagworld: Paul gives advice to those who work with content management systems. Marcus finally talks about charge out rates and we talk to Dan Mall and Mark Huot about swfIR.

Download this show.

Launch our podcast player

News and events

37signals in Time Magazine

I notice that 37signals have made it to Time Magazine. This is exciting stuff because it shows the growing awareness in mainstream media of the explosion of web 2.0 businesses. However, the real reason I mention this article is because of what it tells us about how 37signals work. You get to learn about their focus on simplicity, the fact that innovation can happen outside of Silicon valley and their approach to a distributed company.

The one part of the article I personally found particularly interesting is how 37signals’ current suite of products was born out of a need they had to communicate across a distributed company. The idea of building a product that meet a personal need is a good one. It is particularly interesting to me as Headscape has started development of a product which does exactly that. I don’t want to say much more at the moment (as it might never happen), but this article contained a lot of valuable lessons for us.

AJAX tools

I seem to find myself doing more and more ajax and javascript these days. One of the more tricky areas is keeping the user informed about what is going on. I am encountering two specific problems:

  • How to draw the users attention to content that has changed
  • How to inform the user that content is still loading

The latter is fairly straightforward as you simply display a loading graphic. However, I am a lazy sod and can’t be bothered to hand craft a beautiful animated gif. Fortunately this week I came across AJAXload which generates those pretty web 2.0. loading graphics for you. Very nice.

Informing users of changing content is a bit more tricky. I have been aware of the fade to yellow technique for a while but that requires a white background, which my designs don’t ways have. What I didn’t know until I finished Jeremy Keith’s “Bulletproof Ajax” is that there is also a fade to anything technique. This is basically the same as the fade to yellow approach but the background colour doesn’t matter. Simply download the code and away you go :)

Waves of creativity

I stumbled across an article this week talking about the relationship between brain waves and creativity. This explained a lot about my own personal creativity! The gist of the article is that your brain needs to be relaxed in order to be at its most creative. This makes sense for me personally as inevitably I am at my most creative when I am lying in my bed at night.

The sad truth is that we spend most of our lives in a more agitated state and so creativity is hard to achieve. This dove tales nicely with my experience of implementing “Getting Things Done: The Art of Stress-free Productivity” (David Allen). Since reading that book I have felt much more relaxed and in control and hence I have been considerably more creative.

Eric Meyer explain why forms controls can’t be styled

A big thanks to Eric Meyer who has been kind enough to look into the incredibly confusing area of form controls and then explained it to the rest of us. Many web designers express a real frustration with the fact that you cannot consistently style form elements. Although personally I think it is generally unwise from a usability perspective to start mucking around with form elements, I have still always wondered why browser developers have chosen to give us so little control. In a recent post Eric goes into extensive detail about why form controls are “weird” but the upshot is that you are simply better off not styling them.

Agony uncle: Web Design rates

Another question from Bob in Iceland:

“Hi guys, I am becoming increasingly bewildered with what I should charge for web design work. I also do a fair amount of copywriting and content research. What should I charge? Should my rates change for different work? I am a one man band.”

Firstly, I should say that there is no real fixed figure for web design related work. It depends very much on a number of factors, such as:

  • Experience e.g. proven capability to deliver
  • Ability to deliver specialist services e.g. usability testing
  • Size
  • Diversity of staff
  • Location
  • Portfolio

However, to use a real example as a baseline, a survey carried out by eConsultancy a couple of years ago showed that English web design agencies employing 10 to 20 people with a turnover of approximately £1M, charged between £500 and £800 per day for most services. I expect this gone up a little since then.

Setting your rates is partly science, partly weighing up what the market will bear for what you offer.

You do need to work out to the best of your ability what your daily break even cost is but in, in theory, your annual figures should be able to tell you that. The biggest drain on any web agency, unless you have marble and gold clad offices in central London, will be your staff. Good creative/technical people don’t come cheap.

Be realistic from a number of different angles:

  • Don’t try and charge a grand a day if you’re straight out of uni with no experience under your belt
  • Don’t expect to have 100% effort allocation – 70% is excellent
  • Price projects as honestly as you can but remember that clients are human beings and really don’t like paying for project manager anywhere near as much as they do technical development

So should you charge different rates for different services. Again… it depends. Some jobs require a lower level of skill as part of the project. For example, recruitment (though an absolute pain) for any type of testing requires basic organisational skills and not,say, years of experience in project management. If you can outsource that work at a lower rate, then charge a lower rate, but if your PM ends up doing it then you have to charge at your PM rate.

For years we charged a flat rate across the board because it was simpler to manage and we felt clients liked it. Over the past couple of years we have done a lot more consultative work that has placed pressure on the timetables of the directors. This has led us to having the following rate categories:

  • Creative director – Paul
  • Consultancy – IA, business analysis, testing etc
  • Standard – design, technical, pm

We charge a fixed uplift (per client dependent on geographic location) for on site work – kick off meetings, testing etc.

Client corner: Advice for CMS users

I have been putting together a document for work that provides some basic advice for people who work with content management systems. It covers things like accessibility and writing for the web so I thought there might be some value in sharing it on the show. For complete notes on everything I cover check out the CMS user blog post.

Ask the expert: Dan Mall and Mark Huot on SWF image replacement

I was fortunate enough to get some time to chat with Dan Mall and Mark Huot the creators of SWF image replacement. We talked about:

  • What exactly swfIR is and how it works
  • What kind of scenarios they imagine it being used in
  • What inspired them to create swfIR in the first place
  • A little bit about the process of applying it to a site
  • What the future holds for swfIR
  • What it is like working at Happy Cog

No show next week

Just a quick note to say there will be no show next week as I am off on holiday to sunny cornwall. However, please continue to send in your suggestions for the show and don’t forget you can always check out the forums if you want your boagworld fix :)

Show 78: POSH?

This week on Boagworld: Paul redesigns the way clients and designers interact, Marcus asks if you really need a content management system, and Garrett Dimon sharings his experiences of information architecture.

Download this show.

Launch our podcast player

News and events

Breadcrumbs are good, its official

When Jakob Nielsen speaks the world listens. This week he has come out with the shocking revelation that Breadcrumbs are good. Okay, so this doesn’t come as a surprise to most of us, but its still an interesting read. Apparently more and more people have come to rely on this secondary navigation tool and notice if it isn’t there. Jakob believes that breadcrumbs never cause problems in user testing (although sometimes they are not seen) and provide a wealth of benefits to visitors that do use them. Finally, he goes on to talk about the fact that breadcrumbs should always show a sites hierarchy rather than the path a user has taken through a site.

Techcrunch drool over Silverlight

So the guys over at Techcrunch have spent the last week at MIX07 and seem to have been brainwashed by the nice fellows at Microsoft. They are positively drooling over Silverlight, Microsoft’s challenge to Flash. In one post they say:

“It makes Flash/Flex look like an absolute toy… without exaggeration, Ajax looks like a bicycle next to a Ferrari when compared to Silverlight”

Personally, I haven’t had a chance to look at Silverlight yet so cannot express much of an opinion. However, I find it hard to believe that Silverlight will topple Flashes dominance before Adobe responds with something equally impressive.

Although competition can never be a bad thing, it strikes me that this is yet another plugin for people to download and another platform we have to worry about developing for.

RSS in plain english

RSS can be a difficult concept to get your head around the first time you encounter it. Its still a good idea to explain what RSS is on your site for those that don’t know. Obviously you can create a page yourself explaining or sometimes I link to the BBC website which provides an excellent description. Of course if you want something a little more exciting you might want to link to this superb video that explains exactly what RSS is and how it works. Its just a shame they don’t offer the option to embed it directly into your own site.

How POSH are you?

I have to say I was very cynical about this news story when I first encountered it but after hearing Jeremy Keith’s argument on the last .net podcast I have to say I am coming around. POSH is yet another another “catchy” web acronym. It stands for “plain old semantic HTML”. So why do we need yet another acronym? Well the argument goes that nobody is getting excited about semantic HTML these days. Its just not cool. Instead we are obsessed with Microformats or AJAX, things that are perceived as being “in” and “trendy”. The POSH acronym is designed to get us talking about semantic HTML again. The idea is that we start blogging about how we mark stuff up and sharing ideas with one another. The example Jeremy gave on the show was; what is the best way to mark up a conservation in HTML? He suggested that it was simply an ordered list of blockquotes. Do you put that much thought into your code? I can’t say I always do.

So with that in mind I have opened a new section on the Boagworld forum where you can post your examples of good code. You can ask questions like; what is the best way to markup… or simply post how you choose to markup different elements. Whatever the case lets start sharing our good practice in HTML.

Client corner: Do you really need a CMS

Apart from a few ‘design only’ projects we get involved in, every tender that comes through the door includes the words “control over content is a must have”… or words to that effect.

But thinking about all the ‘full’ CMS based projects we have delivered, is that really what the client wanted/needed?

So what types of CMS solutions are there? Here’s a quick summary:

Limited CMS (non-structural) e.g.
  • News
  • Events
  • Popular a few years ago when ‘full’ CMS was a much more expensive.
  • Pros – simple to understand (and build)
  • Cons – clients tend to request more and more areas of the site become CMS controlled and you can end up with a bit of a mess and the cost of replacing can be prohibitive.
Blogging tools
  • Article based
  • With commenting
Full CMS
  • Control over structure: move pages, edit pages, create news pages (and sections) and the front end navigation updates automatically
  • Usually modular: news, events, downloads, forms (dynamic), lists, newsletter, etc
  • User management: Roles, permissions, preview, workflow
  • Licensed or bespoke?

You need to ask yourself a couple of fundamental questions:

Even if I have these tools, will I have time to use them? All websites need to have an owner or editor. Someone who’s job it is to manage all content sources and keep the site up to date. We have been asked many times to carry out work content population work on a CMS that we built…

How much of my content needs updating more than monthly and how often do I need to add new pages to my site? It seems that having the ability to extend a site is often seen as a ‘must have’ when in reality new pages are only added, say, quarterly at most. Added to that, the only content that changes regularly is, for example, news, events and case studies. Employing an agency to add new pages and manage site structure/navigation is not a big job (though some seem to charge extortionate rates). Added to that, clients who do not use a CMS very often tend to forget how to use it and then go back to the agency simply because of that.

To summarise, think very carefully about your requirements in this area and talk to prospective agencies about what they recommend. You could end up making a costly mistake.

Ask the expert: Garrett Dimon on Information Architecture

I am a huge fan of Garrett Dimon’s work and so I am really excited to have him on the show this week. Garrett’s job title is “information architect” and so unsuprisingly he joins us to share some of his experiences on working with information architecture. His advice includes:

  • Embrace constraints
  • Know when to challenge the constraints
  • Explore lots of ideas
  • Work in conjunction with clients
  • Don’t use your computer
  • Throw away more than you keep
  • Don’t worry about the details until later on
  • Simplify and cut back on details
  • Communicating is more important than documentation
  • Make your IA deliverables visual as they are easier to understand

Agony uncle: The wish list brief

This week I am back on Agony Uncle duty with an email from Dan in Swansea:

I am increasingly frustrated by the briefs I am getting through from potential clients. They read more like wishlists than real briefs. They lack focus and often ask for functionality they just don’t need. How do you respond to briefs like that?

Its a great question and set me thinking a lot about the web design process. In fact it was the primary motivation for a recent blog post on the subject which we talk about on the show. I think the key to this question is to not be afraid to go back to the client and challenge them. Perhaps propose a rough costing based on some of the items in their list but suggest that the first step (if you are taken on) would be to define and price a more accurate brief. I think most clients will respect you for suggesting an alternative and more effective strategy. In many ways its like the speculative design argument, it may feel scary to challenge the client before anything is signed but in my experience clients respond positively to a carefully thought through argument.

Review: Spoken Text

A while back I asked people to submit their own reviews. I didn’t specify that people couldn’t review their own product and so I recently received a review from Mark promoting Spoken Text. Now, I don’t want to open the flood gates to shameless self promotion but I like spoken text so much that I want to include it on the show. It is basically a free, text to speech system that allows you to convert multiple file types into audio files.

Mark shares four great reasons why he thinks we might be interested in it as web designers:

  • Use spoken text to provide alternative audio versions of the content on your website
  • Allow users to record and save any content from your website they want
  • Create a podcast of your websites content
  • Create your own podcast of other people’s content that you want to listen to while on the go

There are two things that excite me most about this service (beyond the fact that it is free). First is the accessibility benefits it could bring for visually impaired users and secondly the ability to make instant podcasts of new stories from your site without the complication of finding somebody to present it.

This isn’t a service that is useful to everyone but I think in certain circumstances this could be a killer app.

Show 77: A dream?

On this week’s show: Paul talks about how a client’s work is never done, Marcus looks at dealing with scope creep and we review Dreamweaver CS3 (is it really worth upgrading?).

Play

Download this show.

Launch our podcast player

News and events

The web design survey

A List Apart are trying to build up a picture of the web design community by launching their web design survey. In my opinion this is an incredibly valuable project because there is so little statistical data on our profession. We have next to no information on salary levels, job titles, location, type of work done or even educational background. Its a strange situation for what is now a mature industry. Perhaps, as Jeffrey Zeldman suggests, it is largely due to the fact that we work in a hidden profession where the practitioners have meaningless job titles that bear little resemblance to the work we do.

Coding for content

If you listened to the SXSW special we did a while back you may remember me interviewing Garrett Dimon about the recent redesign of his blog. In that interview he talked a lot about his desire to focus on content and that the design should exist only to support that. The results of this effort are truly phenomenal and he has produced one of the most refreshing sites I have seen in ages. It is clean, easy to use and really succeeds in bringing the content to the fore. Well, this week he wrote an article that follows up on previous comments he made about his design approach by talking about how he coded the site. Its a great article and really shows off the fact that an attention to detail and methodical thought process can really generate some amazing results.

Don’t be a hero: Giving up is good

How often have you heard me drone on about return on investment? Well, now you can hear the guys at 37 Signals talk about the same thing but from a slightly different angle. In their post “Don’t be a hero: Giving up is good” they talk about the fact that developers don’t like to be beaten and will continue grappling with a problem long after it ceased to be profitable. The article argues that it is important to know when you cut your loses and drop functionality if it is simply taking too long to implement.

Working with tables and CSS

It’s amazing how many problems you have with tables even after you have moved across to CSS based design. One common problem I see a lot is the data in tables pushing out the tables width which in turn often breaks the design (see an example). Fortunately this week I found a post that seemed to solve the problem. It uses the table-layout property in CSS along with overflow:hidden. Its a useful little technique that is definitely work checking out.

Client corner: A client’s work is never done

In last week’s client corner section I talked about the role of the client and how in many cases it is very poorly defined. This started me thinking in more depth about how clients perceive web projects and how they often fail to grasp the enormity of the undertaking. In this weeks show I explore the ongoing commitment that clients have to make to their websites and look at what exactly they will find themselves doing on a day-to-day basis. As with last week’s client corner, this is a subject I have recently blogged about and so if you want to refresh your memory on what I said in the show check out my blog post on the subject.

Agony uncle: Dealing with scope creep

This week we will be reviewing a question from Bob in Iceland – “How should I deal with clients that keep changing the spec throughout a project?”

I guess the first thing to say is that the spec will change, they always do. Often it is perfectly understandable because people see a new design or piece of functionality and think ‘hey, we could do X or Y as well’.

But… and I have been as guilty of this as anyone… often the scope will creep as the client learns about the web development process as the project goes along. This is avoidable. It can often be seen as pedantic, or possibly even negative, to spell out exactly what a client is getting. For example, design iterations or template styles. Ask yourself when writing the spec – would a layman understand this? If not, then add notes to explain.

So, what to do when the first request outside scope comes in? As with most things, use your brain regarding how to respond!

If it is a 5 minute job then just do it, but make sure that client is aware that it is outside scope so a) you can earn some points with them and b) let them know that you are keeping a tight eye on the scope of the project.

Anything over that, you need to respond in writing (email is fine) stating that the work is outside scope and you estimate it will take X hours to complete… please confirm that you wish us to go ahead with the work. This puts the onus back on the client and makes them think about whether they really do want the work done.

It is good practice to have a change control procedure written into any statement of work. These can sometimes be over the top, demanding contract extensions in writing and the like (which probably is appropriate for a large new piece of work) but usually something like –

As and when issues arise, it is the project manager’s responsibility to raise these with the client and agree any actions to be taken.

If any rescheduling is required, the project manager will be responsible for ensuring that acceptable changes to the schedule are agreed with the client and documented.
The project manager will maintain an issue log and ensure that issues are either closed following discussion with the client or result in an agreed change to the project plan, with associated change documentation including price change where required.

Basically, this is saying ‘use your head’ and make sure you write down whatever is agreed.

Sometimes, however, it is wise to carry out additional work as a gesture of good will. This is usually appropriate if you ‘owe’ the client a ‘favour’ of some sort, for example if you had charged 5 days to produce a design and it took 1 because they signed it off immediately. You don’t necessarily actually owe them anything (assuming a fixed price contract) but they will be aware that you didn’t put in as much effort and probably won’t take a kind view to your charging them for an extra half an hour’s work at the end of the project.

Review: Dreamweaver CS3

I finally got my hands on a copy of Dreamweaver CS3 this week and although I am still taking it all in I thought I would share some of initial thoughts.

I guess the question you want answer is whether it is worth upgrading or not. As normal the answer isn’t black and white. If you are a a strong standards based designer who has worked with things like DOM Scripting or AJAX then this upgrade probably isn’t for you. However if you are still finding your feet with CSS and don’t want to learn Javascript then this upgrade is definitely worth considering.

Obviously Adobe is trying to pursued us that Dreamweaver offers a huge range of reasons to upgrades such as better Photoshop integration and improved browser testing. However, when it comes down to it, I believe it only offers two killer features.

CSS Layout made easy

If you are new to CSS this feature might be useful. It basically allows you to select from a series of CSS layout templates to get you started. Now, this never replaces hand coding it from scratch, however if you are anything like me you find it easier to learn from example and this certainly helps with that.

Spry framework

If you have tried and failed to get your head around DOM Scripting and AJAX then I would suggest you start off by buying “DOM Scripting: Web Design with JavaScript and the Document Object Model” (J. Keith) or “Bulletproof Ajax (Voices That Matter)” (Jeremy Keith). However, if even that fails then you might want to take a look at the Javascript framework now built into Dreamweaver CS3. As with CSS layout I should stress this isn’t as good as hand coding because:

  • you are stuffed if you want to add or amend functionality not offered from within the framework.
  • the code is bloated in places meaning it will make the page take longer to download.

However, that said, the functionality offered in Dreamweaver is very impressive. You can achieve all of the following without touching a line of code:

  • Work with XML datasets (like RSS feeds)
  • Expand and collapse content areas
  • Make accordion menus
  • Validate forms

The code isn’t great but at least from what I have seen it degrades reasonably and isn’t too intrusive.

If you are a confident CSS and DOM Scripting coder then the upgrade offers considerably less. Personally the best thing I saw was the ability to sort my CSS files in a drag and drop approach. Beyond that and copy and paste straight from Photoshop, there really isn’t much to get excited about.

The question is; has Adobe done enough with Dreamweaver CS3 to keep themselves ahead of Microsoft’s Expression Web which reports say is very impressive. Personally the lack of mac support in Expression Web could well be the deciding factor in what otherwise are very equally matched products.

“Adobe Dreamweaver CS3 (PC)” on Amazon

“Microsoft Expression Web (PC)” on Amazon

Show 74: Marcus 2.0

This week: Is scrolling a bad thing, using frameworks to speed development, encouraging goodwill among your visitors and Marcus 2.0.

Play

Download this show.

First of all let me apologize for the somewhat sparse show notes this week. Things are particularly manic at the moment and so I don’t have the time. If somebody fancies doing a better job then email me with a better version and I’ll upload them here.

News and events

Google My Maps

Google deliver a body blow to the various Google Map mashups that help you plot your own points by releasing My Maps onto the world. Now if you want to build your own Google map you can do so simply by clicking on the My Maps link on the Google Maps homepage. You can then save the maps, email them or link to them from your site. However if you want to directly embed a map into your site then you will still need a third party service. Personally I recommend Map Builder.

What it takes to be a great web designer

I was relieved to discover this week that I don’t need to talented be a great web designer. An article on boxesandarrows points out that skills such as working quickly and attention to detail are just as important.

Setting up a web design business

Rich Quick (author of the Web Design Book), has posted an excellent article on how to go about setting up a web design business. Although not very detailed and specific to the UK it does provide an excellent starting point for anybody considering going freelance.

Machine Tagging

Machine tagging seems to be what all the cool kids are doing these days. Jeremy Keith talks about some of the ways he and Rich Rutter are using machine tags to enhance their websites. He is also kind enough to explain what the hell machine tags are!

Client corner: Generating goodwill

I have just got my new copy of Steve Krug’s book “Don’t make me think”. This updated version has loads of extra content including a chapter dedicated to creating brand goodwill using your website. In this week’s client corner we look at what Steve covers in this chapter and exactly how you can improve or damage peoples perception of your brand via your website.

Ask an expert: Server side frameworks

On this week’s ask an expert section, I ask Jonathan Snook about how frameworks can speed up the development process of server side applications. He talks about what frameworks are, their benefits and drawbacks and which framework is best.

Agony Uncle: Is scrolling bad?

I spotted an interesting post by Ronald on the boagworld forum asking whether scrolling is bad or not. In this week’s segment I attempt to expose some of the myths surrounding scrolling, why historically it has been perceived as an issue and what rules of thumb to use when working with scrolling.

Review: Adding RSS to your website

Its not uncommon to want to add an RSS feed onto your website. You might want to include your twitter posts on your blog or news stories on your corporate website. Whatever the reason it can be a pain to set up. One option to avoid this hassle is to use a service like Feed Digest. Not only does Feed Digest allow you to post RSS content to your site, it also allows you to work with multiple feeds, edit the format of the output and filter the content from the various feeds.

Again let me apologize for the lack of detail in the show notes this week. However, for those of you who cannot listen to the show you might want to view the script that I work from (PDF: 82kb).

Show 68: Tagtastic

This weeks show includes hints on email campaigns, writing Web design contracts and site navigation approaches.

Play

On this week’s show; Matthew Patterson from Campaign monitor shares some handy hints on sending an email campaign, Marcus finishes his series on web design contracts and Paul looks at some interesting alternative approaches to site navigation.

Download this show.

To subscribe directly within itunes click here

News and events

Diversity in web design

This week the web design blogosphere has been dominated by discussions about the lack of women speakers at conferences. Jeffrey Zeldman, Eric Meyer, Jeremy Keith, Tantek… the list goes on and on. Frankly, I find the debate less than helpful. It is interesting to note that all of the women I have seen post on the subject have seemed very defensive almost as if they are under attack for not speaking more!

More on Open ID

Open ID continues to build momentum with both AOL and Digg.com saying they will support the standard. Dan Webb also provides a guide on how to support Open ID in your web applications.

Validation: why it matters

Ethan Marcotte has just published an interesting article on the List Apart website looking at the business benefits of validation and why it continues to polarise the web community.

The sorry state of web accessibility

The subject of web accessibility receives another body blow this week with Mike Davies posting a damning criticism. What is probably most disturbing is that I am yet to find a post disagreeing with him.

Client Corner: The statement of work (final chapter!)

This week sees the end of Marcus’ series on the statement of work (I know, it is distressing for us all!). In this final segment he takes a look a:

  • Milestones and timescales
  • Project management
  • Testing
  • Deliverables
  • Pricing

Ask an expert: Matthew Patterson on email campaigns

Matthew Patterson works for campaign monitor one of the best email management sites about. Their site is stuffed with great advice for those thinking of running an email campaign and so it seemed only natural to get him on the show and get his thoughts on how best to run a successful campaign.

Non hierarchical navigation

Headscape was recently approach by a potential client who had literally hundreds of thousands of web pages which were almost impossible to organise into a traditional information architecture. They wanted us to suggest some alternatives and so I thought this sounded like a great issue to cover on the show.

Instead of trying to stuff everything we covered in those show notes, I have instead posted a separate article on non hierarchical navigation which includes everything I said and the links I mentioned. Hope you find it useful.

Show 65: Dying (Man Flu!)

This week on the Boagworld Podcast, Paul and Marcus drag themselves from their death beds to share why you should care about Vista and Drew McLellan explains the pros and cons of Ruby on Rails.

Play

This week on the Boagworld Podcast, Paul and Marcus drag themselves from their death beds to share why you should care about Vista, which browsers you should support and introduce you to the exciting world of terms and conditions. Oh yes and Drew McLellan explains the pros and cons of Ruby on Rails.

Download this show.

To subscribe directly within itunes click here

News and events

Barcamp

The weekend of the 17th of February sees the second barcamp to take place in London. If you haven’t come across barcamp, it is a gathering of web geeks where everybody takes turns to present a 30 minute session. You can pick which sessions you wish to attend and the whole thing has a very informal feel. Its free and arguably one of the most valuable meetups of the year.

Paper prototyping

There is an excellent new article on the List Apart website. It proposes closing down your PC and returning to good old pen and paper. Compelling stuff, which should make you evaluate the way you develop your designs.

Bulletproof AJAX

Jeremy Keith is about to release the follow up to DOM Scripting, Bulletproof AJAX. As with his previous book Bulletproof AJAX is aimed squarely at the designer community. It will be perfect for people who have read DOM Scripting and want to take the next step. If you can’t wait that long and can squeeze £295 out of your boss then you might want to attend Jeremy’s AJAX workshop down in Brighton. I have attended it myself and it is extremely good.

Custom reading containers

This is an incredible proof of concept that I was emailed last week. Basically it enables the user to resize elements of your web page to suit their requirements. Admittedly it has only undergone limited testing so far and relies on PHP; nevertheless it looks very interesting indeed.

Client corner: Terms and conditions

This week Marcus starts a new series on client contrasts with a “fascinating” look at terms and conditions… I know… control your excitement! Some of the points he covers include:

  • Make sure you read the T&Cs carefully no matter how boring they are!
  • Get advice if you don’t understand something
  • Make sure you note the governing laws that cover the T&Cs
  • Note the deliverables and rights
  • Understand your liability if there are problems

Agony Uncle: Browser support

Danny has sent in an excellent question about how far we should go in supporting the numerous browsers out there. Should we support IE5, Opera mobile, Opera on the Wii and so on? In the show I talk about the need to not set hard and fast rules in this area but adapt to the individual requirements of our clients. I talk about not blindly accepting the browser support requested by the client but rather analysing statistics to establish the best browser set to build for. Finally I also explain the concept of graded browser support as implemented by larger organisations like Yahoo!

Ask the expert: Ruby on Rails

Talking of Yahoo, this week our expert is Drew McLellan who works in their development team. He is on the show discussing the pros and cons of working with frameworks like Ruby on Rails.  Among other things he looks at speed of development vs. maintenance and generally gives a nice overview on the subject. He certainly helped me have a clearer understanding of the benefits and drawbacks.

Review: Vista

So Vista has hit the shelves and being the uber geek that I am I couldn’t resist upgrading as soon as I got my hands on the disk. I know there are loads of reviews on Vista but I thought it was worth reviewing specifically from a web designer’s perspective. I talk about the problems I had installing Photoshop, the improved FTP support and the multiple website support now in IIS. I also look at how Vista could potentially change the way people interact with the web by bringing things like desktop widgets and RSS feeds to the masses.

2007

Well I am back from my Christmas break and I am really looking forward to 2007. In particular I can’t wait to get going on the new .net podcast and the revised boagworld show.

It was a great Christmas this year. I got a Nikon D50 and so my flickr feed has exploded. Combined with my new digital picture frame it has been a typically gadgety Christmas.

Of course it was hard to come back to work, especially when your son burst into tears because daddy won’t be around as much to play with him. However, on the upside I get to podcast again which I really enjoy.

Changes to boagworld

We are revamping the boagworld show. Towards the end of last year it was becoming a bit stale and both of us were having trouble getting enthusiastic about it. The new show will be shorter, snappier and split into clearly defined segments.

The bit I am most excited about is the new “Ask an expert” section. This will include various “experts” answering questions submitted by you the listeners. Already I have answers from Jeremy Keith and Christian Heilmann; however loads of other people have agreed to take part.

Practical Web Design becomes .net

Of course it is not just the boagworld show that is changing. We are also relaunching the Practical Web Design podcast in a new form from the publishers of .net. This show is going to be totally different to anything I have done before and I have a mixture of fear and excitement about it. Its going to be a round table discussion via skype made up of numerous well known web design names as well as a few that you need introducing to! We already have a list of over 20 people who are willing to come on the show and I am sure this will get even bigger once the show is launched.

My fear comes from the technical side of production. Skype isn’t always the most reliable technology but hopefully it will be up to the task. If not then we will have to think again. However, you never know until you try.

As for timescales, well I am not quite sure when we will launch the .net show. However, boagworld will be back on Tuesday 9th January and will now always go out on a Tuesday.

Boagworld meetup

Finally, I also have the boagworld meetup in London to look forward to. I have met the occasional boagworld listener before at conferences etc, but it will be nice to meet a load of people in one go. Currently there are 22 people attending and that’s before I have announced it on the podcast. It should be a cool evening.

My Sledge Hammer List

I got into a very strange conversation today on Twitter that resulted in Chris Heilmann suggesting I broke the hands of any designer I felt was more talented than me. With that in mind here is the list of people I intend to attack with a sledge hammer at SXSW.

Of course the list could have gone on much longer, but the sledge hammer is heavy and I have a feeling I might be tired by the end of the list.

Who would be on your list?

Refresh06

So Refresh06 is now over and I am mere moments away from heading back to the UK. Although the conference suffered from the occasional hiccup it has been incredibly enjoyable and I have been inspired by the amazing people I have met.

It has been a pretty incredible time and it’s hard to know what the highlight was. A good contender is the behind the scenes tour of the Kennedy Space Centre organised by a boagworld listener Benny (who is a real life Rocket Scientist!). However, good as that was, I would have to say the top spot has to go to the people I have been fortunate enough to meet.

I am not a big conference goer or indeed even a regular member of the web design community. However I have been made to feel incredibly welcome over the last week. To a large extent this has been down to Andy and Jeremy who have both taken me under their collective wing. Despite the constant humiliation and piss taking, they have both made a point of introducing me to new people and making me feel part of the gang.

And what a gang it is. I am not even going to try and mention everybody I have met, however I would like to say a special thanks to Jina, Dan, Cindy, and Jade who seemed to endure me for longer than most.

For me conferences are all about the people. The talks are a secondary factor. I guess that is a strange thing for me to say as somebody who was speaking at Refresh06 but I honestly believe there is more to learn about web design by chatting over a pint than sitting in a conference hall.

Refresh06 wasn’t perfect. The organisation could have been tighter at times and there have been some problems with the audio recording (meaning my sessions are not going to be available). However, for me none of that matters. What matters is that I got to talk to some incredibly talented people and meet my web design superhero Cameron Moll (although I was too shy to have a long conversation with him!).

All in all a brilliant time and I cannot wait to SXSW.

No show: Making Marcus Jealous

Just a quick reminder that there will be no boagworld podcast this week as I am living it up in Florida.

I know I announced in last week’s show that I wouldn’t be putting out a podcast this week but I just wanted to remind you all because I know you don’t always pay attention ;)

I guess if I am honest I also wanted to rub Marcus’ nose in the fact that I am sunny myself in Florida while he is enduring the British winter. However, Marcus will be pleased to know that Jeremy Keith and Andy Budd are keeping me in my place (through various imaginative put downs) so he doesn’t need to worry too much about my ego over inflating.

In case you don’t know I am in Orlando in order to participate in the Refresh 06 web design conference. I am really excited about it and can’t wait for it to kick off. There are actually a few places left so if you are quick you might be able to grab a ticket and join us. Go on, you know you want to!

Anyway, must go… I am off to Universal studios soon!

Book recommendations

One of the most common questions I get emailed with is “what book would you recommend for XXX”. As I find myself continually recommending the same set I thought I would post a list of them here.

Update: Just a quick note to say that I have updated this post with some new books and will try and continue to do so in the future. Please note that this list only contains books I have personally read so bear in mind there maybe better books out there :) If you can’t be bothered to periodically check back then you can always subscribe to my booklist feed on delicious

Build your own website the right way using HTML and CSS

This snappily named book is written by Ian Lloyd (of accessify.com) and is perfect for those starting out in web design. This book will teach you how to build websites from scratch. No previous knowledge required. What is more, as the title says, it shows you how to build them "the right way". A refreshing change when compared to most web design books out there.

Buy Build your own website the right way at Amazon

The Zen of CSS Design

This book is basically made up of a series of case studies based on designs found at CSS Zen Gardens. In my opinion it is ideal for developers who are trying to improve the quality of design on their sites. The book is a mixture of CSS tips and design advice.

Buy the Zen of CSS Design at Amazon

CSS Mastery, Advanced Web Standards Solutions

Andy Budd’s book is perfect for those of us who have been using web standards for a while. We know the basics and are looking for advice to make us more efficient in our coding. This book is packed with all of the techniques you would expect plus some extra tip bits that make you slap your forehead and wonder why you never thought of doing things that way.

Buy CSS Mastery, Advanced Web Standards Solutions from Amazon

DOM Scripting

Jeremy Keith gives Javascript a new lick of paint, calls it DOM Scripting and blows your mind with its potential. If you are a designer who has always shied away from Javascript then this book is a must read. Jeremy teaches you Javascript from the ground up and then shows you just how much it can enhance your design.

Buy DOM Scripting from Amazon

DHTML Utopia: Modern Web Design Using Javascript & DOM

If you already know the basics of Javascript then Stuart Langridge’s book is probably a better bet than DOM Scripting. Stuart teaches you all the latest techniques of unobtrusive Javascript and throws in a bit of AJAX for good measure. Probably a bit heavy going for your average designer but easy fodder for you hard core developers.

Buy DHTML Utopia from Amazon

Designing with Web Standards

If you need convincing about all of this web standards rubbish then Zeldman’s book is for you. This book will give you the history of web design and explain why we have ended up designing with tables. It explains why web standards rock and then gives you a whistle stop tour of the basics. A must read for anybody starting out in web standards.

Buy Design with Web Standards from Amazon

Web standards Solutions

Of course once Zeldman has convinced you of the value of standards and got you doing the basics, you are going to want to get into the details. That is where Dan Cederholm‘s book comes in. This handbook covers every conceivable area of CSS based design and shows you all the tips and techniques. You will find yourself thumbing through it regularly.

Buy Web Standards Solutions from Amazon

Getting things done

This book has nothing much to do with web design but I would high recommend it anyway. Getting Things Done provides great advice about organizing your life to make your more efficient both at home and at work. Also a lot of what he covers is directly relevant to running successful web projects.

By Getting Things Done from Amazon

Laws of Simplicity

Again not directly about web design but invaluable none the less. This book talks about simplicity in life, in work and in design. The principles laid out in this book are a template for good design. If you design user interfaces you should read this book.

Buy The Laws of Simplicity from Amazon

Bulletproof AJAX

I think the best way to describe this book is as the sequel to DOM Scripting. Where DOM Scripting taught designers Javascript, Bulletproof AJAX takes you the next step on. I have to say if you have read DOM Scripting there is a lot of repetition in this book but nevertheless it is worth the money

Buy “Bulletproof Ajax” (Jeremy Keith) from Amazon

Don’t make me think

If I could recommend a single web design book then I think it would be this one by Steve Krug. Zeldman’s book on Web Standards is a close runner but this book covers the fundamentals of user centric design. You learn why usability testing is so important and are even taken through the processes of running a session. It is down to earth, practical and at times very entertaining.

Buy “Dont Make Me Think” at Amazon

Prioritizing web usability

Jakob Nielsen can be a bit full of his own self importance at times but he definitely knows his stuff. If you can work through the first chapter where he tells the world how clever he is then you will find a very valuable resource with lots of real world examples.

Buy “Prioritizing Web Usability” (Jakob Nielsen) at Amazon

The Tipping point

The Tipping point is not about web design but is a must read anyway. It talks about the concept of ideas and products going viral. How do some products or trends suddenly spread like wildfire? How do you make that happen? It discusses how small changes can have a big impact. Its invaluable to web designers because it shows how reaching the right audience and presenting information in the right way can have a profound impact on the success of your website.

Buy “The Tipping Point: How Little Things Can Make a Big Difference” (Malcolm Gladwell) at Amazon

Mobile web design

This book takes the principles of web standards and applies them to the mobile web. Cameron Moll discusses the different approaches to taking the web mobile from doing nothing to creating mobile specific websites. The book really does tell you everything you need to know to start building mobile websites in only 100 pages.

Buy “Mobile Web Design” (Cameron Moll)

External Links and new windows

Not long ago I shared some advice on handling links within your web pages. Today I want to cover linking to external sites. However, be warned, this is not a normal boagworld.com post… it contains code!

27/07/06: I have finally got around to updating the code below to reflect feedback I have received via the comments. Thanks to everybody who has contributed.

What to do with links to third party sites has always an area of debate. The accessibility purists argue that the practice of opening new windows when linking to external sites is evil and that if users wish to, they can do so themselves. However, if you have ever sat in on a usability session you quickly learn that simple things like launching a link in a new window is beyond many users. Furthermore, with so many bad sites around you cannot always rely on the back button to return the user to your site. Of course, at the end of the day these kinds of debates are redundant because if the client demands it, you will have little choice in the matter.

The golden rules of new windows

Whether you like it or not sooner or later you will have to open external sites in a new window. The trick is to ensure that this link doesn’t make your site break WAI guidelines on accessibility or invalidate your code.

Accessibility

The first problem relating to accessibility is relatively easy to solve. The guideline in question states:

Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.

The trick to complying with this checkpoint is to "clearly inform" the user that a new window is going to open. I recommend doing this in two ways. Firstly, assign the link a title tag telling the user the new window will open. Secondly, because you cannot rely on the user hovering over a link before clicking, add an icon after the link showing them something different is going to happen.

Validation

The issue of validation is a bit trickier. Normally to launch a link in a new window you use the target attribute. Unfortunately, this attribute is on the way out and will more than likely invalidate your document. Ensuring that your HTML is valid now and in the future is good practice for numerous reasons that I won’t go into here (if you want to know more about validation read my post on the subject). Sufficed to say that using the target attribute is not the answer.

Flexibility

What if your client changes his/ her mind in the future? Do you really want to be going through potentially thousands of pages altering all of the links? What you need is a solution that manages all of these links centrally so that by changing a few lines of code you can change the behaviour of all of them at once.

A neat little solution

If Jeremy Keith has taught me anything, it is that DOM scripting is great for this kind of stuff. In three easy steps, you can create external links that open in a new window while still being accessibility, valid, and flexible. Here is how:

Step 1: Semantic code

Remember we might want to change our minds about spawning a new browser window later so no target attributes or title tags talking about opening new windows. Each link to an external site will simply read as follows:

<a href="http://www.headscape.co.uk" class="">Best web design company ever!</a>

All I have done is say this links to another website with the class="", other than that it’s an ordinary link.

Step 2: Apply the JavaScript

The JavaScript function below does the following:

  1. Looks at all of the a tags on a page searching for those labelled ""
  2. Changes the class of those tags to "newWinStyle" (I’ll explain why later)
  3. Adds "(new window)" to the end of the title tag so users know it is going to spawn a new window
  4. Attaches an "onlick" event to those links so that when they are clicked it opens in a new window.

// Opens a link in a new window when class =
function doPopups() {
if (!document.getElementsByTagName) return false;
var links = document.getElementsByTagName("a");
for (var i=0; i < links.length; i++) {
if (links[i].className.match("")) {
links[i].className = links[i].className + " newWinStyle";
if (links[i].title == "") {
links[i].title = "(new window)";
}
else {
links[i].title = links[i].title + " (new window)";
}
links[i].onclick = function(e) {
if(!e)e=window.event;
if(e.shiftKey || e.ctrlKey || e.altKey) return;
window.open(this.href);
return false;
}
}
}
}

If JavaScript is disabled the link still works but opens in the same window. That is why the title tag is applied in JavaScript. If the "new window" message was added in the html it would cause confusion if JavaScript is disabled and the window spawning didn’t happen.

Step 3: The CSS

In your CSS file, you can now create a new style for "newWinStyle" and make external links look however you want. The reason you do not style "" directly is for the same reason mentioned above. You don’t want a new window icon appearing if Javascript isn’t enabled and the link wont spawn a window.

Added bonuses

This simple little approach has some great added bonuses too. Firstly, the content providers who create the links in the first place don’t need to add title tags or set the destination window for the link. Secondly, it would be easy to create an additional bit of JavaScript that allows the user to enable or disable window spawning. This gives the control back to the user where it belongs.

So what do you think? Have I missed something? Can this approach be improved? Do you believe you should never spawn a window?

Web Design Podcast (9) – Jeremy Keith Interview

This week Paul is joined by Jeremy Keith, author of DOM Scripting and joint head of the WASP DOM Scripting Task Force. Paul and Jeremy look at how to take the principles of web standards a step further by separating function from content as well as just design.

Play

Download this show.

Below are links to a number of resources discussed in the podcast:

A better way to build websites
A boagworld.com article introducing web standards and explaining their benefits.

Web standards at all costs?
A boagworld.com article discussing whether there are occasions where table based design can be justified

Adactio
Jeremy’s personal website including a shed load of invaluable articles!

DOM scripting book
A superb book my Jeremy aimed at introducing designers to unobtrusive JavaScript.

DOM Scripting task force
Apart of WASP this group is dedicated to bringing the quality of scripting up to that of XHTML and CSS.

Unobtrusive JavaScript Tutorial
An excellent introduction to Unobtrusive JavaScript by Chris Heilmann.

clear:left
Jeremy Keith, Andy Budd, and Richard Rutter have joined forces to form clear:left, a new web design company based in Brighton.

d.construct
The UK’s first grassroot web 2.0 conference. Unfortunately this is now sold out.

@media 2005
The @media 2005 conference brought together the biggest names from around the world to talk about the hottest topics in web design – web standards and accessibility.

HTML dog
The web designer’s resource for everything HTML and CSS, the most common technologies used in making web pages.

WASP
The Web Standards Project is a grassroots coalition fighting for standards that ensure simple, affordable access to web technologies for all.

Web Design Podcast (8) – Jakob Nielsen

This week usability guru, Jakob Nielsen, has released his top ten web design mistakes for 2005. Paul and Marcus review the article and provide their own unique perspective on the great man of usability!

Play

Download this show.

Below is a brief outline of the things covered in this week’s podcast as well as links to some of the sites mentioned:

Feedback

Our thanks to Nick for providing this brilliant example of a site that fails to give the user any idea what it is about…visit periscope now

Thanks too go to Ed for spending us our first MP3 question. If you would like a question answered on the boagworld.com podcast send us an MP3 to [email protected].

News

We are delighted to announce that boagworld.com has teamed with the "Practical Web Design" magazine. Our podcasts are going to ship on their cover CD along with some shows done exclusively for them.

Over the coming week we will be doing an interview with Jeremy Keith of WASP. We are delighted to have Jeremy on the show and can’t wait to do our first interview!

Boagworld.com is running a survey to better understand the needs of our listeners. It will only take a couple of minutes and is completely anonymous. Take the survey now!

Main feature

We do not have much in the way of notes for this weeks feature as it was a review of Jakob Nielsen’s "Top Ten Web Design Mistakes of 2005". We suggest you read the article and decide for yourself if you agree or not!

@Media2005

@Media 2005 was the first Web standards and accessibility conference here in the UK and only the second worldwide. The conference demonstrated a growing commitment to building accessible and standards friendly web sites.
So what came out of the conference and why will it affect the way we all build web sites.

I was fortunate enough to attend this two day conference and had the opportunity to listen to some of the leading figures in web design. They spoke about how the way we build web sites will change and how it will benefit us all, both users and site owners alike.

I have to confess I was totally inspired by the conference and so here are just some of my initial thoughts:

Taking standards based design the next step

I probably haven’t spoken about standards based design enough on this site before, but what I have written has hopefully explained that web standards are about separating content from design. This has a whole range of benefits including, but not limited to;

  • faster download time,
  • sites being easier to maintain or redesign,
  • greater accessibility,
  • available to a greater range of browsers and devices,
  • better print capability.

However what really inspired me was a talk by Jeremy Keith who took the idea one step further and suggested we also separated out behaviour from content.

If you have read my blog before you will know that I try and avoid technical jargon because there are enough people out there providing the technical detail. With that in mind I am not going to get into the specifics of DOM and Javascript and exactly what I mean by behaviour. However what I will say is that by separating out interactive / functional elements from your web site you gain a number of advantages. These include:

  • the ability to manage all of your functionality (such as popup windows etc.) from one central source,
  • a cleaner, more accessible web site that will still work even for people without the software to view the extra functionality,
  • the ability to add new functionality site wide without editing each page that the functionality needs to appear in.

The beauty of Design

Douglas Bowman gave two very inspiring sessions that raised a number of interesting points. One of the issues he touched on is something that is particularly close to my heart and something which I believe is fundamentally important to good web design. He spoke about our tenancy as designers to be constrained by the practicalities of web page construction and that this often stifles our creativity.

So many web sites look the same, not because they are trying to conform to design standards (which is something I whole heartedly support) but because the designers have an inability to think outside of the constraints of the medium. Douglas encouraged innovation where we design first and work out how to build it later. Only by taking this approach can we ensure not only the best design for the job but also that we are constantly pushing back the technical boundaries of web design.

The real face of accessibility

For a long time now I have accepted that we have a responsibility as web designers and indeed web site owners to ensure that our web sites are accessible to the widest possible audience. Indeed I routinely check my sites against web accessibility guidelines and fix individual little problems so they work better with speech browsers. However it wasn’t until a presentation by Robin Christopherson from Ability Net that I fully began to realise how impossible it is to browse the web as a blind user. Robin himself is blind and demonstrated some of the problems faced by blind users. He did a particularly compelling demonstration by attempting to navigate the Amazon.co.uk web site using a standard speech browser. Although I have tested pages before in speech browsers I don’t think I have ever attempted to achieve anything other than basic tasks. Robin’s demonstration was a real eye opener and has galvanised my commitment to creating truly accessible design.

Praise and criticism

For me this conference was a real turning point. I have to be honest that over the last few months I have become disillusioned with web design. As somebody that has been involved in the web since the early days I missed the challenge and excitement of those chaotic times. Somehow things had become very stale and sensible. However @media 2005 has made me realise that I have a real opportunity to shape the way the web develops in the future and make it a much more usable place for everybody.

I have read some comments that have critised the conference and in particular the speakers for being to insular. Some have expressed a sense that those speaking and running the conference were elitist in some way. Certainly they all seemed to be good friends but I would argue that their closeness is one of the reasons they have achieved so much. I have to confess I had a pang of envy that I was not one of the elite who inspired web designers worldwide and is forging the future of the web. However I quickly realised that it is down to people like me and you to implement these new methodologies on a daily basis if we are really going to achieve a more accessible web. You can have all the evangelists in the world but unless they win converts and those converts act on their new found convictions it means nothing. They have certainly made a convert out of me and I thank them for their inspiration and hard work.