Web Design News 15/06/10

This week: We look at emerging trends coming from Web Direction @Media including microcopy, HTML5 and CSS3 and inclusive design.

Relly talks about microcopy

The one talk I am most passionate about is Relly Annett Bakers talk on Microcopy. As web designers we constantly moan about the quality of copy produced by our clients and yet make the problem worse by producing poor copy of our own.

The problem is that we think we don’t write copy. However that is simply not true. We are forever writing error messages, instructional text and labels. We are also involved in information architecture where we make decisions about the naming of navigation and page elements. All of this is copy.

Whether you get to hear Relly’s talk at @media or not, it is worth learning about best practice in microcopy. Fortunately there is no shortage of online resources available.

For a start Relly has written extensively on the subject including her 24 Ways post ‘construction of instruction‘.

However this is a subject others are tackling too. Joshua Porter has written a great post entitled ‘Writing Microcopy‘. It is well worth a read and is a brilliant introduction to the topic.

example of microcopy from Joshua's article

Finally Joshua has also created a Microcopy Flickr Group which showcases great examples of microcopy. If you are looking for some inspiration as you write, this is a great place to start.

Bruce and Rachel talks about HTML5 and CSS3

Unsurprisingly this years @Media will be focusing on HTML5 and CSS3 with a number of great talks including ones from both Rachel Andrew and Bruce Lawson.

Without a doubt these are really hot topics and open up a world of possibilities for us as web designers.

Of course this is also a topic that has been done to death online. However because there is so much material it can be hard to know where to start. That is why being able to see a presentation from the likes of Rachel or Bruce is invaluable.

That said, there is some material out there worth checking out.

When most people think of CSS3 they think of border-radius, gradients and shadows. There are literally hundreds of articles dedicated to this subject. However there are also a couple of tools for those of you who cannot face yet another blog post.

The first is a simple tool for generating border-radius code. Simply type in the values for each corner and it creates the code for Mozilla, Webkit and the W3C spec.

The second tool does a similar job for gradients, box shadow, text shadow and transforms.

A tool for creating advanced CSS3 effects

However, CSS3 isn’t just about new effects. As Rachel Andrew points out in her 24 Ways article it can also help you create cleaner code.

As for HTML5, I have seen Bruce talk about coding in HTML5 before and it is well worth watching. He demonstrates just how easy it is to start coding HTML5 today even though the spec is not fully supported across all browsers.

Bruce has written extensively on the subject of HTML5 as a quick Google will testify. However I recommend you check out his website html5doctor and a previous presentation he gave that introduces HTML5. Both provide a great starting point.

Inclusive design

The final talk I wanted to highlight is Inclusive Design by Sandi Wassmer.

Inclusive design is not a term I have come across before, which is why this talk interests me. However according to Sandi it brings together Accessibility, Usability, User Centric Design, Progressive Enhancement and User Experience. It recognises that a ‘one size fits all’ approach is not always appropriate and that we need to provide users with more choice in how they interact with our content.

I get the impression Sandi chooses to talk about inclusive design rather than accessibility because accessibility is so strongly associated with the disabled and in particular those who use screen readers.

In fact accessibility is a much broader subject that includes accessibility for all, even those who still use IE6!

Sandi has actually created a very interesting PDF on the subject of inclusive design that is worth downloading. It will certainly get you thinking in a different way about what it means to make your website accessible.

Adapting to accessibility

Is it time for us to take a fresh look at the subject of accessibility? Phil Powell offers some thoughtful insights into how we might make the web a more accessible place – not just for those who are disabled, but for everybody.

Let me get this out of the way at the start: I’m a disabled web user, registered as severely sight impaired. I’m also a web designer and developer – have been for over 10 years. I’m not just a tinkerer: I’ve worked for the likes of Audi, Levi’s, Adidas and even won a few awards for my work with U2.

In the early days, like many of us, I didn’t take issues of accessibility as seriously as I ought to have done (I committed my fair share of usability sins and implemented some really bad design decisions). But, I saw the error of my ways, and nowadays I’m a loud advocate for good standards and better accessibility. And, as both a disabled web user and a web practitioner, I think I have some useful insights to offer on how we might make the web a more accessible place, not just for those who are disabled, but for everybody.

We’ve come a long way

There have been fantastic advances in improving access to the web over the past ten years or so. The wider adoption of web standards by both browser vendors and web practitioners has bought huge benefits to all types of disabled users. These advances have helped to inform trends in web design and development in a myriad of positive ways.

Personally, I’m finding that my web experience is steadily improving thanks to these adoptions, which is a fantastic thing. There is still some way for us to go though. I still occasionally stumble across high-traffic sites which are terribly inaccessible: code soup which makes a site unintelligible to screen readers; design treatments which bewilder anybody with learning difficulties; tiny hit areas which make for horrible target practice amongst those with motor disabilities. These aren’t old, creaking relics of a by-gone cyber-era either: they are new, high-profile commissions.

http://www.artscouncil.org.uk/

Sure, not everybody is signed up to web standards, nor is every web designer or developer experienced enough to appreciate the importance of accessibility. But from my experience, it seems that public sector and cultural organisations are the ones who are failing the most. This always baffles me a little, as you’d expect publicly-focused bodies to have a commitment (and in many cases be required) to ensure accessibility to all. Ignoring disabled members of society in the physical world is wholly unacceptable, so why do we still tolerate it in our virtual world?

The fact is that not every disability is the same, and the acuteness and intricacies of a disability can affect people in so many varying ways.

Well, part of the reason, I think, is due to a slightly skewed way we think about disability. It is easy to fall into the trap of thinking of someone with a disability as part of a generalised group: someone who is blind, who is deaf, who is a wheelchair user. The fact is that not every disability is the same, and the acuteness and intricacies of a disability can affect people in so many varying ways. This misconception makes it a complex and confusing subject to understand, especially for people with deadlines.

But I think there’s something else we need to address.

There’s a bigger problem

Our industry isn’t innovating enough. We’re simply not being intelligent enough with our design of the web.

Now, that reads as quite a bold assertion, so I’ll try to explain where I’m coming from.

I’m a firm believer that good design should be both beautiful in it’s aesthetics and in the way it functions. But it seems that a lot of the time, when it comes to designing for the web, aesthetics and functionality are treated as two very separate disciplines. I’m generalising, but I’ll bet that the approach to the design of most web projects is still either: a great visual style which needs to function well; or a functional architecture which needs to look good. One generally informs the other.

I’d like to see the wider adoption of a new, emerging type of web design, where style and function are embraced as a single, integrated discipline. Gone are the days where a designer’s job stops when they hand over a Photoshop mockup to a site builder. And similarly, gone are the days when site builders try to design in the browser and then a visual style is conjured up around markup. Both of these approaches have their benefits, but equally, both have their failings. Can we not be a bit more inventive?

Accessibility can be beautiful

I think this is where accessibility could step in. I think accessibility can be a killer tool for some amazing design. But it needs us to look at it in a new way. As much as any of us claim to take it seriously, how often do we think about how it can be done better? The tendency is to just tick the boxes and then move on to another pressing task.

Rather than being a secondary consideration in the design and build of our web experiences, we can better use the disciplines of accessibility and usability as tools to inform and inspire beautiful aesthetics and functional design.

Accessibility should be embraced as a way to allow us all to adapt our online experience to fit the way we use the web.

Good accessibility doesn’t just have to be something which assists people with a disability. We need to flip that idea on it’s head. Accessibility should be embraced as a way to allow us all to adapt our online experience to fit the way we use the web – disability or no disability. Better access to the places we visit on the web doesn’t just benefit people who are disabled, it benefits everyone.

We’re already heading there

Apple are a rare example of a company who take good design seriously and who are already doing amazing things in this field, albeit with installed software.

I have very low vision due to a rare form of albinism. My distance sight is really bad; I wouldn’t be able to recognise your face across a room. But my near vision is exceptionally good; I excel when working with pixels and detail. I predominantly do most of my work on OS X because it has so many low-level accessibility aids built right in: I can zoom the screen with keyboard shortcuts; well-adopted UI guidelines make it easy for me to understand a new app; standard controls and focus help me to navigate without a mouse; finding files, running applications and searching can all be done swiftly and easily using the keyboard.

http://www.apple.com/uk/iphone/iphone-3gs/accessibility.html

I adopted an iPhone for the very same reasons: not because I’m an Apple fanboy, but because it brings with it the same accessible features as my operating system, features I’ve struggled to find in any other mobile device.

For me, these are amazing productivity tools. I tend to work faster and with more efficiency than my well-sighted peers, and that’s purely down to my use of accessible tools. I’ve adapted my working world to not only achieve an equal footing, but my adaption allows me to be more productive than many able people.

But these enhancements haven’t been developed for the sole use of people with a disability. They are elements of good, well-considered design, beautiful in both aesthetics and function, which are available to all. Try it right now: if you’re using a fairly modern version of Safari, hit CMD-F, then start typing a word, and you’ll see a perfect example of what I mean. If you’re using another browser, chances are you’re missing out on the advantages of a piece of simple, but clever, assistive design.

Example of CMD-F functionality in Safari

A subtle, but important distinction

Assistive accessibility means providing add-on tools which help people. My local Co-op print braille labels on their wine bottles: a nice bit of assistive design which helps us visually impaired lot choose our tipple. A worthy amount of effort goes into the transcription of subtitles and closed captions for TV programmes and DVDs: a service many of us don’t use, but which is an invaluable assistive tool for the hard of hearing (and incidentally a tool which is only now appearing as a feature in mainstream online video services).

Adaptive accessibility is about building things into our everyday world which aren’t used by everybody all of the time, but are available as a helper to everybody all of the time. It can be something as simple as a handrail on a stairwell: the more sprightly among us may bound up stairs two-at-a-time; those who are more elderly need the extra support; sometimes children use it; if you’re tired, lazy, carrying something heavy you might use it. You adapt your behaviour through use of the tools around you, depending on all sorts of factors.

I see no reason why this analogy can’t be translated into our experience of our online world. We’re moving away from the desktop, to devices in our pockets, on our laps, in our cars. We can go online virtually anywhere, with different distractions; different demands for our attention. We’re moving away from navigating with the keyboard and mouse, to using touch, gesture, using our voices, using our ears. This might come as a surprise to you, but us “disabled” lot are way ahead of the game when it comes to alternative ways to navigate the online world.

I don’t have any answers

http://standardinterface.org

So how do we start building more adaptive online experiences?

I do not have a simple answer as to how we achieve this, I’m merely posing the question and acting as an advocate for the discussion of ideas. Perhaps it involves rationalising the UI design of the web (the adoption of iPhone design conventions shows an early example of what this might mean); perhaps it means decoupling data and presentation even more than we already have, and looking at a more ubiquitous approach to design; perhaps it means we’ll see the emergence of new creative workflows, and a new breed of designer (there are plenty of “creative technologists” emerging who fit the mould). Perhaps we’ll invent new tools, services and devices which change the way we experience, and perceive, the web.

Or perhaps we’ll just keep plodding on for the next ten years, pontificating and prevaricating, waiting year on year for the ratification of standards, stifling our creativity, innovating by increments, never really being progressive, never being bold. History has taught us that freedom and inclusion can reap huge rewards for all members of our society. The world wide web has shown us an inkling of it’s potential. But unless we take a good, hard look at one of it’s core principles: access for all – then that potential may not have a chance to blossom.

If you recognise that the mobile web is important and you need help deciding on a strategy, then book a mobile consultancy clinic.

Book a consultancy clinic or contact Rob about a more in-depth review.

Running a successful web design agency

Mike and Keir from Carsonified interview Marcus and Paul on how they have made Headscape the successful web design agency it is today.

Keir: Okay, hi Paul

Paul: Hello!

Keir: Thanks for joining us.

Paul: That’s alright!

Keir: Thanks for agreeing to let us turn the tables.

Paul: Are we not saying hello to Marcus?

Keir: Oh sorry, hello Marcus!

Paul: He’s refusing to talk now!

Marcus: Hello!

Keir: So we’ll ease you guys in gently, first of all to you Paul, obviously now your company has grown big and strong and you’ve moved on really from being a web designer / builder…

Marcus: I want to see where this is going!

Paul: You’re going to ask me what my job is aren’t you?!

Keir: No! I’m not going to ask that I’m just going to ask do you miss doing that, being hands on, that sort of thing?

Paul: I have moments of it, yeah. Because I’m somebody who has a short attention span, and I like skipping from thing to thing, I felt like I’d reached a point where when I was designing, all my designs were looking the same. Which was an indication that…

Keir: I think Marcus is nodding for some reason Paul..!

Paul: That my designs all look the same?! So that to me was the part where I had to start moving on and doing different things. But no, I dabble still, I do Boagworld, I do Headscape, but yeah, I do miss it sometimes.

Headscape website

Keir: On the same subject, do you find it hard to relinquish that control at all?

Marcus: No!

Paul: (Laughs) No! Not at all!

Marcus: Sorry I was answering for Paul!

Paul: And I think you’re correct! No, I have certain standards that I think we should keep to as a company in terms of quality of code, that kind of thing. But the guys at Headscape are very good. So it’s often semantic arguments that we have rather than anything of value! In terms of design I have to battle against the fact that I have personal preferences in that I have a design style…you have a design style. When you’re working with a designer, not everybody at Headscape produces design that is in line with my personal aesthetic, and it should be that way because you want a broad range of stuff, but sometimes I struggle to recognise that this is a good piece of design, it’s just not what I like.

Keir: Is there not a Headscape aesthetic, a little bit?

Paul: I think there is to some degree, we pretend there isn’t and we tell our clients there isn’t, but I think there probably is, and I think that’s largely come about (a) because of my own personal bias, but (b) because of the type of clients we work with. With the majority of clients we work with we would be laughed out of the room if we did the kind of stuff you do.

Marcus: That’s a bit harsh! Bloody Hell!

Paul: I’m not saying its bad! It’s great design!

Keir: I think a nice big pumping heart on the homepage of Headscape? That would go down a treat Paul!

Paul: And I know that Mike can do that kind of design.

Marcus: We’ve been talking Mike up a lot lately.

Paul: I know!

Marcus: We’ll have to start interviewing you now!

Keir: Right, back to the questions!

Marcus: As an inspiration for the guys at Headscape to maybe go down a different route, and your work is very inspirational from that point of view. They all say ‘Ooo Yeah, we like a bit of that!’

Keir: That’s nice to know!

Paul: They need to have opportunities to break out from the constraints and the boxes that they’re put in because of the type of clients that we work for.

Keir: So that raises an interesting question, how do you deal with that internally when someone comes and the brief maybe doesn’t quite need a new avenue to go down – how do you hold a designer back from experimenting, do you suggest other outlets internally?

Paul: To be entirely frank with you, our problem at the moment is the other way round, that our designers self-censor themselves, because they work on so many of these kinds of sites, and they predict what the client is going to say and so hold back sometimes.

Keir: And are they normally right or is there room for expression?

Paul: Yeah, they are normally right, but that’s not the point. I see it as our job to push the client. I mean there’s a classic example, I won’t name the client but there was one recently that said they wanted something ‘different’ and ‘radical’ and so we said ‘are you sure?’, and then we did all this cool stuff for them and then they said ‘could we tone it back?’ and so I turned round and said ‘you wanted something radical?’ to which they responded ‘Yeah, we didn’t really did we?!’ (Laughs)

Keir: So what do you see as the hot topics, or is there anything in the web world right now that really excites you? Or even you Marcus?

Paul: (Pauses, sighs) No. No!

Marcus: I’m much more business oriented, so things that excite me are…

Paul: Spreadsheets?!

Marcus: No, no… God no! Because we’ve been doing this for a long time, and we were never the sort of people to say ‘in five years time we’d like to be there’ but then suddenly we find ‘Oh, we’re there!’, so then you find yourself saying ‘What now then?’ and so I’m more interested in what the new thing would be. Because I’m not a designer, I’m not a developer, so I don’t really feel it’s my job to get enthused about anything in particular, HTML5 for example. I’m like, ‘great, cool!’ Paul is much better placed to answer that question as it’s not my specialism. My specialism in this world, if I have one, is talking to people who have websites about what their website could do for them, and so to a certain extent I need to be informed, but he does that for me.

Boagworld Podcast Live

Image Source

Keir: So how do you split your work for a new client? I contact Headscape for whatever reason, we agree to meet, I give you a brief outline of what my requirements are, would I speak to you (Marcus) and what sort of stuff would you want to get out of me and then would you hand over to Paul or the Project Managers?

Marcus: It varies. If it was a really big project I’d say to someone on the phone…

Keir: Give it to someone else!

Marcus: (Emphatically) No! No! Rather than have a lengthy chat on the phone I’d say I’ll come and meet you, and it would usually just be me at that point. And for virtually all projects people will come to us with a ‘We want to do something’, not a ‘We’ve heard you guys are quite good, what can you do for us?’ 99% of the time people have a pretty specific idea that they want us to do x, y or z, so I’ll go along and talk about that, and question why they might want to do that – that’s really the big part of it actually. Why do you want to do that? How’s that going to help you? Is it going to make you more money, is it going to make people who come to your site happier?

Keir: So very much from the business angle, the benefits of having a web presence or what expanding it will do for their own business? Bottom line stuff really?

Marcus: Yeah, to a certain extent, but also that’s the kind of nice client who comes to us. Quite often what we’re doing is responding to invitations to tender, and then it’s case of a brief will come through and we will respond usually with a phone call and questions – what do you mean by this and this and this, are you sure you want to be doing that. We’ll respond with a proposal and hopefully we’ll be invited back to talk to these people, at which point I’ll wheel him out (Paul!) and he’ll enthuse at them for half an hour!

Paul: It takes me a while to latch on to the part of the project that excites me, because if you go into a pitch not excited about the project, you ain’t gonna win it.

Keir: Sure.

Paul: But once you’ve indentified that thing in it that really grabs you and you want to do then I’m away and it’s great. So I mean, I tend to go in at the pitch stage and I give the big presentation. Then we normally, if we win it, at the beginning part of the project is where I flesh out that stuff that I was enthusing about, so where we really develop and set the direction of it. I talk the client through the process, help them to focus the vision, and that’s done in conjunction with the development team, the developer, project manager, designer, all the rest of it. Once that process has been done I step back and the project manager runs with the project.

Marcus: That’s the big bit out that I do. Requirements, information architecture, stakeholder interviews, all that stuff, and then I’ll step away from it usually. Then project managers, designers and developers get on and build it.

Paul: Periodically through the project I keep my eye on it to make sure that that vision that was created at the start of the project hasn’t been lost at any stage.

Keir: Just quickly because I’m really keen to know, there’s a lot of talk in the internet about, and I hate the term, spec work. Mark and I have talked about this a lot. I’m of the opinion that doing a tender or response to a proposal could be deemed as doing spec work in some respects because by the definition you’re doing work – how much time or value and what’s the end product of that…

Marcus: Shall I tell you how I define it? I as a sales person, and I do information architecture as well and that is all paid work, but at least 50% of my role is as a sales person and sales people don’t get paid by clients.

Paul: They’re a cost of sale.

Marcus: So if it’s work that I’m doing then it’s fine, if I have to get a designer to do work as part of that document, then I don’t think that’s right

Paul: Because those are chargeable people, I’m a chargeable person.

Keir: We know that Paul!

Paul: The most that Marcus would require of me would be to bounce some ideas around in the proposal stage. The pitch obviously is free; we would go up and do that. But the way that I view it actually is that spec work in my opinion is work that you give to a client that could potentially be used in the actual project. So our proposal documents aren’t spec work….feel free to disagree

Keir: No, it’s interesting because you make it sound like you go to a pitch with nothing?

Marcus: Correct. We don’t pitch any graphics ever.

Paul: No. Never. Never any graphics.

Keir: OK, so how much work would you say goes into a pitch?

Paul: Into the pitch itself?

Keir: Not the actual time of the pitch.

Paul: OK, preparing for the pitch, well the proposal, a lot of work goes into that.

Marcus: At least a day. Usually two.

Paul: Because that, with the type of work that we do, there’s quite a lot of boilerplate in it, ‘We’re Headscape this is what we do’ but with large public sector organisations that we tender for they want to know a lot of detail like financial history, they want to know the name of your third child, but it’s not a document that necessarily contains lots of ideas.

Marcus: A good way to think about the process is – we’ve won the work, and the process usually starts off with him analysing the existing website, the brief they’ve got, talking ideas, he’ll make a bunch of recommendations out of his own mind as it were. I’ll then test that on a load of stakeholders via one to one interviews. Based on that we’ll then put together a report which pulls all that together. Then we’ll do information architecture, then we’ll do mood boards that will kick in to the actual design. And that’s a load of work that I’ve just described. If we value giving designs up front then all of that is pointless.

Paul: It’s the fact that before you make a recommendation to the client, either in terms of visuals or in terms of the direction or vision of the site, you need to understand the client, you need to understand the business and the objectives. You never get all of that from a brief. It doesn’t matter how thorough they think the brief is. So therefore our proposals are very detailed responses to the brief that has been provided. But oftentimes that not what we’ll end up delivering. Often we’ll win the work, do a lot of research work and then turn round to them and say ‘Actually what you asked for out of the gate was this, and that’s not the right thing, we need to be going in this direction.’ So the proposal document only really exists to establish our credibility and to get us to the point of actually winning the work. There’s not loads of stuff in that proposal that they could take and say ‘A-ha’ I really like these ideas I’m going to take these and go with another agency. It’s not that type of document, but with a piece of speculative design they could do that, they could say ‘A-ha’ I really like this bit of design, I’m going to take this and give it someone who is cheaper.

Marcus: To finally nail this point to the table! We see proposals and pitches, the proper response from us is to basically tell our prospective clients that we can do a really good job, and give them lots of reasons why. We think your project might be really similar to the one we did for this client. Look at all the work we did on this and this was the process we went through, with lots of pictures of what we did for that client, but no actual ‘ We might be able to do something that looks a bit like this for you.’

Keir: That’s a historical thing though because you’ve got a canon of work, you’ve got heritage. What would your advice be to young people up and coming, 18, 19 20 years of age when you’ve not got that canon, you’ve not got that history?

Paul: I would encourage them to actually do some voluntary work.

Keir: Build up the portfolio

Paul: Yeah.

Marcus: It’s the same when you’re looking for a job, we want to see your portfolio, what you’ve done before and we think clients are the same.

Paul: My attitude is, let’s take a piece of speculative design work is going to cost two days of a designers time – I’m just plucking random figures out of the air here – but you could spend two days doing speculative design work for some dodgy guy who says ‘If you do some speculative design work you’ll win the business’ – and let’s be honest, these are the kind of guys you are going to be working for when you start out – screw that for a game of soldiers, he’s just trying to get one over on you. I’d prefer to spend to the two days working for a local charity that have got no money but a really worthy cause, give them a great design that they can take away and build or do what they want with, and then I’ve got a good portfolio piece.

Marcus: That said, we used to do designs up front. We were shooting ourselves in the foot doing it.

Keir: Before we move on, I think the one thing that struck me was of your comments, and I think it was in response to a particular blog post was that spec design work was actually bad for the client, more than it is for the designer which is quite a unique perspective

Paul: I was reading some of my stuff over that because I think we have a rock solid argument. I won’t go through the whole argument now because there are other things to talk about but basically it boils down to the fact that as a designer or developer you are not well enough informed at the spec stage to produce anything other than a piece of show-off work – so all you are doing is going ‘Taa Daa!!’ look how talented we are! You are not solving any problems, you are not challenging their brief, you are literally just doing a bit of fancy work. And the reality is that if you are the client you are paying for it anyway, because we have to roll the cost of sale into the project. But here’s the killer. You’re not just paying for the piece of speculative work I’ve done for you, but you’re also paying for the speculative work I did for ‘Mike’ who turned us down., because we still have to recover the cost of time we spent doing Mike’s piece of work. So the reality is your paying for your own speculative piece of work and for other people’s speculative piece of work! Sorry, I’m pointing aggressively!

Paul Boag speaking at Future of Web Design

Keir: I’m retracting quickly!

Marcus: I’m gonna get him a box to stand on!

Paul: But I get really annoyed about it and really passionate about it. I would never hire a company that does speculative design work because I’m paying for other people’s design work! It doesn’t make sense!

Keir: Moving swiftly on! (laughs) Going back to the original question! So there’s nothing exciting going on in the world of web?

Paul: Sorry, I’m very aware we’ve gone off on a tangent! There are two levels of excitement. There’s the Silicon Valley, web app type of excitement that everybody features. The cutting-edge, we’re-some-fancy-agency-startup-with-lots-of-venture-capital. And then you go to a conference and there are large companies that are ‘dealing with scalability with over a million hits!’, and you think to yourself ‘very interesting, but no kind of impact on my life’ – but over time that sort of cool stuff tends to trickle down, and I get excited at the next tier down. I get excited when I start to see some of that really cool stuff that maybe is old hat now, that everybody was talking about a year ago or maybe two years ago, when I start seeing that appearing on average websites. Websites that the vast majority of us are working on.

Keir: Can you give an example of something that has done that for you recently?

Paul: Just this whole web application culture of Javascript driven, application-like / desktop-like, because for such a long time that was only for things like Gmail and Google Maps and stuff like that, but now that’s all trickling down and you’re starting to see rich internet applications in boring everyday sites, whether it be a university site or you know, Sussex Police! Anna was telling me about a Police website where is you hear a police helicopter flying over you at night you can look it up the next day and find out why it was there and what it was doing! And all of those Web 2.0 things about openness and transparency as well as some of the technology stuff like AJAX, all of that stuff is now becoming mainstream. And I get excited when fringe stuff becomes mainstream, and the bigger community of developers outside of ‘The Valley’ all start doing it. That’s why I get excited about the web, and that’s why I get excited about stuff that everybody else was excited about a year or two years ago!

Mike: We wanted to move on to the subject of blogging. As a company I believe you don’t blog?

Paul: Not as a company no.

Mike: So you blog as Boagworld, but recently we’ve been intrigued to see you’ve been blogging more personally on Posterous so really we’re trying to work out, is Boagworld purely on the education side and those on your micro-blog are more personal? We were particularly struck by one article – what was the title? ‘The Idea of Personal Brands Stinks’, you use AudioBoo, you have a lot of outlets, how do you decide what goes where?

Paul: You’re making a fundamental mistake here!

Paul: I make many Paul!

Paul: The fundamental mistake you’re making is that you’re presuming that I have a strategy! Which I really really don’t!

Mike: The question should have been, what do you get out of blogging professionally and personally?

Paul: I’ve never been so professionally interviewed!

Keir: Apparently Anna can cut stuff out! It’s apparent that you might get work out of your blogging, I don’t know, but you obviously get more out of it than just that?

Paul: OK! Let me see if I can find a question in there somewhere!

Keir: We don’t do this for a living you know!

Paul: There’s a few things to comment on. First of all, without a doubt, blogging is a major marketing tool for Headscape. The vast majority of our new business comes in via that. It is definitely and categorically a business tool. But it didn’t start out that way. When I started out blogging, it was a little bit of ego – we went to @media 2005 and they got different bloggers to stand up and I thought ‘I want to be like that!’ so I get very inspired and I started blogging partly because of that. But I quickly realised no-one was interested in what I was writing at the time so the blog for me became this place where I could take what I was learning and picking up and rationalise it in a way that made sense to me. So it became a way of me wrapping me head around everything that was going on. It was also a way for me to be storing and holding the stuff I was learning because my memory is horrendous and to this day I find myself saying ‘I’m sure I’ve written something on that’ and I go onto my blog and it’s a way for me to remember. I know it sounds stupid but I really do this, and so I’ll read through my blog and say ‘OK, so that’s what I’m supposed to think about this!’ But it really helps to clarify my thinking – so that was a big part of it. But Boagworld, the domain was bought and I thought I’d write a bit about web design, it was my personal website, and as I wrote more about web design as my head was buzzing with that at the time as this was the time of Web Standards and we were getting into accessibility. And then other people started to take an interest in it and it grew and grew – and then we started the podcast which really came out of the fact that (a) I’d got an iPod for Christmas that was just about beginning to support podcasts, and so I looked for a web design one and there wasn’t one so I thought ‘I’ll do that’ because it’s easier than writing one and I’m crap at writing.

Marcus: (Shyly) Hello, it’s Paul, this is the first ever podcast!

Paul: (Laughs) Which is pretty much what it sounded like!!! It’s like stepping back in time listening to those early ones.

Keir: How long ago was that Paul?

Paul: 2005/2006? I’ll have to have a look. No, it must have been 2005. It was growing, it was building momentum until it eventually became this thing of it’s own. It was beginning to have marketing benefits and I was beginning to spend some of my work time doing this. So relatively recently I came to this realisation that Headscape had robbed me of my blog! Which I’m quite happy with as it’s turned into this great marketing tool which is fun to do and I love it. But I had nowhere to share, I dunno, a silly video of James or some cool thing that was nothing to do with web design or whatever else. So that’s where Posterous came from. It was just an easy way for me to talk about something that wasn’t web design. Occasionally bits of web design get in there – I’ll tell you my dirty little secret for this one, which is that often, if there’s an idea I’ve had, I’m too lazy to write a blog post about it, I’ll record a video. But I won’t put the video onto Boagworld as there’s an expectation that I’ll have a transcript of it to make it accessible, and so I just put it on Posterous to get around it which is really naughty and I should be ashamed of myself! But I do occasionally do that. But most of the time Posterous is just about me having fun. Then you get into things like AudioBoo – AudioBoo is my idea of micro-podcasting, like Twitter is micro-blogging. So it’s little snippets of tips and advice. So, how do I decide what goes on where?

Keir: You’re interviewing yourself now!

Mike: Let’s go and get some coffee! Marcus?

Paul: So basically, if it’s not good enough and not long enough to be a blog post, it’ll become and AudioBoo, that’s if it’s about web design. If it’s about web design and it’s too long for an AudioBoo, it’ll become a blog post. If it’s not about web design, it’s Posterous.

Keir: So you do have a strategy!?

Paul: But where it falls down is where I’ll do a little AudioBoo about something which is the beginning of a thought, then it ends up as a blog post and then it ends up on the podcast as well. So it kind of ripples through.

Keir: That’s cool – it’s interesting to know all that but what I’d personally like to know is what makes you want to share such personal stuff sometimes? I know you’re a Christian and you talk about God, but you also talk about some other personal stuff sometimes too? What is it in you that makes you want to do that?

Paul: I think it’s two things. It’s two major parts of my personality. One is that I am a massive extravert, I’m a massive show-off – I’m never happier than when I’ve got a massive audience. To be entirely frank, you know!

Keir: Had anyone spotted that?!

Paul: Unlike Marcus I can’t sing or play a musical instrument! The best I can do is jump up and down, wave my hands in the air and say ‘Look at Me!’ So there’s that aspect to it. I think there’s another aspect to it. Somebody said to me right when I was a young kid, they said Paul, the thing about you is that you live with your heart on your sleeve, what you see is what you get. And I still think I’m like that now. I’m a very open person. If I’m grumpy everyone knows I’m grumpy, if I’m happy everybody knows I’m happy. I live my life in the open and always have. So I do that online, because I’m not a different person online than I am offline, and I know a lot of people are, but I don’t choose to be that.

Keir: Thanks Paul, that’s a nice explanation.

Mike: OK, one of the questions we have is about honesty and speaking and blogging. Do you ever…

Paul: I make up stuff all the time!

Mike: But it’s very hard I think to always be honest, in all spheres of life. Do you feel you are always as honest as you are?

Paul: Does this go back to the conversation we were having previously Mike?

Mike: It does yeah.

Paul: Because we had this conversation, me and Mike about when you stand on the stage, and sometimes you get off after a presentation and sometimes you go ‘Why did I say that?’ and you think, ‘I said that because I think that’s what people expected me to say’ rather than what I was actually thinking. I mean you gave the example about where you gave a talk about sketching where you said ‘Get away from your computer and start sketching’ when that’s not actually what he does. (Laughs) Well it was either a case of share an example where I had done that and I would rather humiliate you than me!

Mike: Yeah, I wanna reverse that! Anna can apparently cut things out.

Paul: No, no, no editing. We tell people that but it’s a lie! And I’ve done similar things, I’ll be honest. For me where the line comes with honesty is, I don’t think there’s anything wrong with saying ‘I think this is the way it should be’ – but where you fall down and it gets a bit shady is where you say ‘I think this is the way it should be’ but fail to mention that you’re actually there yet, we’re heading in that direction. And I’ve made that mistake too. But I do try and be transparently honest – I don’t try and dress up anything that I talk about, and in fact I’m probably a bit self-deprecating actually. Actually I think a lot of people think I’m a bit of a joker and a bit of a moron. But I do like to simplify things and I do like to take the mystery out of things – I think there are a lot of people, and this goes back to our conversation, I think there are a lot of people making out like their job is a lot fancier, a lot harder than it actually is – and we do like to justify our own existence by using lots of clever words., and having ‘processes’ and ‘methodologies’ and ‘systems.’

Mike: Cool, thanks, that’s interesting. So coming on to status, how important do you think status is in the industry?

Paul: OK, well I’m glad you worded that question the way you did, as I was worried that you were going to word it ‘How important is status is to you?’, and you’d purposely put the question of honesty beforehand! (Laughs)

Keir: We were going to ask ‘How big is your ego?’ but then we’ve scribbled that out! But this also comes off the back of your article about personal branding; the idea of web celebrity, a lot of people would refer to you as one of those.

Paul: I’m going to be entirely honest about this right – which I don’t think a lot of people are. Yes, I love it.

All: (Laughs)

Paul: Of course I love it! Of course you’re going to love it when someone comes up to you and says ‘You’re Paul Boag aren’t you, I really love what you do!’ and anyone who pretends that they don’t like being praised is a liar.

Marcus: I’ve got quite a funny story actually. I went to the Comedy Store in Leicester Square last Friday evening, and we got there and sat in our seats, and there was this young couple, both of them in their early twenties came and sat down next to us for the first half. And I kept seeing this guy look at me, and I thought ‘He’s recognised me!’

All: (Laughs)

Marcus: Nothing was said! Interval comes, I get another beer and sit back down. And he said, ‘I think I know who you are’ and I was like…you’ve got it wrong!

Keir: You’re Paul Boag!

Marcus: But supporting what Paul’s saying, I get recognised at conferences. ‘Say something’ that’s what they always say.

Paul: Yeah!

Marcus: Especially Americans!

Marcus: So I said to one guy, ‘You’re a web designer are you?’ and he said ‘No, I think my Mum’s got one of your records!’

All: (Laughs)

Marcus: It’s gone full circle now. If it’s someone young I expect them to recognise me from the podcast.

Mike: Didn’t your daughter’s friend come up and say she knew you from the podcast?

Marcus: Yes, yes, it still amazes me, because I just pitch up once a week and try and make it look stupid!

Keir: What band were you in again?

Marcus: A band called ‘Breathe’

Keir: And now it’s ‘Stroke the Toad?’

Marcus: Now it’s Stroke the Toad.

Paul: Yeah, to say you don’t like that, I mean, I was at Thorpe Park recently with my youth group and we were queuing up and some guy came up to me and said ‘Are you Paul Boag?!’ and my youth group were wetting themselves, they thought it was hilarious! And yeah I like it, course I do! And people are really kind, they’re really nice about it – but you gotta keep it in perspective right? You know, I’m a niche of a niche of a niche of a niche. I might aspire to be Leo Laporte, and Leo Laporte might aspire to be a daytime TV presenter who aspires to be I dunno, a mainstream TV presenter who aspires to be a film thing and so it goes on. And it’s the whole premise – and I reject the premise – but it’s the premise that because you’re well known, and because a lot of people have heard of you, that in some way your life is of more value. And I think that’s the point I was trying to get across in the personal branding thing. There’s this friend of mine I grew up with who got married to this Indian guy, and she works out in India – we actually raised money for her on the podcast over Christmas – and runs an orphanage out there with a couple of hundred kids who have had their lives ruined. She does more good in a single day than I will do in my lifetime. And OK no-one knows about here, and no-one is interested in her, and I get people come up to me on the Tube?? And that’s ridiculous to me! And that’s what made me angry and that’s what made me want to do that post. And then it all gets out of proportion and it all gets silly. Where in our culture – sorry this is all getting a bit heavy! – where in our culture did we get to a point where Kevin Rose can’t stand in a blimmin’ party without being mobbed by people? You know, that’s weird? There’s something screwed up there.

Marcus: That’s not weird? That’s normal?!

Keir: I guess celebrity is changing? When I grew up fame was the pop stars, the rock stars and now you’ve got tech celebrities.

Marcus: If they had a rock star in that room they would get even more mobbed, but it still happens.

Paul: Just because it’s normal doesn’t make it not weird. Just because it’s been going on for a hundred years, doesn’t make it not weird.

Marcus: I’d say it’s human nature.

Paul: Yeah, and I’m saying human nature sucks!

Marcus: Well deal with it!

Keir: OK, so it has some benefits to you, but it is important?

Paul: In the industry?

Marcus: I’ve been thinking about this. Who’s the most famous web celeb? Zeldman maybe? People with big web projects and big budgets go to Happy Cog because of Zeldman’s celebrity. Not only that – he wouldn’t be famous if he didn’t know his stuff and talked well etc etc.

Paul: The sad fact is there are designers and developers and agencies out there that are as good as Happy Cog.

Marcus: Course there are.

Paul: And there are certainly ones that are better than us. But they don’t get the exposure because they are introverted people. It makes me sad but that’s the reality.

Keir: You actually said the other day in your video…

Paul: Oh don’t quote me back! I’m going to have to contradict myself!

Keir: You said the other day that you could be introverted and be just as successful.

Paul: Yeah, I think you can, but in a different way.

Marcus: What, in a non-successful way?! You can be as good a designer, as good a developer without being famous, but if you’re trying to win business using the Zeldman / Happy Cog argument then you’re going to be a lot better off if you’re somebody who’s known.

Paul: Yeah, but you could still be known and be an introvert. It’s indentifying the methods by which you’re known. For example, Rachel Andrew. Until relatively recently she didn’t do a huge amount of public speaking, and even now doesn’t do massive amounts. But she’s written book after book after book after book. She’s known for that writing and that has given her the profile. You could be an introvert and blog, and have one of the best blogs in the world. You could be submitting gorgeous designs to CSS galleries and be winning work that way. So it doesn’t need to be by being mouthy and extrovert.

Keir: The funny thing is there are agencies out there that are as good as each other – some might win work because of their public persona, and then there are those who win work because they constantly put out a really high standard of work.

Marcus: There are others that might win work because they have a really pushy salesman! It’s just another way of marketing yourself or your company.

Paul: To be honest, look at yourself Mike. OK, you’ve done a couple of speaking slots, but you haven’t spoken a huge amount. But your work has been picked up by people, and people have gone ‘Wow, I really like that’ and that’s spread virally without you jumping up and down like I do going ‘Look at Me!’ So it’s perfectly possible, it’s just a different way of doing it.

Keir: Another question that’s worth asking is that a lot of people have become well down for their niche – recently you’ve been talking a lot about educating clients, Mike has talked a lot about creativity and where he gets ideas from., they tend to be offline. Andy Clarke talks a lot about progressive CSS, CSS3 that sort of thing, for someone who is looking to get their face known in the industry is that something they should do? Find something they’re really interested in and just push it out?

Paul: Absolutely. I remember much nearer the beginning I’d built up a popular podcast that a lot of people listened to and were passionate about. But I couldn’t get speaking opportunities. And I think it was Ryan actually, who was honest enough to talk to me about it and it was his response that was ‘I don’t know what it is that you do?’ – a lot of people don’t know what it is I do! But

Keir: That’s a whole other interview Paul!

Paul: He didn’t know what box to put me in. People like putting other people in boxes.

Mike: It makes picking speakers easy to be honest.

Paul: So you can go, ‘We need someone in this slot who’s going to talk about business’ or ‘development’ or whatever else. I packaged myself very specifically for conferences and speaker opportunities, I will talk about this kind of stuff. Once you’ve done it once, that’s it. But, the problem is you can’t do that forever. You need to re-invent yourself. Jeremy Keith is very good at that. He started off as the DOM scripting guy, then he became the microformats guy, now he’s the HTML5 guy. He knows how to move from thing to thing. He would say that his interests change and he moves on, it might be, it might be a totally subconscious thing, but it’s a damn clever thing, however you slice it.

Marcus: I would argue that this applies to life, not just web design. I’ve got quite big kids now, and I’ve been saying to them for years now relating this to subjects that they are studying, do what you like doing, not what you think you ought to be doing. It applies across the board. If you can do something well, you are going to enjoy doing it.

Keir: Yeah, that will come out when you speak about it, in the passion.

Paul: OK?! Finished with us?!

Marcus: You’ve got a whole podcast here! At least 45 minutes!

Paul: OK, well thanks very much for listening to Boagworld, we’ll see you again next week!

Keir: Thanks a lot!

Thanks goes to Andy Wickes for transcribing this interview.

The wonder of the web

A few thoughts on why I think the web is truly amazing.

I am now officially on holiday for a week. However before I leave the web behind to enjoy the sun and culture of southern France, I wanted to write a quick self indulgent post.

Its easy to become jaded in our industry. We work with the web day in and day out. Its easy to take it for granted or even see it as a burden. We complain about always being connected and the challenges of a 24/7 world. However, from time to time we need to stop and remember what an amazing thing the web is.

The web is a truly remarkable innovation. As significant as the printing press and as culture changing as the renaissance. It is scary to think that most of those in the youth group I run have grown up with the web. They cannot remember life before it. Soon the time will come when we will all take this amazing achievement for granted.

Before that happens I want to catalogue why I think the web is so wonderful…

It is accessible by all

Yes, we can argue that it could be more accessible. Yes, there is a digital divide between those with connectivity and those without. Yes, it is not perfect. But remember it is a hell of a lot better than we have known in most of human history.

Back in 1995 I used to run a virtual community. It was the early days of the web and this community was small and very close. What struck me most about that community is the large number of house bound individuals who were apart of it. For them it was the only regular human interaction they got. I remember one lady in particular called Chrystal. She was extremely ill and dying of Cancer. However, the web gave her an opportunity to have a social life. Even when she could not get out of bed, we still chatted regularly and she became a valuable member of the group. In fact she was able to dedicate far more time to the community because of her condition.

The web sweeps away many traditional areas of discrimination. On the web you don’t know if somebody is deaf, wheel chair bound or even of a different race. It equalises and although not perfect, it points to a better world.

Anybody can contribute

Web designers complain about the horrible quality of many website. You may have even looked at the link above to my youth group and tutted at the terrible code. However, for me that is the glory of the web.

I built that youth group website using iweb in under 1 hour. Anybody could have done it. No technical skill was required. For me that is amazing.

We now live in a world where anybody can publish and be heard. A world where the barrier to entry is near zero and you no longer need a printing press, TV broadcast network or radio station.

Again, the web equalises. The fact that the boagworld podcast can beat a BBC podcast in the .net awards, shows that the world has changed. The fact that two guys with a couple of mics and dodgy audio can put out content of value is a good thing. Power shifts from the few to the many.

It has the sum of all knowledge

How did we survive before the Internet? Remember the days when you went to the library and looked in a massive set of encyclopedias when you wanted to know a certain fact. Much information you simply couldn’t get at all.

Now we live in a world where almost any piece of information is available to us. The web is effectively the sum of all knowledge. Admittedly finding that knowledge can be challenging and maybe the semantic web will help with that. However even as things stand, it is mind-blowing.

It brings people together

I have friends in every corner of the globe. Some I have met, some I probably never will. I also read blogs from people in an even greater selection of countries. The web connects us. The web turns those in other countries into real people.

Its hard to demonize a nation when you know some of its people. The web does that. It wipes away prejudice and creates a global community. To be honest I don’t feel British anymore. Sure, I live in England but I am part of a bigger community. One that ignores national barriers and political squabbles over geographical territory. Somehow borders feel pointless when you are on the web.

It caters for the long tail

There was a time when if you wanted to be a professional musician you had to sign with a major record label like Marcus did. There was no way you could support yourself financially without that machine behind you. Not so anymore. Now we have artists like Jonathan Coulton who not only makes a living as a professional musician but do so within one tiny niche (Jonathan writes music for geeks!)

The biggest benefit this brings is one of choice. In the past the only way a record label could recover the cost of marketing an artist was to go mainstream. You had to appeal to everyone, or at least a sizable audience. This limited choice. However, we now live in a world with a low cost of production and sizable niche audiences. This means the market can support near infinite choice. If you have an interest, the chances are thousands of other people online do too.

Obviously this does not just apply to music but to pretty much anything that can be delivered electronically. There are specialist blogs, software, video or indeed pretty much anything else. We live in a world of ultimate consumer choice.

It is transforming entertainment

I have already talked about podcasting and the music industry but the transformation does not stop there. Increasingly young people are turning their back on the TV as a form of entertainment and turning instead of social websites including Facebook, YouTube and Twitter.

What I love about this is that we are becoming both consumers and producers of entertainment. People are no longer being passively spoon fed by mainstream media, eating whatever we are given. Instead we are generating our own content, our own entertainment.

In my opinion that leads to a more creative, proactive culture and that has to be a good thing.

It provides the ultimate freedom of speech

Many complain about some of the content on the web. Many of my fellow Christians tut disapprovingly at the pornography, while others campaign against the hate filled messages of white supremacists and fanatical groups.

However, for me these things are just the unfortunate consequences of a greater good the web provides – freedom of speech.

The recent coverage of the Iranian elections on Twitter prove the power of the web to ensure freedom of speech. Despite Iran’s best efforts dissidents found a way to get their message out.

Equally we in the west no longer need to rely on a small number of mainstream media outlets for our news. We can be connected directly to events as they happen. Our news no longer has to be filtered by the analysis of the news outlets. We can draw our own opinions and choose to listen to or reject less mainstream views.

Conclusions

I am very aware this post has been written with rose tinted glasses. However, that is intentionally so. I am fed up with the constant criticism the web receives. Whether it is as a hide out for child molesters or a communication network for terrorists, the publicity around the web is so often negative. For once I wanted to read something positive and as I couldn’t find anything so I wrote it myself!

Web Design Wisdom from Twitter

I asked my twitter followers for their web design words of wisdom. I had over 200 responses. Here are some of the lessons learnt.

I am a lazy guy and Twitter is the perfect tool for people like me. Rather than go to all the effort of searching for an answer on Google, I often find myself turning to the Twitterverse. After all, some of the brightest minds on the web use Twitter and I can get an answer faster from them than looking it up myself.

However, with this article I am taking laziness to a whole new level. Instead of carefully considering my own words of wisdom regarding web design, I have turned to Twitter…

I am writing a post on web design words of wisdom - think 'confusus says'. Post yours to Twitter in 140 characters or less. #webwisdom

Setting aside the people who wanted to point out that I cannot spell confucius, the responses was amazing. Answers ranged from the silly to the surreal. However, there were also some real gems and a number of recurring themes. What follows is a summary of the main recommendations.

Focus on the user

There was a general consensus that maintaining focus on the needs of users, was a crucial component in a successful website.

Dan Goodwin put it best when he wrote…

If you can’t work with your users, talk to them. If you can’t talk to them, at least think about them.

A number of users recommended Steve Krug’s book “Don’t Make Me Think”. However, the irony of one particular tweet made me smile…

Confucius says “Don’t Make Me Think”.

There was also a lot of advice about the importance of providing adequate signposting for users as they navigate your site. Colin McCormick wrote…

When leading a user make sure they always know where they are, how to leave and how to continue.

The issue of users becoming lost and confused also led to a call for simplicity.

Keep it simple

A number of contributors spoke about the importance of keeping our sites simple and intuitive. Niki Brown encapsulated this attitude when he wrote…

Keep it simple… the average user tends to get confused with massively complicated interfaces.

It is certainly true that many damage their sites by continually adding features and content, when they should be simplifying. However, according to some of our twitterers that is easier said than done. One wrote…

Simplicity is the most complex achievement.

While another indicated that the ability to create simple sites only comes with experience

As you become a better designer, your designs become simpler.

There is no doubt that simplifying a website can be challenging. However as I explain in “The Three Secrets of Simplicity“, if you challenge the need for new features it is possible. Too many web projects experience scope creep that undermines simplicity. That is where having a clearly defined brief comes in.

Clearly defining the scope

Too many web projects lack clear boundaries. Often they are wishlists of functionality that have not been fully considered. As Rich Wells points out, the first step is to define the problem…

When planning a site it’s always worth asking “what problem am I trying to solve?” before looking at functionality/solutions.

The trouble is that many of us are seduced by some new piece of web functionality and forget that our websites should primarily be about fufilling business objectives. As Marc Hindley points out…

Think business first, technology second.

Of course defining the scope of a project should not just be the role of the client. The web designer has a responsibility too. As Wendy Phillips explains…

Clients think they know what they want until you ask the right questions.

It is down to the web designer to ask the right questions. In order to do that they need to understand the business. One twitterer encourages them to…

Get as much info from the client upfront as possible, even things you think aren’t that relevant – get to know their needs.

Web designers and clients should work together to define the scope of a project. The client brings their business expertise while the web designer brings their knowledge of the web. Unfortunately the role of web designer is often reduced to that of a pixel pusher.

Recognise the value of web designers

Interestingly it is not just clients who undervalue web designers. Many web designers undervalue themselves. Andy Clarke endevours to encourage fellow web designers when he writes…

You don’t get paid for the hours you work, but for the years learning your skills and craft.

However, it is not just an issue of payment. The Twitter community also encourages web designers to be willing to walk away if clients become unreasonable. Alun Rowe writes…

Don’t be afraid to say no, or to walk away if a client becomes unreasonable. It’ll only cause you pain/distress later on.

David Roessli echos Alun’s point before also going on to say…

Be clear, direct, and honest. Don’t make promises you can’t keep.

Too often web designers will say anything to win or keep a piece of work. Ultimately this is damaging to both the web designers business, and the website of their client.

Of course, this advice doesn’t apply just to designers. It is valid for developers too. That said, there was also some developer specific tweets as well.

Developers pay heed

Whether you are a front end developer or a server side coder, there was some excellent advice coming from Twitter. Our very own Craig Rowe shared one particularly pragmatic piece of advice that made me smile…

Web development is a balance between well made and made just to work.

His second tweet contained a touch of bitterness that can only come from a .net developer fed up with receiving abuse from the fanatical PHP crowd…

The backend language really doesn’t matter.

That said, there is no denying he is right.

Talking of fanatical, Mark Mcaulay put another overly enthusiastic group in their place when he wrote…

WordPress is not the solution to everything.

Of course you could just as easily replace the word WordPress with any other CMS or development platform. Nothing is a silver bullet.

There was certainly no shortage of tweets touting the benefits of various frameworks, CMS and platforms. However, there was a general principle that 29Visual summed up well…

Learn a framework or develop your own. About 90% of the Website structure can be reused. The other 10% falls on design.

You can save yourself a lot of time with the right tool. However it is not just tools that can save time. Good code can too, as Joel Drapper explains…

Code with the next developer in mind.

I think we can all remember times when we have inherited code that is impossible to read let alone understand!

Our last piece of advice for developers comes from Vicky who shares one of the nicest tweets of the lot…

Code with humility and grace – acknowledge those who are on IE6 or screen readers.

That brings us on to the subject of accessibility.

Always keep accessibility in mind

The Twitter responses I received were particularly passionate about the importance of accessibility. However as Ricky Onsman pointed out, they wanted more than just access for the disabled…

Forget disability access – go for universal access.

In particular universal access included access to those using older browsers. That said, there was realism in their expectations. Nobody expected websites to look identical in all browsers. David Randall commented…

Web sites should not look the same in every browser – it’s okay to be different.

This passion for graded browser support was encouraging. However, it was not the end of their ambitions. As Joel explained, accessibility also brings with it improved search engine placement…

If your site is accessible, it’s also search engine friendly.

Website owners are often willing to invest considerable money in things like SEO or design, but rarely in accessibility. Hopefully Joel’s words will encourage them to reconsider.

Talking of investing in design…

Lessons about design

I conclude these words of wisdom from Twitter with three pearls surrounding the development of a design. The first comes from Colin who says…

Prototype and consider other designs. Do not be narrow minded. Be prepared to throw away every design at the design stage.

This is excellent advice. Often designers become locked into a single approach too early in the development cycle and fail to experiment and seek out inspiration. Of course there is a fine line between inspiration and theft. Tom Kenny writes…

Remember, inspiration is not about copying but rather kick-starting an idea of your own.

And that takes time and lots of different ideas and approaches.

But do not fret! If you are struggling to find your inspiration remember Bruce Lawson’s words of wisdom about design…

Readers care much much much much less about your design than you do. They care about content.

Conclusions

To be honest the idea of a twitter driven post was somewhat of a whim, but the replies I received were extremely impressive. This post does not do justice to the depth and quality of responses. There were superb tweets on launching a site, reinventing the wheel, and the importance of copy. I highly encourage you to look through the entire list.

However for now I leave you with some final words of wisdom from Jonathan Snook.

Anything is possible. Its just a matter of time and money

171. Access

On this week’s show: Ryan and Paul talk to Robin Christopherson from Abilitynet about web accessibility and Dave shares Headscape’s experiences of moving to Google Apps.

Play

Download this show.

Launch our podcast player

News

Page zooming vs. text scaling

In show 169 we featured Cameron Moll’s article “Coding like its 1999“. In this post Cameron explained his decision to move from ems based sizing to pixels. He justifies this decision by citing the fact that all modern browsers have moved from text resizing to page zooming, as their primary resize tool.

Cameron’s position has caused some controversy in the web design community, with passionate responses from leading figures like Drew McLellan and Roger Johansson. Cameron’s original post also attracted some heated debate in the comments.

So why do so many object to this move away from text scaling and fluid design? Most of the arguments are the same as those that have been around for years. Fluid design…

  • Adapts to varying amounts of content and different languages.
  • Makes better use of screen real estate.
  • Puts the user in control
  • Prevents horizontal scrolling
  • Adapts to alternative devices (such as mobile)

However, Molls critics also point out that page zooming is not support by IE6.

Cameron has responded to the criticisms in “The debate over page zooming vs. text scaling.” He argues against the principle of “one site fits all,” which underpins fluid design.

In my opinion this is a question lacking a black and white answer. Although generally I share Cameron’s view, we still occasionally build fluid or ems based sites depending on the project requirements and target audience. There are good arguments on both sides and neither approach should be dismissed.

10 web design rules you can break

What the discussion over page zooming shows us is that nothing is absolute. As human beings we like black and white rules, but actually those rarely exist. The web is full of articles about web design that layout rules for design, usability, accessibility and every other aspect of running and building websites. However, in truth no such hard and fast rules can exist.

Sure, there is best practice. There are principles of design, development and management we should use whenever appropriate. However, these should not be followed blindly. Sometimes meeting business objectives or users needs involves breaking these rules and doing something different.

This week the Web Designers Depot has released “10 Web Design Rules That You Can Break“. This post looks at some of these supposed rules and shows examples of sites that have successfully ignored them. The rules they have challenged include…

  • Do Not Display the Horizontal Scroll Bar
  • Use a Minimal Number of Font Faces
  • Do Not Use Too Many Colors
  • Make Your Site’s Goal Obvious
  • Navigation Should Be Easy To Figure Out
  • Stick to Web-Safe Fonts
  • Don’t Have a Splash/Landing Page

In fact all of these ‘rules’ are actually very good advice. However, they should not be followed blindly. That is why I love this post so much. It highlights best practice, while at the same time inspiring people to challenge ‘the rules’ occasionally.

Grass roots viral marketing for ordinary people

While we are on the subject of challenging preconceptions I would like to draw your attention to a post on Sitepoint entitled “Create a Buzz: Grassroots Viral Marketing For Regular People.

I am constantly amazed at how many website owners (and even web professionals) believe that viral marketing and social media are the easy answer to their marketing needs. As the article points out viral marketing is far from easy and if you don’t have a massive twitter/facebook following it is even harder.

Although the article is essentially a guide on how to be successful in viral marketing, it does not sugar coat the realities. It points out a number of harsh truths…

  • You need a product or service that people actually care about.
  • You need to reach a major influencer to have any hope.
  • Don’t just rely on a single outlet (such as YouTube) to get your message out. You need lots of avenues of attack.
  • A lot of it is just down to luck!
I found two quotes particularly telling…
If your message doesn’t offer people something they need, something they want, or an opportunity to support something they believe in, you may need to rethink a viral campaign.
The truth about viral marketing is that many times it comes down to being in the right place at the right time.
I am extremely skeptical about the benefits of viral marketing and believe that unless you are willing to put in a lot of hard work it rarely proves successful. The perception that viral marketing is some kind of magic bullet simply isn’t true.

Information as a task

In order to prove I am not the only skeptical, cynical and despondent person on the web this week, I would like to refer you to a post by Gerry McGovern entitled “Information as a task“.

This barely disguised rant about working on large pubic sector and corporate websites, resonates with my own experiences. The heart of the article is a call to website owners to stop putting up content  unless it helps users fulfill a specific goal. Its a simple message but one often ignored.

Website owners too often start the process of deciding on content by asking “what do we want to say?” rather than “what do users want to know?” Gerry writes…

Many organizations have a strange attitude towards information. Its creation is nearly always disassociated from its use. Information is rarely seen as useful or purposeful. It’s just there because people need it. It doesn’t help you do things. It’s simply there for you to read just in case you need some information.

He goes on to write…

Organizations have a fabulous capacity to produce massive quantities of low grade, aimless, pointless information. Much of the information that should have a point is useless because it is not useable. People don’t understand it. They can’t act on it. It doesn’t result in someone completing a task.

I couldn’t agree more. Before any content is added to a website the author should always ask “what task does this help users complete?” and “is this task actually one real users will be trying to do?”

Back to top

Interview: Robin Christopherson on Accessibility

Ryan: Now here with Robin Christopherson from AbilityNet. Good Afternoon! How are you?

Robin: Yes, really good thanks, yeah!

Ryan: Fantastic! So for anyone who doesn’t know you or know what you do, could you explain that to us please?

Robin: Thank you very much. I am head of accessibility at AbilityNet and my team basically deliver consultancy and free advice and information on Web and software accessibility. And AbilityNet for people that don’t know are a charity and we do accessibility services but also assessments of disabled people in the home or in the workplace or in education and making sure they’ve got the right kit to access a computer and the Internet, etc. most effectively. And we’ve got now 800 advice information number, etc. so all things technology and all areas of disability. That’s who AbilityNet are.

Ryan: Fantastic. And you’ve just given a talk on “Designing for All in a Web 2.0 World” which was quite an eye-opening presentation I think for a lot of people who may not have seen or used a screen reader before. What was quite amusing was when you first started using it the rate at which your screen reader started speaking the content of the BBC home page, I don’t think any of us could understand it.

Stanton: I had no idea what it was saying at all.

Robin: You actually would tune in relatively quickly because when I’m working on the computer at home sometimes I don’t have it on earphones so it’s just kind of coming out through the speakers in the office and my wife just having walked past a few times now can get it so I think you probably kind of tune in. Maybe it’s a bit like the black faces and the white candlestick, you know you suddenly kind of see the other one and you kind of click. Yeah, when you’re reliant on speech output you don’t want to be sitting there twiddling your thumbs after having left the synthesizer at the default speed that you get when you install it out of the box. So you want to crank it up and not have to be waiting for it to finish what it’s saying.

Ryan: So you kind of highlight some of the issues from quite a site impairment point of view but there’s also a lot of other considerations that people designing websites should be looking into. You mentioned dyslexia or cognitive impairment. How do those type of conditions affect the way people use websites?

Robin: I think that vision impairment is probably the category of impairment that is the most difficult to cater for and someone like myself who’s got no useful vision, screen reader users are probably the hardest customers of all. A lot of the standards like ARIA for example, Accessible Rich Internet Applications, most of the guidance is around helping people who are screen reader users for example. But that’s not to say that there aren’t all the other impairment categories. Motor impairment people that have difficulties using a pointing device, a mouse or they’re keyboard only users or they’re voice-recognition users. People with a cognitive difficulty or dyslexia or with a literacy difficulty or for whom English isn’t their first language, all of these categories of impairment and obviously hearing impairment as well, have issues to do with accessing the Internet and software applications as well and the most notable ones tend to be those related to people like myself who can’t see: alternative text on images, not being able to access inaccessible Flash content and that kind of thing or Web 2.0 applications because of the inaccessibility of the JavaScript. But there is a significant impact on all those other groups. The speaker before me, Mark, was talking about typography and the choice of type, the font style is so important for people with a vision impairment, people with dyslexia, people with cognitive difficulty, etc. so Times New Roman may look absolutely gorgeous on the screen and on the page, but from an accessibility point of view, it isn’t necessarily the right choice to make for the body font. Maybe it’s fine for headings to give a certain style and because it’s a bigger font it’s going to be more legible than if you had to read a whole website, ten or eight point using Times New Roman. I wish I’d had three hours instead of half an hour to kind of go through the headline issues, right across all the different impairment categories. I had half an hour so I concentrated largely on the high profile issues to do with screen reader users and in particular Web 2.0 application type scenarios where the new guidelines like ARIA for example can make a significant impact.

Ryan: OK. What should we as, I suppose now that you mentioned typography being extremely important, what should we as designers and developers be doing to improve accessibility and day to day. I know it’s a very loaded question and there’s lots and lots of things we should be doing but as kind of a minimum we should just do all the time, every time we build a website, minimum we should be doing and then before we take the next step to really drive it home. What’s the minimum things we should be incorporating?

Robin: Um, there are some low hanging fruit. You know, there are some things that you could look at any site, any existing site and clean up: alt tags on images, and a decent heading structure, and make sure that the text resizes, that sort of thing that shouldn’t be too difficult to implement. On anything new that you’re building you really do need to get scripts with the WCAG, the Web Content Accessibility Guidelines, and the new version has come out last December to update those significantly, WCAG 2.0, and those are applicable to all the new technologies that are coming out, etc. and there’s really no shortcut to really kind of internalizing, digesting those and just letting them inform your every day practices in what you do, you know. They impact on everything from the wireframe right through to UAT and go live and also post go live maintenance and that sort of thing so you really just need to make sure you’re one of the web designers that have got with the program and you’re not doing the old bad habits of fixing everything to make it pixel perfect and doing lots of hacks to make it look OK in different browsers and that sort of thing. Luckily we’re in a much more standards compliant world now than we ever have been so you can really adhere to standards and only have to do minimal tweaks to make sure that things look relatively OK right across all the range of browsers and we’re asking that you go further still and you consider handheld devices and you consider Web TV as well as people with different impairments and that’s really going to significantly increase the customer base that you are going to be enabling to access your content and if it’s any kind of website with a business model with a revenue stream, right through to a site that’s an e-commerce site, you absolutely can’t afford to ignore accessibility in such a tough and competitive online environment.

Ryan: Yeah, especially with there was that Legal & General case which you mentioned earlier. They redesigned their website to be more accessible and had some quite good results with that, didn’t they?

Robin: Yeah, I mean this is an ancient example now. We helped the Legal & General in 2005. We did disabled user testing on the accessible relaunch and yeah, I mentioned that one in the Q&A at the end because most people will have heard of that one if any and they had staggering ROI. They had a saving of 200K per annum on site maintenance. They had an increase in online sales almost instantaneously after the relaunch of 90% and that kind of indicates that there was an audience out there that was knocking on the door before but couldn’t get through because of lack of platform compliance or lack of accessibility with the range of assistive technologies that people were using. Other people couldn’t tweak the browser to make the text size larger or impose their own color preferences. So there was an audience out there waiting and as soon as the site was relaunched and had opened the door to all those people, there was a step change in revenue. So, but there have been lots of cases since as well as cases that have shown the danger of ignoring legislation. You know, the Target case in The States where they thought it would be cheaper to be fined than to retrofit their site but when it came to it in the end they lost obviously, because they were in the wrong, and they were fined and they were also told to retrofit so they made the bad decision there and had loads of really bad PR as well. That sort of thing is going on over here but it doesn’t actually reach the court, they are settling out of court and part of that settlement is anonymity, a requirement for anonymity so we don’t have headlines over here, but there is litigation going on. So, there are the carrots and the sticks and all of those things have got to be an overwhelming case for getting with the program and becoming one of those Web developers who are able to build accessible websites which are being stipulated so often in tenders these days. You can’t work with the public sector without being able to create accessible sites and accessible functionality.

Ryan: Yeah, I work in the public sector myself as a full time developer so our baseline is it’s got to be AA compliant with WCAG2, have got to comply to the SENDA, the Special Educational Needs and Disability Act. Not so much the PAS 78 guidelines but I believe those are becoming the British standard, or are rumored to be.

Robin: Yeah, I mean it’s dragging on a bit, but it is going be sometime this year. I think probably Q3 this year and it’s going be a BSI full standard, BS 8878 and Julian and the panel including John Gooday from AbilityNet are on that again authoring panel. I think that one thing that is essential, is really important in assuring real life accessibility is testing. So, any web designer, any organization that have internal guidelines, style guides, etc. should have accessibility built in from a checkpoint or a good practices level but you also need to have a range of testing tools, whether it be the accessibility toolbar or some sort of accessibility checker. We can’t all afford an enterprise accessibility checking tool, but if you can they can be extremely useful from a monitoring point of view and ideally you’d have end users involved. So within your organization, if you’re a large organization or otherwise go externally to an organization like AbilityNet to get some end users looking at your content and making sure that it’s not only accessible to the guidelines but it’s also accessible in reality. We did some lab testing for a site that was strict AA about four months ago and 90% of the tasks weren’t completed by the testers because the AI was all over the place, the usability. None of the guidelines had been contravened but it was an extremely inaccessible site for people for a number of reasons. It’s an acknowledged fact that there are a lot of issues outside WCAG that you can’t really document that are specific to a site and the general layout and presentation of that site and the architecture, etc.

Ryan: Sure. So you mentioned testing there. Is there anything say that any of our freelance listeners that may not be able to afford a specific software, any quick and cheap kind of guerilla usability testing, that kind of stuff they can test for accessibility as well?

Robin: Ideally you’d get hold of a screen reader and become familiar with the basic level of functionality of that screen reader and just check with that. There are a number of browsing tools that can render the page similar to how a screen reader would read it out to you etc. but they’re not that useful when it comes to checking for compatibility, you know, if you’ve got a lot of JavaScript, how’s the screen reader going to handle those, etc.? There’s no easy answer to that apart from becoming familiar with the guidelines, using JavaScript from accessible JavaScript libraries where somebody has already done the work for you, and become familiar with a number of access technologies that you can use to double check some of the functionality and the content perhaps on a kind of sampling basis and you’ll begin to realize then which things are going to be problematic and that will inform your design from that point on. In Vista, voice recognition comes as standard and Windows 7 has got a full screen magnifier when that comes out so you won’t need to be purchasing a lot of different assistive technologies to be able to test with a number of them to inform your design process.

Ryan: In your presentation you talked about CAPTCHA still being a huge problem for accessibility and some visually impaired users can’t even register on a site. I also noticed that there was a kind of hidden extra link if you’re using a screen reader that nobody else really sees but you pick up on that once you go through with a screen reader. Are there any other kinds of sign posts that we should be putting into our sites like “Skip to Content” and things like that, that make it beneficial to visually impaired people or visually impaired users or people using screen readers?

Robin: I mean there will be a lot of other people as well, keyboard only users, when they gain the keyboard focus a lot of skip links become visible. People using Web TV, set top boxes often don’t fully support styles and a lot of those things become visible and they are in effect keyboard users. You can go over the top on skip links for example I’ve seen ones where there were like eight skip links and basically that’s a nav in itself, so you really need one at the top that says “Skip these skip links” or something so that is, you can kind of go overboard but yeah there are lots of little tweaks that you can do that make getting around a page, getting around sections of the page that are going to be hugely beneficial, but just doing something as simple as putting headings in, using the landmarks that ARIA offers to identify key, the top of key sections of the page are going to be hugely useful, not just for blind users for example but they are meant for a range of other user categories as well that would benefit from them.

Ryan: Could you talk a little bit about ARIA and how that’s beneficial for accessibility?

Robin: It’s relatively early days really and the support for it is pretty minimal at the moment. You have to have the very latest version of only a number of screen readers and the very latest version of Firefox, IE8 isn’t quite so good at having fully implemented ARIA support. ARIA stands for Accessible Rich Internet Applications and it’s basically the answer to the fact that WCAG, even WCAG2 hasn’t got a huge amount in there from a developing point of view. It’s more of a “Now let’s check the thing you’ve already done” point of view. But also didn’t define a standard for browser developers and AT developers, Assistive Technology developers, to interface and like an API almost and so ARIA has a number of things. Being able to define controls and their role and their status that you could never have done before in a browser. Slider controls in a media player for example a bit like in media player, Windows Media Player, but online in a, just as an embedded control in a page, that has never been possible to be made accessible before. Popup menus and that sort of thing before would have been done in styles or DHTML and that would be very problematic but with the new ARIA way of implementing them as long as you’ve got the right browser and the right AT then that is just like doing it in a desktop environment.

Ryan: One of the tips that you demonstrated on stage was for mobile devices. For the primary navigation one of the internal wars that’s always waged with me is “Should you put the navigation at the top or the bottom of the mobile page?” so that the mobile phone reads it from top to bottom every time the page loads and you showed that this site had the primary navigation in a dropdown menu.

Robin: Yeah, that’s how they chose to implement that as a dropdown and that is very cute implementation. That’s a good choice I think because you’ve got the nav there but it’s literally just one item or two items with the select button. Obviously it would be problematic if it was just a dropdown that was auto-fired for people that just arrowed down it without doing alt down arrow because that’s very a inaccessible implementation of a dropdown box but you’ve just got two items which you have to get over. If you had the nav at the bottom and you wanted to use the nav, then you’d have to get to the bottom and in some browsers there isn’t a quick way of doing that. On my mobile phone, the browser that comes with the Symbian operating system, WebKit I think, the screen reading software talks that I’ve got on my phone. I can literally just arrow left and right or up and down through items on a page, just like tab and shift-tab, that’s all I’ve got. So there’s no way of getting down to the bottom of a page to get to the nav so I would probably on balance having it at the top that in it is two items to get past. If you don’t want to interact with the nav it’s quite an elegant solution really.

Ryan: Are there any major issues with the predominance of touch user interfaces coming through now? I would think that using a mobile phone, the tactile feedback of the buttons is quite important or am I wrong?

Robin: Yeah, I mean we’re concentrating a lot of people who are completely blind but you’ve also got people with vision impairment and people with motor difficulty for whom iPhones are a non starter really so any kind of touch screen interface where it’s the entire interface, it’s not as if it’s an optional extra way of doing it. In Windows for example there’s going to be a lot more touch and multi-touch stuff going on in Windows 7. When apps use that as the only way of doing something, that’s when accessibility is going to become a big issue. There needs to be always an alternative way. Alternative to drag and drop for example of doing things for people with a vision impairment or can’t using a pointing device, etc. So as long as there’s a redundancy there that’s fine, which there isn’t in the iPhone.

Ryan: OK, that’s great. Just to finish up, is there a, do you have a list of things that you see regularly that are counterproductive to accessibility that you can recommend for our designers and developers to just try and stop doing or try and do better, these are kind of like my top five tips, yeah common mistakes type thing?

Robin: Yeah, if you go to AbilityNet.org.uk/webresources then one of the things we’ve got in there is top five tips and top five sins, that’s one of them. And another one is a top ten checklist of things to do. Which implies that if you do them, then um, well if you hadn’t done them like label images properly, then that would be a sin. So follow the check points, those ten and those are ten things you can avoid sinning on. So yeah, there’s a number of resources on there. Other sites that I would definitely recommend to people for getting to grips with accessibility would be WebAIM.org and they go from the very basics right through to really quite advances. Accessify.com is brilliant because they’ve got of information but also a lot of forums as well so you can kind of talk with other guys getting to grips with it. I would point you at the source of the WCAG guidelines but actually they’re kind of not the best place to start but I mean everyone who knows about accessibility knows where that is anyway which is at w3.org/WAI. But yeah, WebAIM, Accessify and our site are good places to go.

Ryan: Fantastic! Well thank you very much for your time!

Robin: Great!

Ryan: It’s been a pleasure talking to you.

Robin: Thanks ever so.

Thanks goes to Todd Dietrich for transcribing this interview.

Back to top

Review: Migrating to Google Apps

It’s something we’d been considering for a while, we’d weighed up the pros and cons and finally took the plunge. The key benefits of Google Apps are huge amounts of storage, a quality web interface and considerable cost savings. There’s also the reassurance that Google is actively developing the product with regular updates and improvements that don’t require installing fresh software or waiting for a hosted service to upgrade. If you’re currently using POP to receive emails or are archiving locally, you’re running the risk of losing your history of emails, should a disaster befall your computer. Keeping emails in a centralised service and syncing with IMAP gives you the security of safe storage and the convenience of access from anywhere. This is where large storage allowances come in handy.

Preparing

Setting up an account is easy. Google offers a team version with fewer features than the premium, allowing an admin to create users, email lists and try out the service. This is also great for demoing the service. Google provide a test domain for sending and receiving emails using your regular style company email address (firstname.surname@). Depending on how big your organisation / company is, it’s worth testing out a few accounts across as many email clients as people run. It’ll help knowing off the top of your head where various settings are to save on support time later.

Migrating

One of the key features of the premium account is IMAP email import. This allowed us to pull emails from our current Exchange server straight to Google, server to server. You basically just provide Google with your current email login details and it takes care of everything. You can specify a bunch of email accounts to import at once, and if you have a super-admin login to your email you can grab everyones with one set of credentials. This didn’t work perfectly for us, a few accounts seemed to hang and never complete. If that happens, it’s worth removing emails from the server with large attachments and trying again. If all fails, the alternative method is to setup your Google account in your email client and just drag all your emails from one to the other. Might have to leave it going overnight if you have a big inbox! Once you’re ready all you have to do is point your domain MX record at Google and you’re done.
On top of the usual email setup there are a bunch of settings Google recommends for desktop clients to aid consistency with the web version. These help prevent duplicate folders for drafts, sent and trash cluttering up your interface.

Migrating Calendars and contacts is dead easy, Google provide tools to sync local calendars and contacts can be exported / imported.

Support

The biggest hurdle in a switch like this is gonna be support. Unsurprisingly, some people don’t like change, especially when it concerns services as critical to productivity as email. They’ll need reassurances that emails won’t go missing and everything will be as easy as it was before. There will be a short period where emails could end up going to either your old inbox or your new one, but as long as you check both for a couple of weeks post switch, you’ll be fine. We did see an email or two arriving at our old accounts a week after the switch, this is due to caching of MX records, not to worry though, they’ll propagate eventually.

A different way of working

My favourite features of working with Google Mail are archiving and labels. Labels work in the same way as folders, except an email can have several labels at once. This can cause some confusion when using a desktop client, as emails will appear in multiple folders. When an email is deleted from the inbox or any folder in a desktop client, it isn’t deleted on the server. It may still have other labels and will still exist in All Mail. To delete an email from a desktop client it has to be dragged to the Trash/Bin folder. This is great for keeping a clean inbox with current / unhandled with emails.
Another advantage to having all your emails on Google’s servers is search. However fast your computer is, you can’t match the speed at which Google can search your inbox for that elusive message from last year containing critical info. Instead of using a regular desktop client, you can take advantage of Chrome with Gears for a hybrid web client / desktop app. This allows you to keep the benefits of the desktop such as offline email access combined with the familiar web interface.

Thanks goes to Todd Dietrich for transcribing this interview.

Back to top

168. Personality

On this week’s show: Paul explains how to give your site real personality and Dave shares some top tips for writing secure code.

Play

Download this show.

Launch our podcast player

News

Typekit – the messiah of web typography?

There is some big news this week for those website owners and designers keen to use custom fonts on their websites.

For the longest time web designers have been limited to a small subset of fonts that were known to be present on the majority of users PCs. Although CSS font stacks allowed designers to choose less common fonts, because they could specify a safe alternative if that font was unavailable, this did not guarantee the user would see the design as intended. The only way of forcing a particular font was using Flash (via sIFR) or images. However, both of these approaches created potential accessibility problems.

The irony of this situation is that browsers provide a way to embed fonts in your webpage using @font-face. The problem is not technological but legal. Font foundaries are concerned about loosing control over the distribution of their fonts.

This is where Typekit comes in. Typekit is a soon to be released tool from usability expert Jeff Veen. When writing about the service he says…

We’ve been working with foundries to develop a consistent web-only font linking license. We’ve built a technology platform that lets us to host both free and commercial fonts in a way that is incredibly fast, smoothes out differences in how browsers handle type, and offers the level of protection that type designers need without resorting to annoying and ineffective DRM.

As a Typekit user, you’ll have access to our library of high-quality fonts. Just add a line of JavaScript to your markup, tell us what fonts you want to use, and then craft your pages the way you always have. Except now you’ll be able to use real fonts. This really is going to change web design.

In short, they provide an easy and legal way to use custom fonts. Of course, there are still some unknowns. We do not know what font foundries have signed up for the service and so have no way to know what fonts will be available (or how many). We also do not know the prices involved. However, presuming you are happy to use Javascript to deliver your custom font then this looks like a very promising solution.

Apple vs Microsoft – A website usability case study

The Web Designer Depot is running an interesting post that compares the usability of Microsoft and Apple’s websites. Let’s be honest, pitting Microsoft against Apple is a little bit of a gimmick. Its actually very hard to compare these two websites. The two companies are aimed at very different markets (as the post itself admits) and are on very different scales. Apple is much more focused as a business than Microsoft and so the Microsoft site is always going to be more complex.

That said, it is extremely interesting to see the two sites deconstructed from a usability point of view and it does identify a number of common usability issues that we can all learn from.

The article focuses on the following areas…

  • Homepage design
  • Flow
  • Navigation
  • Readability
  • Search
  • Aesthetics
  • Consistency

I am sure it will come as no surprise that Apple won hands down. However, I think it is interesting to note that the primary reason for Microsoft’s failure was its size. The larger a site is, the harder it is to maintain consistency, ensure quality and handle navigation. There is a lesson here for all owners of large websites – if you want your site to be usable, make it smaller by simplifying. Apple applies the principles of simplicity to everything from their products to their websites and it results in exceptional usability.

Reinvigorating old blog posts

This week I came across possibly the most ridiculously named idea in the whole of the web – “Sneeze Pages“.

Although the name is stupid the idea is actually a good one. According to Sitepoint a Sneeze page is…

a page that propels people in different directions deep within your blog by highlighting a variety of posts that you’ve previously written.

In other words it is a way of drawing users attention to older blog content buried deep in your archive and therefore increasing the ‘stickiness’ of your website.

As the post on Sitepoint points out, the problem with blogs is that new user rarely get past the last dozen or so posts. The wealth of content in older posts is largely invisible. It therefore makes a lot of sense to create the occasion post which draws attention to this older content.

The Sitepoint article suggests four types of “Sneeze Pages”:

  • Themed Sneeze Pages—these are posts or pages on your blog or site that revolve around a single theme (e.g. The best of Boagworld usability advice)
  • Time-related Sneeze Pages—these pages are based around a defined period of time (e.g. What you might have missed this month)
  • Retro Sneeze Pages—another variation of the time-related sneeze page is to do one that unashamedly shows off a number of posts ffrom a particular point in its history (e.g. The best of 2008)
  • Series Sneeze Pages—this is the technique of writing a series of blog posts exploring a topic over a period of time with lots of interlinked posts. (e.g. My 10 harsh truth posts)

Personally this strikes me as great advice and you can expect to see several such posts from me over the coming weeks and months.

Creating WCAG 2.0. accessible forms

I never get emails asking us to cover accessibility in more depth. Its just not a sexy topic. Designers, developers and website owners know they should care about accessibility and even endeavor to make their sites accessible. However, it doesn’t really excite people.

However, it is an important topic and one I will continue to cover on the show. I would also argue it can be inspiring  too. I will never forget the first time I watched Robin Christopherson from AbilityNet use a screen reader. Its not until you see it in action that you realize the challenges people face.

The same revelation came for me again when reading Accessible Forms using WCAG 2.0. Its not a light read and takes some getting through. However, it has some great insights into exactly how screen readers deal with forms and yet how easy it is to improve the experience if you know what you are doing.

For example did you know that screen reader users have to enter a special “form mode” to complete a form. When in this mode the screen reader will only read form elements. It will ignore any instructional text, unless it is wrapped in a label or other form element. This can easily be a real problem.

There is also advice on…

  • Colors and fonts
  • Mandatory fields
  • Use of Javascript
  • Timeouts
  • Grouping form elements
  • and much more

Personally, I feel this should be required reading for all designers and developers.

Back to top

Feature: How site personas can enhance your sites

If your website was a person, what type of person would it be? It is an interesting question. Take a look at your website for a moment. Look at the design, read some of the copy. Can you picture a single person that represents your site? If the answer is no, then you may benefit from the creation a site persona.

Read How Site Personas Can Enhance Your Website

Back to top

Listeners feedback: Stop hackers hacking your hackey code!

Steve from Aberdeen writes:

You promote the show as being for all those who “design, develop and run websites on a daily basis” but actually don’t cover much for us developers! How about covering some more developer orientated topics such as website security.

Its a fair accusation Steve, which is why I we have Dave on the show this week. He is going to provide a basic introduction to website security.

Security is a complicated monster to tackle, so it helps to think about it in really, really basic terms. Stuff comes in, stuff goes out. We have to assume that anything that comes from the user is dangerous, or tainted, and can’t be trusted in any way what so ever. We don’t even know for sure that the user is who they claim to be. Trust no-one. We also have to be 100% sure that anything we send back to the user is safe, un-tainted, and uncompromising. You don’t want to send dodgy scripts to your users, and neither do you want to send back valuable clues to the inner workings of your code. This is not meant to be an all-encompassing guide to preventing attacks, but instead a set of guidelines to writing applications in secure way.

Minimise

The first rule is this. Minimise areas that accept input from the request, and minimise areas that send response. Sanitisation and validation should be the first thing you perform on data received and the last thing before you return it. Following a sensible architecture such as the Model View Controller approach separates data received by the Controller area and data returned to the View. This will make your life far simpler when you start tackling such issues. This applies to all forms of input (form data, querystrings and cookies) and all forms of output (HTML, redirect, file download).

Validate

A commonly overlooked validation is confirming the data has been intensionally sent from the user. There’s nothing to stop a 3rd party website posting to your website, so it doesn’t matter how secure your login form is, the posted data could be coming from any of the dodgy websites your user has open. An easy solution is to use a random key as part of every posted form, unique to the users session. This way you can easily verify the form has been posted from a tightly controlled page you served to your user. It’s not enough to look at referrer headers, because these are easily faked. ASP.Net web forms, to their credit, do this by default.

Use White-lists over Black-lists. Lets say for example you’re validating a phone number, you don’t specifiy every non-digit character you want to remove, you strip everything that isn’t 0-9. A little too obvious? The same applies to the classic script tag. If you start trying to remove every form of <script> tag, you’ll end up playing catch-up against tricks using <img>, <body> and clever encoding. If allowing any kind of HTML through is necessary, you’d better be damned sure who submitted it and who is going to be able to see it.

Storage

So you’ve received your data, it looks pretty good. Whatcha gonna do with it? If it’s heading towards a database, you can’t be too careful. Escape it, or better yet use parameterised queries. If it’s the file system that your data is ending up, put it somewhere sensible. Ideally, this would be somewhere outside of your webroot, or in a protected folder. Whatever happens, you don’t want anything here directly accessible or executable. Just to be sure.

Responses

OK, so we’re sending a response. Just because the data we received passed our tried-and-tested validations doesn’t mean it’s safe to send back to the user. We HTML encode everything, unless absolutely necessary. If it’s plain text, fairly straight forward. If you’re putting suspect data into an HTML attribute, it might be an idea to verfify the format. If you think you’re outputting an SRC or HREF, check it at least looks like a path. If your response happens to be a redirect, double check nothing funny is going on with the URL. If your response is a (serious) error, make it look friendly, but don’t give away exactly what went wrong. If you want to send them a file, attaching it and manually setting the MIME type is more controlled to simply pointing them at the file.

This is not intended as a set of golden rules, rather a few key points to help you think about the code you write. Most new forms of injection and hackery are just clever ways of attacking poor code. Writing sensible code will keep you one step ahead of such attacks.

Back to top

164. Case Study

On this week’s show: Paul shares his experiences of working on the Wiltshire Farm Foods website, we examine the role of Twitter and Ryan Carson shares some more advice on building web applications.

Play

Download this show.

Launch our podcast player

Housekeeping

Write for Boagworld

I am constantly amazed by the intelligence of those who listen to this show. The talent and knowledge of the Boagworld community is truly staggering. If you don’t believe me spend a bit of time in the boagworld forum.

I am therefore looking to get more people involved in publishing to the Boagworld website. If you have an idea for a post that you think others will be interested in, write an outline and post it to this thread. If the idea is appropriate I will get in touch and arrange for your post to be published.

Obviously, the post will be fully credited to you and will link to your site. Hopefully that will make it a worthwhile marketing opportunity!

Back to top

News

The importance of sketchbooks

Talk to any designer and they will tell you about the importance of keeping a sketchbook. Ask that same designer whether they actually do it and the answer will probably be no.

The most common reason for not doing so is a belief that you need to be able to draw to have a sketchbook. Believe it or not most designers cannot draw. According to Jason Santa Maria’s latest post “Pretty Sketchy” that is not the case.

He argues that…

Sketchbook’s are not about being a good artist, they’re about being a good thinker.

I have to agree. However, sketchbooks have always filled me with some trepidation. Although I know they don’t need to be a work of art, I still want them to be.

That said, this post has inspired me to start keeping a sketchbook again. I know I am no longer what you would consider a designer, but Jason has made me realise that having an easily accessible place to keep ideas is worthwhile, whatever your role.

I encourage you to read Jason’s post and do the same.

Supporting old browsers

Jonathan Snook has written an interesting post about support for old browsers this week. He begins the post by establishing the importance of supporting older browsers. He writes…

When it comes to market support, I’ve often looked at it as one big pie. You may say that Opera is too small to really care about. It’s only 2%. You don’t care about Firefox 2 users. It’s only 2%. You may not care about accessibility issues. It’s only 2%. Soon enough, you’ve whittled down your potential market to 90% of what it could have been.

This is certainly a slippery slope and one that I personally take very seriously, hence my posts on Graded Browser Support.

However, as Jonathan goes on to point out, graded browser support is not without its problems. Although it is relatively easy to provide alternative basic styling to IE6 and below (thanks to conditional comments), it is much harder with earlier versions of Firefox, Opera and Safari.

Personally, I am not happy to resort to browser sniffing and I am not sure this is a massive issue. Based on stats from sites we are involved in, most users of minority browsers (Safari, Firefox and Opera) upgrade to the latest version.

In the end you can only test on so many browsers.

Approaching content on the web differently

The two articles that have most excited me this week both relate to website copy.

As we have said many times before on this show, all too often website owners are willing to invest considerable time and money in getting design right, but largely ignore their content. If you are willing to pay a designer to work on your site, you should also be willing to invest in a content strategist.

Tiffani Jones from Blue Flavour outlines the role of a content strategist in here post “Learning About Content Strategy“. When describing this emerging discipline she writes…

We kind of know that it lives somewhere between web writing, web editing, information architecture, SEO stuff, web analytics, and production.

She goes on to demonstrate that websites need somebody capable of writing good copy but also understanding SEO, wireframing, marketing and much more.

Of course, many people think they can write good copy themselves. They may infact be able to do so. However as Gerry McGovern points out in our second post about copy, good web copy writing is different from traditional writing.

Gerry argues that some of the rules of traditional writing do not apply to the web. He compares writing online copy to giving an elevator pitch…

Your customer has walked into the elevator, the doors have closed, they turn to you and say: “Convince me before the next stop to buy your product.” Design your website from the ‘I badly need to go to the toilet’ perspective. Your customer needs to act and act quickly. That’s the Web.

Setting aside the dubious toilet analogy, this is an excellent post that really makes you think about whether your copy is meeting users needs or massaging your own ego.

Improve usability through help elements

Smashing Magazine have released a helpful article on help this week.

It looks at the context sensitive help that is becoming increasingly prominent in web applications, ecommerce systems and forms. It outlines the obvious usability benefits and gives loads of examples of how context sensitive help can be implemented.

There are no major revelations in this post but it is useful to see how others have tackled this issue and to be reminded just how important help is.

It is too easy to address help as an after thought and so not properly integrate it into the design. As designers it is often not until a developer asks about error handling that we begin to start thinking about help messaging. We need to ensure it is apart of our design process and that the wording of these messages as well as their design is carefully considered.

Audible recommendation

Download a free audiobook today

This week I would like to recommend Nudge on Audible.com, a book about influencing the decisions people make. Although not directly about web design it has had a profound influence on how I build sites. If you want to influence the behaviour of users then I would highly recommend this book.

Best of all if you sign up with Audible you can get this book totally free. Simply go to www.audiblepodcast.com/boagworld and claim your free credit.

If you want to listen to it, Audible has it! With over 60,000 titles and virtually every genre, you’ll find what you’re looking for. Get a free audiobook and 14-day trial today by signing up at www.audiblepodcast.com/boagworld.

Back to top

Feature: Case Study: Wiltshire Farm Foods

One of the biggest challenges of running a successful website is balancing the needs of users with those of the business. This is especially true when an existing business model conflicts with user needs.

Read the full article

Back to top

Ryan Carson: Advice on building web apps part 2

Ryan Carson:Hey Everybody, this is Ryan Carson one of the founders of Carsonified.com today we are doing are second instalment of five minute Web App tips for Boagworld. So let’s get started, the first thing I’d say is do not build your billing system from scratch. Now, if you have a Web App that does recurring billing, so you are charging someone’s credit card every month there is quite a bit of code to write for that. When we built dropsend.com there was at least 1200 lines of php code in order to do that, and it’s a very difficult problem to solve. You have to do things like charge someone’s card if their card has been cancelled, send notifications, try to bill them again and in seven days bill them again, another seven days keep track of invoices, cancel them if they cancel their account. It is just a real headache and there is a lot of stuff that can go wrong with that. So, I would say you should outsource something like that to spreedly.com. Basically it’s an API web service that does recurring billing for you, so give it a try. I don’t work for them; I’m not being paid to say that, I just think it’s a good idea. And y’know if you ever decide to switch out of Spreedly the nice thing is that you’ll make a series of API calls out to the service and all that you’ve got to do is bill those services internally if you decide to do so later. So it’s definitely important not to waste time doing that from the beginning. Also, some people may say “Well, what about the fact they are going to take a part of your revenue?”. Well, the truth is, your bank is going to take that cut anyway, so you might as well have Spreely take that cut, there really is no loss there.

The second tip I’d like to talk about today is that you should plan on doing AB testing from the very beginning. When you do all of your site designs, especially your Home Page and your Sign Up/Payment Page, those really need to be tested with AB testing from the very beginning. Have a series of phrases or different graphics you plan on switching back and forth and make sure you measure which ones are working and increasing your paid sign ups. There is a great post on “Signal Vs Noise” about that, if you go to bit.ly/ab-test they talk about their pricing page and how they made some basic changes and they saw huge increases, 30% in sales for instance, it’s really important. On the subject of AB pricing I spoke to Jason Fried over coffee at the Future of Web Apps in Miami. I said “Can you tell me anymore about what you learned during AB testing?” and he told something really fascinating which was, When they changed the words ‘Free Trial’ (or Sign Up for free) on their Home Page to ‘See plans and pricing’, they saw an increase of 200%, so that was a real shocker. What he said was happening was that, people were afraid of signing up. Y’know they thought if they clicked on the ‘Free Sign Up’ button, then somehow they would automatically get an account that they could not get out of. Whereas if you say “Hey, Check out plans and pricing”, y’know no commitment, people are much more willing to click through and then probably
sign-up. So that was really interesting.

Okay, another tip for you is, I would suggest creating a new company for your Web App. The temptation would be to launch it as a service of your current company. So for us, when we launched Dropsend.com it was owned by Carsonified. But when we sold Dropsend it was really hard to extract out that company from Carsonified. So if we had started Dropsend Ltd. or Dropsend LLC it would have been a lot easier to do that. So I would just set up a fresh company from the beginning, it can be owned 100% by your current company which will make selling it, if you ever sell, a lot easier.

The final tip I’d like to talk about today is source control and I would highly recommend you use http://github.com it’s free, it’s a wonderful way to keep track of your repository for code and I’d highly recommend it. So, that’s it, thanks for your time today, and thanks for listening. Goodbye

Thanks goes to Ben Hardcastle for transcribing this portion of the show.

Back to top

Listeners Questions

Twitter

This week I received two excellent and related questions about the use of Twitter as a marketing tool. The first comes from Teifion who asks…

My question concerns morality and twitter, an odd combination I know. I have several bots on twitter, all day long they download RSS feeds and then tweet links to new articles. A good example would be @design_agg which reads design websites such as Boagworld, it then tweets the relevant links to the post and the post title. There are other bots like them, for example I know that @stanton maintains the @boaglinks bot.

Of course, none of these bots create content, they simply link to it. The question is, is this wrong professionally and is it wrong on a social level? For a list of the bots, just look at who @design_agg follows.

The second questions refers to another automated Twitter account…

Hello Mr Paul Boag, this is Jimmy Nightly from the Swedish online auction site jiiro.com. I’ve recently been following Amazon on Twitter and they’re using several feeds to draw traffic to current campaigns. Their feed Amazon Deals has only 8000 followers and to me it just doesn’t seem that much compaired to how big Amazon really is over here. My point is, if they only have 8000 followers do you then think Twitter is a marketing tool for the future?

Both questions revolve around the subject of automated twitter accounts. These are accounts where the posts are automatically generated rather than the thoughts of a particular individual. Our first question is concerned with their morality and the second is concerned with their effectiveness. Both valid concerns.

Let’s take each issue in turn…

The morality of automated twitter accounts

The fact that Boagworld runs an automated twitter account posting web design related links shows that I do not have a problem with their morality. However, I understand that others do. Let’s look at two potential criticisms.

  • They are not in the spirit of Twitter – Some argue that Twitter was not created as a broadcast tool and should not be used in that way. Twitter is about community not news/announcements. Although I do agree with this point to some extent (as you will hear later) I don’t think the argument ultimately stands up. Strictly speaking Twitter was created for people to post ‘what they are doing’. In reality it is rarely used in that way. Twitter has grown to be much more than originally intended and a broadcast mechanism is a part of that.
  • They steal content from others – The second concern is that they are regurgitating content created by others. They are not in themselves creating value. Again I would disagree. Their value comes in the time saved for the reader. Instead of having to manually check sources, they are presented with all they need to know in a convenient form. In my mind it is no different from an RSS feed on Delicious or the news section of this show.
  • In the end, if people do not like these ‘bots’ they can unsubscribe. However, some do find them useful and there is no reason why they should be denied their services.

    Of course, they may provide value to the subscriber, but do they provide value for the owner. Are automated twitter accounts an effective marketing tool?

    The effectiveness of automated twitter accounts

    Jimi’s question calls into doubt the effectiveness of Twitter as a marketing tool, citing the Amazon Twitter account as proof. It is remarkable that Amazon only have 8000 followers on this account but it is worth noting that their Amazon MP3 account has over 300,000.

    However, it is not the specifics of Jimi’s question that I would challenge. It is the entire premise. To me, if Twitter is used well, it can be a lot more than a marketing tool. Companies like Amazon are failing to grasp the full potential of Twitter because they are using it as a broadcast tool, rather than a way to engage with its users.

    Twitter provides a lot more than an opportunity to broadcast your latest deals. Twitter also allows…

    • An opportunity for great customer service
    • A chance to inform your new products and services
    • A way of creating passionate evangelistic users
    • Real engagement with your users

    Unfortunately using Twitter to publish automated ‘feeds’ fails to reap these benefits. It in no way engages with followers. It only broadcasts.

    Only by engaging with their followers will organisations really reap the benefits of Twitter. Companies like Zappos or Omnigroup are leading the way in this by using Twitter to provide support, inform their future products and engaging with their community.

    Back to top

    Case Study: Wiltshire Farm Foods

    One of the biggest challenges of running a successful website is balancing the needs of users with those of the business. This is especially true when an existing business model conflicts with user needs.

    Although not always the case, one situation where this conflict can arise is with franchise based businesses. For the last few years I have been working with a franchise business called Wiltshire Farm Foods. Although, their business model has been phenomenally successful it caused significant problems for their online customers.

    When business models and user needs conflict

    When hired to redevelop the Wiltshire Farm Foods website I saw an opportunity for a quick win. Before a user could enter the website, they were required to provide a postcode. This was a massive barrier to entry as users do not like handing over personal information (such as a postcode) without being given a reason. From looking at the website statistics it was obvious many users were abandoning the site because of this requirement. I couldn’t understand why the company had created such a huge usability hurdle.

    The Old WFF homepage

    The answer was simple – Wiltshire Farm Foods had chosen to give their franchisees control over pricing. Without knowing where the user was located it was impossible to provide a price.

    The decision to give franchisee variable pricing was a good one in the pre e-commerce era. However, as the importance of the web grew, it created a significant problem when competing against large supermarket chains with a national distribution network and standardised prices.

    Although this was a problem for online users, the model worked for the business as a whole. Wiltshire Farm Foods had an incredibly successful relationship with its franchisees. Some had been with the company since day one. The business was driven by the entrepreneurial spirit of its franchisees and independent pricing was a key component of that success.

    Working within constraints

    With the variable pricing constraint remaining unmovable it became a case of managing the impact. Our first step was to move the point at which users were asked for a postcode. Instead of requesting it up front, we only asked for it when users asked for a price. This allowed users to view products and clearly linked the request for a postcode with pricing. We also explained why this step was necessary to reassure users this was not a ploy to send them unsolicited mail. However, ultimately we could not get around the extra step required to see prices.

    It would have been counter productive to dig our heels in and refuse to compromise the user experience. Instead we took a pragmatic approach and worked within the business constraints. Ultimately this worked in our favour. When Wiltshire Farm Foods saw the increase in sales that came from moving where users entered their postcode, it encouraged them to consider changes in their business model.

    Users now get a web price for each product when they arrive on the site for the first time. This price is then ‘adjusted’ once they login or provide a postcode. The user is notified of the change and because the price normally decreases they are generally happy. It is not ideal but it is a dramatic improvement that has greatly increased sales.

    Turning a negative into a positive

    Although the introduction of web prices is significant, it has not been the biggest change in the site. The real change has happened in my own thinking. In the beginning I saw the franchise model as a hurdle to overcome. However, I have since come to realise the benefit it has to the overall user experience, especially for the site’s target audience.

    The Wiltshire Farm Foods audience is elderly with the average purchaser being in their eighties. Not only does this audience have certain accessibility requirements, they also have a number of concerns that need addressing.

    One of their biggest concerns is security, both when purchasing online but also when meals are delivered. They are nervous about letting strangers in their house and yet need help unpacking and storing their meals.

    The Wiltshire Farm Foods franchise system accommodates this perfectly. Customers always get the same driver and feel they are dealing with a local supplier rather than a national brand. They can even pay with cash on delivery and place new orders directly with the driver.

    The problem was that the website did not reflect this local caring service. I was so preoccupied with the negatives of the franchise system, that I failed to identify it as a major selling point.

    Franchises can offer personal service

    Fortunately as I grew to understand the business model, I was able to grasp what Wiltshire Farm Foods had known since the beginning – that service was what set them apart. Wiltshire Farm Foods did not need to be overly concerned about universal pricing because they offered things no national supermarket could. They offered a friendly, caring service from police checked uniformed drivers. These drivers would even unpack meals and take next orders. However, most importantly they were a local supplier who customers came to know personally.

    Once I understood this important selling point it fundamentally altered my approach to the site. The homepage shifted away from merely showing products to promoting the service that was supplied alongside the meals.

    WFF homepage

    The homepage now focuses on promoting these ‘value added’ services through the use of animation. However, more importantly we made a feature of postcode entry. Entering your postcode no longer just revealed your region specific pricing, it introduced you to your local franchisee. Gone was the faceless national brand and instead you were given the names and phone number of your local supplier. Soon you will even see a photograph of your local franchisee and details about their delivery schedules.

    Screenshot of the local outlet information

    All of this helps to reassure the user and personalise the experience. Computers are seen by many (especially the elderly) as impersonal and cold. Techniques like this humanise the experience and connect with users.

    Lessons learnt

    There is a lot that can be learned from the development of the Wiltshire Farm Foods website. We can learn about the importance of understanding your target audience and their motivations. We can learn how a perceived limitation in a business model can be turned into a strength. However, what excites me most is the opportunities provided by the Franchise model to engage with users in a more personal way that is lacking in many websites. With the growth of online social interaction there is the potential for an unprecedented level of customer care.

    160. Education, Education, Education

    On this week’s show: We speak to Aarron Walter about teaching web standards. Ryan Carson starts a series on web applications and Paul talks about remote user testing.

    Play

    Download this show.

    Launch our podcast player

    Housekeeping

    A couple of quick pieces of housekeeping to kick off with…

    • Huge thanks to Ryan Taylor, Paul Stanton and Sarah Parmenter who did a stellar job standing in for myself and Marcus on last week’s show. They were actually far too good and I have already started receiving requests that they become the permanent hosts! Anyway, if you didn’t hear last week’s show then make a point of downloading it.
    • My second piece of housekeeping is a quick plug for Bamboo Juice, a grass roots conference taking place in Cornwall on the 24th April. Myself and Jeremy Keith are just two of the speakers in what will be a packed day. It’s so good to see smaller conferences like this springing up outside of London and so I would encourage as many of you as possible to attend. Best of all its only £99 (£79 for Boagworld listeners!)

    News

    To be honest, what with SXSW and my week’s holiday I am feeling completely out of touch with the web design world. Fortunately, Mr Stanton is continually updating our twitter feed with juicy stories. I have therefore picked 4 that caught my eye.

    How to create a great web design CV

    Poor old Smashing Magazine. People do like to tease them (myself included), but they write some damn useful articles. A recent example that caught my eye was ‘How To Create A Great Web Design CV and Resume?‘.

    This post is essentially two articles in one. It starts by asking 10 designers to design a hypothetical CV for a fictional individual. Each designer writes a short paragraph about their chosen approach and you get to look at some nice examples.

    The second part of the post provides 10 useful tips for creating a great CV. Suggestions include…

    • Make it printable
    • Have a summary
    • Link to online projects
    • Show your personality
    • Keep it simple and understandable

    For the complete list of tips read the whole post.

    Its a good post, but I am not sure whether producing a ‘designed CV’ is entirely necessary for web designers. If I was hiring a print designer then I would expect a CV to look impressive. However, if I am recruiting a web designer I think I would be just as happy receiving a cleanly designed CV that links to a stunning portfolio website.

    There are a lot of differences between designing for the web and print. It is possible to be good at one and not the other. Therefore, a printed CV doesn’t tell me much about a persons capability as a web designer. That said, a well designed CV isn’t going to hurt your cause!

    Design: Make it Memorable

    One tip that could have gone in the Smashing Magazine article, is to make your CV ‘memorable’ and not just ‘flashy’. This picks up on the theme of a post over at 37 Signals entitled Designers: Make it Memorable.

    The post talks about the difference between making something visually appealing and actually memorable. Too many sites are impressive but fail to leave a lasting impression. At one point in the post the author writes…

    I started to recall those amazing Flash Sites of the Day. You know those sites that get passed around via IM in your office on a slow day? Simply amazing design and programming. Problem is: I can’t for the life of me remember what those URLs were much less the company/product that was being featured! Isn’t that the point with those sites? That the impact should be profound so that you remember Product or Company X?

    This is a lesson that all those involved in the web design process need to learn. Whether we are designers or website owners, we have a tendency towards thing that provide the wow factor. However, often it is the thing that makes us go wow we remember rather than the message being communicated.

    Statistics and website owners

    Our next article of the week is an ‘all too brief’ post on web stats entitled How to Sell Statistics to Clients.

    The post focuses on a common problem – most website owners know they should be tracking website statistics, but don’t really know what they are looking for. In fact the author writes…

    In my experience, the loudness or frequency of a person’s request for web statistics is inversely proportional to their understanding of them.

    That has often been my experience too.

    He goes on to identify three ways that we as web designers can help rectify this problem. These are:

    • Providing cheat sheets that help the client understand terms like ‘hits’ ‘page views’ and ‘unique users’.
    • Add web metrics training into the budget of your projects.
    • Provide summaries and reports for the client on key metrics such as conversion rates or sales.

    To be honest this is a much bigger problem than can be covered in a short blog post. Too many website owners think that having Google Analytics will solve their statistics needs. However, having the data is not the same as understanding it. If this information is misread it can lead to bad decisions about the future development of a site.

    Specialist vs. Generalist: Who Wins?

    The final post this week is of interest to pretty much everybody who listens to this show. It asks which is better – the Specialist or the Generalist.

    This is an important questions for both web designers and website owners. As web designers we need to know whether we should be specialising in a specific area of web design. It is important for our careers and our businesses.

    As website owners we want to know whether the pain of dealing with multiple specialist suppliers is worth the increased expertise you would receive over a generalist.

    It has to be said the article is written mainly from the web designers perspective. However, I think there are lessons to be learnt for all sides.

    The post outlines the pros and cons of both approaches, but ultimately comes down on the fence when it says…

    There are advantages to being in both groups, but I think the only way to be truly successful is by being a little of both. You can be a specialist, but in order to be able to develop a profitable business, you may need to be able to supplement your specialty services with some add-on services that may not be exactly in line with your focus.

    Personally, I think it depends on how you define specialist. The type and level of specialisation can vary massively and the way you position yourself will define your success. For example, you may specialise in a certain discipline (e.g. Ruby on Rails development) or in a specific market (Higher Education).

    Ultimately, whether you are a website owner seeking an agency or a web designer forging a career, it is all about balance.

    As a web designer, if you specialise too much you will not find work. If you generalise you cannot differentiate yourself.

    As a website owner you want a web designer who is enough of an expert to deliver an outstanding solution, but you do not want so many specialists that your project turns into a nightmare.

    Back to top

    Interview: Aarron Walter on Interact

    Paul: Hello, and so joining me today is Aarron Walter. Good to have you on the show, Aarron.

    Aarron: Thanks for having me.

    Paul: And the reason we have Aarron on the show is because he is going to talk about a new initiative.. is ‘initiative’ the right word, Aarron?

    Aarron: Yeah, yeah.

    Paul: Let’s go with that. A new initiative from the web standards project, called Interact. Now, let’s kick off, Aarron, by maybe you telling our listeners a little bit about what Interact is.

    Aarron: So, whilst Interact is an open curriculum framework, basically we’ve been recognising that the Web Standards Project has been around for a long time and we’ve done a lot of things to try to get standards into industry. And to a certain degree we’ve made some big triumphs in that respect, but there are still a lot of websites out there that aren’t following standards and people that are sort of behind. And we saw the Achilles heal as to why that’s not happening, as really, education. So, you know, our medium’s really young and it hasn’t really found it’s bearings with how we’re going to marry industry and education, so whilst Interact is a curriculum that has a series of courses that teach not only web standards, but best practices.

    So there’s of course the stuff that you would expect from WaSP which is the front-end development courses that teach progressive enhancement and semantic markup and that sort of thing. But we have six learning tracks that include foundations; there’s a course in there that’s like an intro to internet concepts and how people can use the internet to teach themselves and use RSS, that sort of thing.

    So there’s front end development, there’s a design track, there’s server side development, there’s user science and then there’s also professional practice. So what we’re trying to do is create a collection of courses that are very modular, to try to get these into schools. And we recognise that not every school is just going to take the entire curriculum and integrate that into their program. You know, if you’re a Computer Science program maybe you’ll take a course or two, if you’re a design program you’ll take a course or two, or even just grab the assignments or look at our competencies.

    Each course is based on competencies, which are the things a student has to master before they can pass a course. And then the evaluation methods: So each course has assignments, it has exam questions, it has readings that come from Operas own web standards curriculum – we’ve been collaborating with them. It has textbooks, it has pretty much everything that an educator could need to teach a particular topic.

    Paul: Okay, so is this something that is then aimed entirely at educators, or if somebody wanted to get into web design and they were trying to learn it in their spare time, could they just go to this and use it in isolation by themselves?

    Aarron: To some degree, I guess they could, but Operas web standards curriculum is really learner-centric, so if you’re trying to teach yourself, that’s probably the place to go. But ours is very much focused on educators, because we feel like there’s a lot of great resources out there on the web if someone wants to teach themselves, but there’s not a lot of great stuff for educators to get stuff into their courses.

    Paul: So, when you say ‘educators’, I mean what kind of level are we looking at here? Earlier you mentioned schools. Are we talking about school age, or are we talking about higher education? What are we covering here?

    Aarron: I’d say our primary target is higher education, colleges, universities, even training programs to some degree. But we are also seeing some of our content in high schools as well and we’d like to see that more. Especially foundations courses like the web design one course or the internet fundamentals course. If students could go into college with a solid foundation, then they can start to focus more on "What can I do with these techniques?" than theory and concept.

    Paul: So is this design to be fairly international or is it quite U.S centric in the way that it’s written.

    Aarron: We want it to be very international and the people that have worked together on this are from lots of different places. We’ve got some folks in Europe, Canada and of course some folks in the U.S, so it is in an international group that’s coming together and we’re actually working with WaSPs ILG group – that’s the International Liaison Group. And we’re working on, this year one of our big goals is to try to get a lot of our content translated to different languages.

    Paul: Okay, so there will be multiple language versions of all of this as well at some point?

    Aarron: That’s the direction we’re heading, yes.

    Paul: So, I mean, how did this come about in the sense of, you know, well, how did you get involved in it for a start and what was the motivation behind it?

    Aarron: So, I’ve been teaching for the past ten years in different schools in the U.S and colleges and universities, but I’ve also been working in the industry as well. And I got on WaSPs mailing list, I just joined the mailing list and started to talk to some folks and then they invited me to join – it was a year ago, I guess it was at the very beginning of 2008 – and so I joined the education task force who created the Interact project. And basically there were ideas about the curriculum and I’d heard lots of people say "Yeah, what we really need is, you know, education’s way behind" and they’re happy to point fingers and "We need a curriculum", but it just never was really transpiring from anyone coming from the industry and so we kind of just decided we need to do this. And I’ve helped create curricula before as a faculty member at the Art Institute of Atlanta and so I had some ideas and we had a really great group of folks that are in the education task force – people that are educators and people that are experts from the industries. So, yeah.. actually South by South West was where this all started, which is pretty amazing, of course there are lots of great people there. So Glenda Sims, who’s one of the heads of WaSP these days introduced me to Chris Mills from Opera who was working on his project and we kind of had some drinks at the Geeks Club bowling event and we just kind of went crazy talking about these ideas. And Steph Troeth then Leslie Jensen-Inman and we all had these ideas, and then we just set a goal for ourselves in 2008 at South by South West and we said "In a years time, we’re gonna be back and we’re gonna have a curriculum." and that’s what we did. This year we launched our curriculum at South By.

    Paul: That’s quite an impressive turnaround for the amount of information that’s in there. How did you draw everything together? Where did it all come from?

    Aarron: Well, we met every week online and we talked and we established a course template, which really helped us. The stuff that we really needed to put in these foundation courses, we all know what needs to go in there. It’s just a matter of getting around the pedagogy or the educational part of it. So we developed a template for assignments, a template for a course and a template for learning modules which are basically like, you know, a teacher could teach a concept like let’s say, HTML forms in a weeks time. So we developed those templates and then from there we just assigned courses to different people and we used a wiki and we just met regularly and.. I gotta say, you don’t have to have a huge group to develop a curriculum.You just have to have a few people who really have their heart in it and.. we have some amazing folks, so..

    Paul: So, what kind of response are you getting so far from H.E institutions? Are they interested in adopting it? If they are, how are they going to go about that, because, I mean, my impression is that it always takes forever to get a curriculum approved at a university or whatever. So I’m just interested in how that process is going.

    Aarron: Yeah, education is.. one of it’s benefits is that it’s slow to move, so once it gets a solid foundation it keeps that solid, but you know, one of it’s drawbacks is that it’s slow to move. And so we’ve got some schools that are really excited about it and generally the folks that.. you know, it’s only been a couple of weeks that this has been live, we’ve got some folks that are really excited about it and those are folks that were kind of headed in the same direction themselves. So we’ve gotten some responses from schools in Europe and some schools in the United States that are interested in pulling some stuff in. And we have a school that’s looking at using a lot of our content right now. So we’re in the early stages of trying to get this out there. I think the easiest part is building the curriculum, because we know what needs to go in there. The hardest part is getting it into schools. So one of our strategies is to get the endorsements of folks in the industry, so we’ve gotten endorsements from Google, from Yahoo, from Adobe, from W3C, from Opera, from Mozilla – they’re all just super excited about what we’re doing and that sort of brand recognition can help us get our foot in the door with schools. And of course going out to conferences, we’ve got folks at the European Accessibility conference right now, talking about it, so we’re just trying to get out there and let people know.

    Paul: Excellent. That sounds brilliant. I mean, I know that a lot of people that listen to the Boagworld podcast – there’s a large number of students that we’ve got listening and I often get complaints about this, that what they’re being taught at university bears no resemblance to what they’re hearing on this podcast. And I’m hoping that that’s because the podcast is right and the university is wrong and not the other way around. So if they’re listening to this and they’re getting really excited about it and, you know, they’ve gone to your website and they’re seeing the curriculum – I’ve got it on front of me now and it does look really exciting – how do they make this happen in their institution? What would you encourage them to do?

    Aarron: So, this is the interesting thing – that so many of us have complained about a problem, but there aren’t a lot of people that will take that complaint and turn it into action. So if you’re a student or if you’re an educator what we need you to do is, there’s a page that’s called Advocate Standards (http://interact.webstandards.org/advocate/) – you can get to it from the homepage of http://interact.webstandards.org. It kind of just describes what standards are, why they’re relevant to you and we need people to share that information with their teachers, we need people to share just this website with their colleagues and show them the testimonials of the people who believe in this and want students to come out of schools with these skills. So we need people to act in a bottom-up sort of way, you know, grass roots. Take this to your classroom, take this to your teacher, take this department chair and just let him know. That’s the most powerful thing that people can do right now.

    Paul: I mean, what I’m quite excited about from looking at this curriculum is that it contains a lot more than "Here’s how you code in X language" or whatever and even has got more in it than just design and user experience stuff. All this stuff about professional practices is very exciting too. Could you perhaps tell us a little bit about that?

    Aarron: Yeah, so professional practice, we want people to not only get the concrete skills of "I can code a standard compliant page" or "I can construct a usable website", but we want people to be able to present their about their work and you know, be able to survive in a real career in the web. And so professional practices is going to have a series of courses to do that. We’ve got some pretty exciting ones that are coming up. There’s ‘writing for the web’ – it’s going to be a really cool one, that Alan Hussain from a List Apart is going to be creating. And we have a presentation course that’s coming down the line. So, we’ve got a number of those coming up.

    Paul: That’s quite interesting, you just said something that I hadn’t grasped which is that there’s more to come here. That this isn’t the end of the line. It sounds like you’ve got lots more that you’re still developing. Is that right?

    Aarron: Yeah. We call it a living curriculum, because you never write a curriculum and then you’re done. Especially in our industry, things change so fast. is what of course we’re going to be working on this year. Our design track is light right now and we want to try and address that ASAP, so we’ve got Dan Rubin and Ethan Marcott, are working together to create a foundation design course, that is specific to what web designers need to understand. And we also have Dan Mall is going to be helping us with a Flash course and Aral Balkan is also going to help us with some flash stuff too. We have a lot of stuff going on this year for new courses, so we hope next year at South By when we see everybody that we’ll have a brand new stack to add to Interact.

    Paul: Excellent, so do you kind of envisage, from an institutional point of view that, like we were saying, it takes a long time for a curriculum to get approved and that part of the problem has always been that, by the time it’s approved it’s out of date, when it comes to the web. So is the idea that you’re going to get institutions to buy into the Interact curriculum in its evolving nature so that they always get the most up to date version of it. Is that the kind of plan? They’re not grasping one moment in time from it, if that makes sense?

    Aarron: Yeah, exactly and we want to take some of the hard work out of being a teacher. I speak from experience, there’s so many things you have to keep track of and trying to keep pace with a lot of changing technologies and concepts, that’s hard on top of the umpteen other plates you’re spinning. So that’s exactly what’s going to happen, is that our courses, they’re not chiseled in stone, they’re published on the web, they’re in an expression engine and we’ll change those as they need to be changed. But that said, we need to strike a balance, because we can’t be chasing every new technology all the time, we have to evaluate and there has to be foundational concepts that remain steady. Separation of presentation and content, that’s steady foundation concept. But new technologies or techniques, they might change.

    Paul: Okay, I mean, the whole area of education and web design is massively exciting and there’s so much going on at the moment in so many different fields. I mean, from your perspective, what else out there is really exciting you at the moment that you’re seeing.

    Aarron: There’s so much, I just feel like last year that I just saw so many companies, organisations, individuals that, it seems that everyone just was pissed and they just walked out their house and they were headed in one direction until it was like everyone sort of meets up in one big mob. And so, what Opera’s doing, what Chris Mills has done with the 55 articles that he’s brought together and edited for Opera Web Standards Curriculum, that’s huge. Those are all rolled into WaSP Interact as our recommended reading, so that was fantastic. Yahoos Juku project, if you’ve heard of this it’s quite amazing. Nick Fogler, who’s the running Juku – Yahoo actually has a training program, where they bring students that are not employees, they’re not hiring them. They bring them in and they train them to be front end engineers over the course of a few months. And they’re doing it because they’re trying to solve this problem on their own. So, we’re talking with them about how they’re solving problems and looking to collaborate and discuss what we can learn from them. John Allsopp who runs Web Directions (the conference series), he brought myself and Chris Mills and Steph Troeth together with a number of other experts and we did Ed Directions, which was a day long workshop that taught teachers how to teach these concepts in their classroom. So there’s just so much stuff that’s happening right now and that’s just the tip of the iceberg.

    Paul: Exciting stuff. It sounds like it’s a really good time and it’s great to have you on the show. How you manage to fit all of this in alongside earning a living too is quite beyond me, but it’s really good that so many people are volunteering and pitching in. That’s great. Okay, let’s get you back on the show, I guess in a years time and sees what’s changed. But thank you very much for coming in now and I will talk to you again soon. Thanks.

    Aarron: Thanks for having me.

    Thanks goes to Andrew Marquis for transcribing this interview.

    Back to top

    Listeners feedback:

    We have two emails this week dealing with two totally unrelated subjects.

    Remote user testing

    Our first email is from Steve. He writes…

    Catching up on past podcasts, I listened to the episode on User Testing (#150). A method I’ve used that I haven’t heard tossed around much is remote user testing using a screen sharing program like GoToMeeting.

    I used this for usability testing of our Intranet and it has several advantages:

    • No need for people to come to central testing facility, or you to go to them.
    • The user is at their own computer, so more comfortable.
    • Ability to record the entire session (screen and audio) so others can look at it later.
    • Tester can conduct testing while in his underwear only (I didn’t do this, but you could.)

    What do you think of this method?

    Sounds interesting although it would not be my preferred approach.

    It’s easy to become a snob when it comes to usability testing and so let me make it entirely clear – any usability testing is better than none.

    If you have no budget for user testing, test on friends and family. If time is tight, test on a colleague sitting nearby.

    In the same way, if you are having trouble arranging sessions then use Steve’s approach. Something is always better than nothing.

    That said, I do have some concerns with remote testing. These include…

    • It sets a minimum bar of technical competency. A user has to be able to connect to the system in order to participate. I know this would have been beyond the capabilities of some test subjects I have worked with.
    • It is less personal. Face to face usability testing puts users much more at their ease and allows you to build a relationship that facilitates honest feedback.
    • It does not allow you to read non-visual signals. Users will often pull a face or shift their positions when they are frustrated. As a facilitator you need to be able to see these signals and ask what they mean.
    • You are not seeing exactly what the user is seeing. You can only see their screen. You cannot see other distractions such as TV in the background. You cannot see the position of their keyboard and mouse. You have a limited field of view.

    My preferred approach is to test in people’s homes. Not only are the users more relaxed, you also get a unique glimpse into their world. You see where they access the web, you learn about their home environment and even gain a better understanding of their character.

    However, we do not always live in a perfect world and so would definitely use remote testing if better options were not available.

    Finding a job

    Our second email is a rather despondent one from Andrew…

    I have one question, In the past you’ve talked about hiring new for staff, but as far as I can tell you’ve never discussed how to look for a job. I’m currently looking for a career in the industry, but I can’t get a resume to any company or even talk to someone of said company. Almost all the businesses I’ve approached (or at least tried to) either work from home, are no longer at that address, or no longer in business, and actually are just freelancers. And when I find a job posting online its for someone far more experienced then I am. I’m completely demoralized.

    You have my sympathy Andrew and I have to say its a tough time to to break into any new sector including web design.

    I am also probably not the best person to answer this question. I have been completely unemployable for some time now due to my ill defined skillset and opinionated character :)

    So, I am going to try something different with this question. If you have some advice for Andrew, post a comment below. That way we can get the Boagworld community helping each other.

    In the meantime here are a few random ideas from me…

    • Give up on the cold calling technique. Randomly contacting agencies is largely a waste of time. You have to get amazingly lucky to contact an agency who happens to be currently recruiting.
    • Try for an internship. Admittedly you will not get paid, but it is a foot in the door. You get a chance to improve your skills and also get to know the people in the industry within your area.
    • Be willing to move. There are jobs out there but they are often further a field.
    • Put yourself in a neat little box. Potential employers need to know what you do. Are you a designer, a coder or a server side developer? Companies don’t know what to do with people who know a bit about everything.
    • Start networking. The best place to find job opportunities is by attending conferences and meetups. Even if you cannot afford the conference itself, turn up at the parties and stand in the halls. Just get yourself out there.
    • Register with recruitment agencies. As an employer I hate recruitment agencies because they cost me money. However, we do still sometimes use them and it doesn’t cost you anything to be listed with them.
    • Ensure your website is perfect. The first thing I do when I look at a potential employee is check out their website. Their site has to be outstanding. It needs to look amazing, be well coded and rich with great content that demonstrates a passion for the web.

    Hopefully that helps Andrew and keep an eye on the comments for more advice.

    Back to top

    Series: Building A Better Web Application by Ryan Carson

    Ryan Carson: Hi I am founder of Carsonified a small web company in Bath, England. I am an American as you can probably tell, as for living in England I have been here about nine years. So a little bit of history about us real quick so you know who I am. I have a computer science degree and I have been involved in building four web apps and we are building a fifth truvay.com which will be released later in 2009, and we have sold two of our webapps dropsend.com and heyamigo.net. So the stuff that I am going to share with you today are lessons I have learnt the hard way basically as we have built web apps.

    So the first thing I want to talk about is the Admin area that you will build for your web app. What a lot of people don’t know is that the Admin area is really the key to good customer service. If you haven’t enabled really easy customer service then it makes it hard to actually please your customers when they have problems so the first one to make sure you build into your admin for your web app are one click refunds so if someone calls and complains and says hey I am having trouble this month I am really frustrated please help you want to be able to just go into the admin do a search for their email address, their name or their company or anything and bam one click and refund their last invoice and what this does is it gives you, it gives you the ability to just make them happy right away. With a lot of web apps these days on recurring billing you will probably be charging people 5,10,15, $20 a month so losing that amount of revenue in return for really making a customer happy is super important. So make that easy for yourself to refund that money.

    The second thing I would make it easy to do is have one click password reset that automatically sends out email with the new password, so with Dropsend it was really hard to reset people’s passwords and that was the number one request people had problems with, they couldn’t remember their password. So if I was to do it again what I would do is I would actually build the admin so I could forward an email from somebody presuming they had sent it from the email address of the account, forward it into Dropsend or the admin and it would automatically know that what it needed to do is reset the password for that email and then it sends out a new one so literally you do not even have to visit the admin area to reset someone’s password you just forward an email that would be amazing, so that’s the way I would do it next time.

    The next thing I would do is also doing a one-click resend invoice. So a lot of people they don’t understand they can go into their "My Account" area of a web app to see their past invoices and what they will do is they will just email you and say hey you know I need last month’s invoice. If it is hard for you to find that or send that it is going to make you less likely to help that person so I would do a search on the email address show a list of invoices bam one click and it emails them a pdf version of the invoice. That’s another, that leads me onto another area that I would like to talk about that is invoicing. If you are doing recurring billing sort of every month billing your customers make sure that you are not re-inventing the wheel I would recommend a web app called Spreedly.com and what it is basically it is a web service for recurring billing they have done all the hard work, written all the code, the code for the Dropsend recurring billing was at least I think 1200 lines of PHP and it was good solid code but it was really hard and painful to write. So I would recommend don’t re-invent the wheel use a service like Spreedly because it is making calls to an API if later you decide you don’t want to use a service like Spreedly any more that layer has been abstracted out so you could replace it with your own billing system or another one and it won’t kill you, but I would say hands down don’t rebuild reoccurring billing it is a real pain in the ass.

    The last tip I would say about your admin area is make sure that it is easy to give your customers credits. you want to be able to login search for an email address and just give them, hey I want to give them five bucks towards next month, ten bucks just to make them happy and you will have lots of happy customers. So that is my five minutes of tips, thanks Paul for letting me be a part of this. Take care Bye.

    Back to top

    158. Home

    On this week’s show: We share the highlights of SXSW, discuss home working, and interview Rob Borley about project management.

    Play

    Download this show.

    Launch our podcast player

    Housekeeping

    Headscape still recruiting!

    Headscape is still recruiting. We are looking for an enthusiastic, talented developer to join our team, working from of our offices in Hampshire. For more information see the job advertisement on Boagworld.

    Back to top

    News and events

    The best of SXSW

    Well, SXSW is over and I am back in the UK. But what happened at the conference? What was the big news this year?

    That is actually a hard question to answer. There is so much at SXSW that it is almost impossible to get a sense of everything that is going on. Even if you could attend every panel that isn’t always where the real action takes place.

    The real conference often happens at the parties and in the corridors. In fact, more than one spontaneous panel was started via Twitter, thanks to official panels being full.

    Panels this year ranged from the downright dull to all out flame wars! One that I unfortunately missed was "Is Spec Work Evil!". However, Marcus attended and tells me it was particularly fiery. Personally, I am very much against speculative work as I have said before. However, not everybody would agree and the panel seemed to reflect this diverse opinion.

    One panel I did make was Paul Annett’s amazingly inspirational talk on Easter Eggs and design twists. The talk focused on the little things you can add to your site to make users go ‘oooo that’s clever’.

    Too often I neglect such ‘bells and whistles’ in favour of usability and accessibility. Paul demonstrated how these different priorities can sit side by side without compromising each other. He showed some great examples including the hidden arrow in the FedEx logo and the vines on the Silverback website.

    fedex logo

    The final panel I want to mention is ‘Being a UX Team of One‘ by Leah Burley of Adaptive Path. To be honest the title of this one was a little misleading (at least from my perspective).

    What I took away from this session was that design should not be a solitary activity, solely reliant on the creative inspiration of one individual. Leah seemed to be arguing for a more collaborative approach especially at the wireframe stage. She proposed that all of those involved in the project should sit down together and hammer out the wireframe designs.

    This addressed two separate problems we have been having at Headscape

    • The developers concerns at not being involved early enough in the process.
    • The question of who should do wireframing – the designer or the IA person.

    Best of all Leah’s presentation was very pragmatic. She provided lots of practical approaches that encourage idea generation and collaboration. I highly recommend listening to the podcast of this when it is released.

    Browser testing and IE6

    In other news, there seems to have been a lot written about browsers this past week. Three stories in particular caught my eye…

    • .net Magazine seems to have hopped on the ‘dump IE6′ bandwagon – My opinion is the same as that of Jeremy Keith as expressed in last weeks show. It is not a matter of dropping IE6. We should instead being deciding whether we wish to offer it the same level of support as modern browsers. I am entirely in favour of providing IE6 with a basic stylesheet that avoids its shortcomings. However, I dislike the idea of dropping it entirely.
    • Microsoft has released SuperPreview this week that allows Windows users to test different versions of IE simultaneously. I have to say this looks like an impressive tool. It allows you to view IE6 and IE7 side by side. It also has many other tools that may also be useful. Support for IE8 and other browsers will follow and although it is currently in beta, I think it will quickly become an indispensable tool for Windows based web designers. Just a shame there is no mac support!
    • Finally, Sitepoint have written a brief outline of how to create the perfect browser testing suite. Ideally for those starting out it lists various online browser simulators, virtual machines and desktop browser emulators.

    Browser testing continues to be a pain in the neck and I for one would be willing to pay for a decent way of streamlining this whole process. This is especially true now that IE8 has been officially released and we have another browser to add into the mix.

    Screenshot of Superpreview

    A simplicity case study

    A few weeks ago I wrote about the importance of simplifying your website. Well, this week Gerry McGovern has written the perfect case study to support the argument I was putting forward.

    Removing poor quality content increases customer satisfaction‘ talks about how the Microsoft website consists of a staggering 10 millions pages. Of those pages 3 million have never been viewed!

    The post goes on to explain how the Microsoft Office team took a different approach with their site by removing irrelevant pages. According to McGovern…

    By weeding the garden, the top task pages became easier to find. But just as importantly it became harder to find a minor task page when you were looking for a top task page.

    In short, removing pages reduced noise. Disturbing though it sounds, I think we could all learn something from Microsoft’s example.

    An introduction to Microformats

    My final post today comes from Richard Rutter’s blog. It is basically an introduction to Microformats aimed at the non-geek. He wrote the post because he recently found himself trying to explain microformats to a client and could not think of a good post that covered the subject from their perspective.

    Personally, I am not sure it is necessary to tell a client you are implementing Microformats. The cost of adding them is so small and the benefits so hard to explain, that you maybe better off just doing it.

    That said, this is an excellent post and if you are struggling to understand the point of Microformats, this is certainly worth reading.

    Back to top

    Interview: Rob Borley on Project Management

    Paul: So, joining me today is Mr. Rob Borley. Hello Rob.

    Rob: Hi Paul, how are you doing?

    Paul: Very well indeed. Good to have you on the show. It’s been a little while.

    Rob: It has, It has. It’s weird hearing the show above you, um rather than being below.

    Paul: Oh yes, because you sit upstairs, don’t you?

    Rob: Indeed.

    Paul: Do you actually hear it?

    Rob: I do. It’s like have a little base bin ?

    Paul: Awh. So, um, we have kind of been thinking for a little while that we need to get someone on the show to talk about project management. And the idea was we’d get some high profile web design project manager to come in and talk about web design project management. Then I realised, um, that I can’t actually think of any. You know, I really don’t know of any kind of web design project managers out there, other than obviously the people that work at Headscape.

    Rob: Well, maybe there’s a gap in the market.

    Paul: I think there is a gap in the market.

    Rob: (unintelligible) celebrity project manager.

    Paul: Well I think that’s somewhat of an oxymoron, but setting that aside, lets shift around a bit, yeah, so, um, so we thought, lets get you on the show. Um, now, you’re quite and interesting case because you started of as a techie.

    Rob: Yes.

    Paul: And you became a project manager.

    Rob: Yes.

    Paul: And, so, um, let’s start by talking about the role of project manager. How would you describe your core role? What is it that you do? I should know this I guess.

    Rob: Well, you mean other than manage projects.

    Paul: Ok, you just have to make a joke out of it. But you know what I’m getting at.

    Rob: Yeah yeah. I mean, I guess, um, the main thing that we do is shovel shit, really. We deal with crap. You know, the main thing project manager would do is a filter between clients and the production team for the project. I mean, there are a couple of stages I guess. So you’ve got the planning part of the job, which is essentially working out what it is you need to do, um, making sure you got the results to do it, plotting a nice time line so they can all fit as far as having deadline. And then you’ve got the people said, because really project management is a people job. You need to know how to get the most out of all the people that are in your project team, um including the client. You need to include the client in your thinking, always. Yah, that’s essentially what we do.

    Paul: Yah. It’s a people person thing. I always thought you were so charasmatic. Ok, so, I mean, I guess the question is, if you look at the kind of, if you look at Headscape, and the way that we’re organised, we’ve got four developers, four designers, and three project managers. I mean, that’s a lot of project managers. And, you know the question is, why, why have project mangers at all? Why couldn’t the designers and the developers do the job? Why couldn’t it be spread across multiple people? Justify you exsistance, Rob.

    Rob: Yeah, this question kind of makes me nervous here. I feel like I’m re-interviewing for my own job. Not that I interviewed in the first place, but, I guess in one sense, if you were in a small project environment, you could almost get away with one person. If, you know, its a one person job, you could get away with them managing themselves for a limited amount of time. Um, but, as soon as you get beyond jobs which are more than one person, um, and go on for an extended period of time, you start needing to provide some glue to stick things together. You need someone whose got an overview of everything that’s going on. You know, the developers have got a very developer mindset about the way things happen. Designers are the same way, they know about the design stuff. Um, but actually translating what the client wants and feeding that into both areas and bring them together is what’s missing, if you don’t have a project manager.

    Paul: So, to some degree, project management becomes necessary with scale. The bigger the projects, and the more complex the projects, then the more a need for a dedicated project manager.

    Rob: Yeah, definitely. I mean, I guess the real role of a project manager in these situations is the facilitator. You’ve got all of these tools which are basically your resources, your developers, your designers, um, and you need to be able to enable them to work effectively together to produce what the end product is going to be.

    Paul: So here’s a question that I didn’t pre-give you, in advance, which is always the best type. Why, why, why become a project manager? What made you – because you were heading up our technical development team, you were, you know, you were doing very well. Why did you feel the need to get involved in what you call shit shoveling?

    Rob: Well, I think my main motivation was, Headscape was growing, and we started employing all of these younger, more dynamic, much more talented, better looking developers, that were basically going to show me up. So I figured that before I got shown in true light that I was going to need to move somewhere else. Um, no, well that’s partly true. Really, I think, its the people’s aspect that I’m really interested in. A good project manager is someone who is able to understand how his resources or how her resources work and how your clients work, and joining the two together. Um, while I quite like writing code really, I’m not passionate about it. So that side of it, you know, I reached as far as I wanted to go, and I really enjoy the people thing.

    Paul: Ok. So what other, I mean, what other kind of characteristics do you think make a good project manager, obviously the people skills you talked about, what other, I mean if there are other people out there going well actually I’m not that passionate about coding, or I’m not that passionate about design, but I am passionate about the web, I do like the web design process, perhaps project management is the way I ought to be going. You know, what skills, what characteristics do they need, what personality traits do they need?

    Rob: I think well, you need to be able to plan. Um, you know, planning is very very important. If you plan well, then your project will usually go well.

    Paul: I like the cornification in that.

    Rob: You have to be able to predict the future is helpful.

    Paul: Yes.

    Rob: A major part of what we de in the planning stages is assessing risk. You know, so, we’ve got what we’re starting with, we’ve got what we want to achieve, and we’ve got a time scale, now we need to work out what things might appear that are unforeseen, which are going to affect us reaching the time scale. So being able to foresee the future is helpful. Um, and so planning, being quite analytical and thorough. The logical background I have from being a programmer, a developer, is really helpful because you have to approach project management in a very analytical way, to make sure you don’t miss things. So there’s that side of it. And then there’s communication skills. You not only need to be able to communicate with a client affectively so they show that you understand what they want, um, and they understand where you are with the project, and they’re happy because a happy client makes everyone happy. But you also then need to communicate that with the various personalities in your team. You know, whether thats the developers locked up in a dark room with no social skills, or the crazy charismatic designers who…

    Paul: You’ve just gone with stereotypes that so don’t apply. If I look at our team, no offense to our designers, they’re the ones that sit in the darkened room with their nose right pressed against the screen. And the developers are the ones that are crazy and never do any work.

    Rob: (unintelligible) something about reading personalities. No, but you see my point. You’ve got these almost extremes, especially in the web, I guess, in the web world, you’ve got these extremes of personailities which somehow you need to be able to communicate with and put it all together and so, yeah, that’s an important skill. I think the third area, is to be quite relaxed about life. Because things will go wrong and do go wrong, it doesn’t matter how well you plan and how good you are at predicting the future. Stuff will appear that is completely unforeseen and will completely throw (unintelligible). And everyone gets really upset and people will shout at you and it goes a bit nuts. Um, and if you go nuts as well, you project team falls apart, because they look at you as the calm rudder in the storms of life. I can feel my other project manager buddies laughing at me, um, but if you’re calm and you can not get stressed at that but actually see, try and find a clear path through a very stressful situation, then really helps.

    Paul: I would so be the worst project manager in the world. I’ve got the attention span of a newt, I’ve got no organisational abilities and I get stressed at everything. So overall, I think I’d fail.

    Rob: Yeah, stick to web celeb.

    Paul: Yes, I’ll come up with some other title that sounds good. Um, ok, so you talked about this really is, I can honestly say, a foreign area to me. Right? You talk about planning a project upfront. I’m not a planning person. Right? And there seems to be so many variables involved in a project and so much as you say, that can potentially go wrong. How do you plan it? I mean, you know, the kind of thing that you always talk about, when you talk about project management is endless gantt charts that seem to be outdated in about 5 minutes, sort of kicking a project off. How to you effectively plan a project?

    Rob: Um, well, we do use a gantt. We always start a project with a gantt. And, um because it seems like thats what project managers are supposed to do, so we justify the time with a gantt. Um, but you do need, um, I think assessing risk is something that is vital in successful project management. Its something that we’ve been doing at Headscape, um, increasingly more over the last year or so otherwise this need to actually spend time highlighting what could actually go wrong here. So, you look at, I’m not going to be able to think of any examples now, but a particular, let’s say you building a shop or something. So potential things which could delay that project would be: the client not getting around to telling you what the products are on the shelf and content population is a big risk on meeting a project deadline, because it is out of your control. So, its like, I need the content by this date, and he needs to put the content in by X date. If the client doesn’t do it, there’s nothing you can do about it.

    Paul: I’m guessing integration must always be a big risk. Integrating with third party applications.

    Rob: Exactly, so if you’ve got some sort of third party database or a web service you’ve got to pull in, something that you’ve done a bit before, but you don’t know anything about, that’s a risk. Because you can guesstimate what’s going to happen, but its unforeseen. And so, the trick is basically, to find all the tasks that have these risks and then multiply (unintelligible) an hour by some random number. And then make the rest up as you go along.

    Paul: So what about once the project gets going, how, what techniques and tools maybe do you use for monitoring and controlling the process and trying to keep on top of everything.

    Rob: Yeah, I mean, there are lots of tools out there, obviously, lots of funky web-based ones, um, there is no substitute for talking to you team. Um, trying to (unintelligible) email or basecamp or something is impossibly without talking to you team. So, communicate. It’s a big part of what we do. You have to talk to the people doing the work, you have to talk to the clients, um you have to keep the lines of communication open. Um, but as far as actually keeping track of what’s going on, we do use basecamp, um which is great for managing lists, basically, you manage lists. So from our gantt shell, we’ll break it up into a series of tasks if you like, wide areas, um, and then, (unintelligible) ask people to add comments to them and take them off and then we’ve got kind of an overview of where our project is. Um, and hopefully from there, and when we’ve got the gant shell, we’ve got some dates, some milestones and reminders like you should have done this by then, um and so, you use that to kind of keep track of where you are.

    Paul: Cool. What about, so that’s kind of dealing with the internal side of things. What about when it comes to the client, I mean, you talked about, you said earlier, a happy client makes everybody happy kind of thing. So what makes a client happy? What are the things that really, or perhaps turn it around the other way, what are the things that really piss of a client and where can it really go wrong?

    Rob: This is really where the people side of it really comes in because every client is different. Some clients want you to talk to them for five hours a day, hold their hand, you know, spoon feed them, and some clients just want to know when it’s finished. So initially, when you’re kind of trying to assess your project team, if you like, your resources and what you’ve got, assessing the personality of your client early on, will really put you in a good place. Um, but, I guess, general principles, if you’re honest, it helps. Um, so, be realistic about what you’re telling your client is going to happen. Don’t promise the Earth by yesterday. Because then you won’t deliver and then they’ll get upset. If there’s going to be a problem, if things have slipped for some unknown reason, then tell them as soon as you know. Tell them as quickly as you possibly can. Um, manage their expectations is kind of the phrase that we use a lot. You gotta manage you clients expectations so that they’re not expecting something that you can’t deliver. And um, and then that limits the amount of upsetness that they get.

    Paul: Slippage is a big one, isn’t it? This kinda whole area of things like, you know problems you kinda face, things, like slippage, scope creep, non-delivery, I mean, how do you have any kind of broad techniques for dealing with these kinds of things, or is it just kinda communications thing again.

    Rob: It’s mainly I think a communication thing again. Um, part of the planning stage is trying to asses these risks and so you try and build in contingency to cope with those, and if you’re building enough contingency, you deliver the project early and that makes everyone really happy, even if its a long project, you deliver it early, you’ve exceeded their expectation also. Um, so I think, if somethings going to slip, I think you should say you’ve got to be honest. Sometimes things are just out of your control, so you’re two weeks before the end of a project, you in the middle of snagging, your lead developer goes down with appendicitis. There’s nothing you can do about that, and so you just need to communicate with the client and hope they take it well.

    Paul: So wishing everything works out, I’m loving that approach. Ok, so, um, let’s finish of with a piece of generic advice. Either people starting out in project management or those that have had project management foisted upon them. You know, whats the kind of one piece of advice that you would leave for people?

    Rob: Get to know your team. I think that’s the main thing I would say. Um, its kind of like, when you drive you car, you’re environment is a very organic, dynamic thing, you know what it really what’s going to happen and the only thing you’ve got to get you through it is that you understand you car. You know almost instinctively how it works, how to drive it it, if you get to that situation with your team, then whatever the project throws at you, you kind of, you can deal with it. If you understand how you client is going to react to a certain situtation, you can intincfully deal with it. And it keeps the stress levels low. You need to find ways of managing your stress levels.

    Paul: There you go, that’s great advice. Thank you vert much for that, it was wonderful. I really appreciate you coming on the show.

    Rob: My pleasure.

    Thanks goes to Meredith Marsh for transcibing this interview.

    Back to top

    Feature: Home Working

    I was recently contacted by a friend of mine Marieke Guy about writing a guest post for her blog on remote working.

    I have been working at home for over 7 years now and am a great believer in the benefits. However when I actually sat down to write the post, I realised just how long it has taken me to find the right way of working.

    As a large number of people who listen to this podcast work from home, I thought I would share my experiences to date and my hopes of where remote working will take me in the future.

    The reality of home working

    Back to top

    10 criteria for selecting a CMS

    Choosing a content management system can be tricky. Without a clearly defined set of requirements you will be seduced by fancy functionality that you will never use. What then should you look for in a CMS?

    I have written about content management systems before. I have highlighted the hidden costs of a CMS, explained the differentiators behind the feature list and even provided advice for CMS users. However, I have never asked what features you should be looking for in a content management systems. That is what I want to address here.

    Illustration of a sales man selling a CMS the client does not need.

    When I left home for University my mother taught me a valuable lesson. If you want to save money, never go grocery shopping when you are hungry and always write a list. If you don’t you will be tempted to buy things you do not need.

    The same principle is true when it comes to selecting a content management system. Without a clearly defined set of requirements you will be seduced by fancy functionality that you will never use. Before you know it you will be buying an enterprise level system for tens of thousands of dollars when a free blogging tool would have done.

    How then do you establish your list of requirements? Although your circumstances will vary there are ten areas that are particularly important.

    1. Core functionality

    When most people think of content management, they are thinking of the creation, deletion, editing and organizing of pages. They assume all content management systems do this and so take the functionality for granted. However that is not necessarily the case. There is also no guarantee that it is done in an intuitive fashion.

    Not all blogging platforms for example allow the owner to manage and organize pages into a tree hierarchy. Instead the individual ‘posts’ are automatically organized by criteria such as date or category. In some situations this is perfectly adequate. In fact this limitation in functionality keeps the interface simple and easy to understand. However, in other circumstances the absence of this functionality can be frustrating.

    Blogger Homepage

    Consider carefully the basic functionality you need. Even if you do not require the ability to structure and organize pages now, you may in the future. Be wary of any system that does not allow you to complete these core activities.

    Also ask yourself how easy it is to complete these tasks. There are literally thousands of content management systems on the market, the majority of which offer the core functionality. However they vary hugely in usability. Alway look to test a system for usability before making a purchase.

    The editor is one core feature worth particular attention.

    2. The editor

    The majority of content management systems have a WYSIWYG editor. Strangely this editor is often ill considered, despite the fact that it is the most used feature within the system.

    The editor is the interface through which content is added and amended. Traditionally, it has also allowed the content provider to apply basic formatting such as the selection of fonts and colour. However more recently there has been a move away from this type of editor to something that reflects the principles of best practice.

    The danger of traditional WYSIWYG editors is two fold. First, they give the content provider too much design control. They are able to customize the appearance of a page to such an extent that it could undermine the consistence of design and branding. Second, in order to achieve this level of design control the cms mixes design and content.

    The new generation of editors take a different approach. The content provider uses the editor to markup headings, lists, links and other elements without dictating how they should appear.

    Wordpress WYSIWYG

    Ensure your list of requirements include an editor that uses this approach and does not give content providers control over appearance. At the very least look for content management systems that allow the editor to be replaced with a more appropriate solution.

    The editor should also be able to handle external assets including images and downloads. That brings us on to the management of these assets.

    3. Managing assets

    Managing images and files are badly handled by some cms packages. Issues of accessibility and ease of use can cause frustration with badly designed systems. Images in particular can cause problems. Ensure that the content management system you select forces content provider to add alt attributes to imagery. You may also want a cms that provides basic image editing tools such as crop, resize and rotate. However, finding such a cms can be a challenge.

    Also consider how the content management system deals with uploading and attaching PDFs, Word documents and other similar files. How are they then displayed to users? What descriptions can be attached to the files and is the search capable of indexing them.

    4. Search

    Search is an important aspect of any site. Approximately half of users will start with search when looking for content. However, often the search functionality available in content management systems is inadequate.

    Here are a few things to look for when assessing search functionality:

    • Freshness – How often does the search engine index your site? This is especially important if your site changes regularly.
    • Completeness – Does it index the entire content of each page? What about attached files such as PDFs, Word documents, Excel and Powerpoint?
    • Speed – Some search engines can take an age to return results. This is especially common on large sites.
    • Scope – Can you limit the scope of search to a particular section of the site or refine search results once returned?
    • Ranking – How does the search engine determine the ranking of results? Can this be customized either by the website owner or by the user?
    • Customization – Can you control how results are returned and customize the design?

    The issue of customization is one that goes far beyond search.

    5. Customization

    I have been unfortunate enough to work with content management systems that are completely inflexible in their presentation.

    Illustration demonstrating the inflexibility of some CMS

    The presentation of your content should not be dictated by technology. It is simply not necessary now that we have techniques for separating design and content. Unfortunately like web designers, many content management providers have failed to adopt best practice and their systems produce horrendous code. This places unreasonable constraints on design and seriously impacts accessibility.

    You need a content management system that allows flexibility in the way content is returned and presented. For example can you return news stories in reverse chronological order? Can you display events on a calendar? Is it possible to extract the latest user comments and display them on the homepage? It is flexibility that makes a cms stand out.

    Talking of user comments, it is worth mentioning all forms of user interactions.

    6. User interaction

    If you intend to gather user feedback, your cms must provide that functionality or allow third party plugins to do so. Equally, if you want a community on your site then you will require functionality such as chat, forums, comments and ratings.

    As a minimum you will require the ability to post forms and collect the responses. How easy does the cms make this process? Can you customize the fields or does that require technical expertise? What about the results? Can you specify who they are emailed to? Can they be written to a database or outputted as an excel document? Consider the type of functionality that you will require and look for a cms that supports that.

    Also ask what tools exist for communicating with your customers. Can you send email newsletters? Can recipients be organized into groups who are mailed individually? What about news feeds and RSS?

    Finally consider how you want users to be managed. Do you need to reset passwords or set permissions? Do you need to be able to export user information into other systems?

    But it is not just user permissions that may need managing. You also have to consider permissions for those editing the site.

    7. Roles and permissions

    As the number of content providers increase, you will want more control over who can edit what. For example, personnel should be able to post job advertisements but not add content to the homepage. This requires a content management system that supports permissions. Although implementation can vary, permissions normally allow you to specify whether users to edit specific pages or even entire sections of the site.

    Illustration showing the consequences of not having a permissions system

    As the number of contributors grows still further you may require one individual to review the content being posted to ensure accuracy and consistent tone. Alternatively content might be inputed by a junior member of staff who requires the approval of somebody more senior before making that content live.

    In both cases this requires a cms that supports multiple roles. This can be as simple as editors and approver, or complex allowing customized roles with different permissions.

    Finally, enterprise level content management systems support entire workflows where a page update has to go through a series of checkpoints before being allowed to go live. These complex scenarios require the ability to roll back pages to a pervious version.

    8. Versioning

    Being able to revert to a previous version of a page allows you to quickly recover if something is posted by accident.

    Some content management systems have complex versioning that allow you to rollback to a specific date. However, in most cases this is overkill. The most common use of versioning is simply to return to the last saved state.

    Although this sounds like an indispensable feature, in my experience it is rarely used expect in complex workflow situations. That said, although versioning was once a enterprise level tool it is increasingly becoming available in most content management systems. This is also true of multi-site support.

    9. Multiple site support

    With more content management systems allowing you to run multiple websites from the same installation, I would recommend that this is a must-have feature.

    Although you may not currently need to manage more than a single site, that could change. You may decide to launch a new site targeting a different audience.

    Alternatively with the growth of the mobile web, you may create a separate site designed for mobile devices. Whatever the reason, having the flexibility to run multiple websites is important.

    Movable Type admin system

    Another feature that you may not require immediately but could need in the future, is multilingual support.

    10. Multilingual support

    It is easy to dismiss the need to support multiple languages. Your site may be targeted specifically at the domestic market or you may sell a language specific product. However think twice before dismissing this requirement.

    Even if your product is language specific, that could change. It is important that your cms can grow with your business and changing requirements.

    Also just because you are targeting the domestic market does not mean you can ignore language. We live in a multicultural society where numerous languages are spoken. Being able to accommodate these differences provides a significant edge on your competition.

    That said, do think through the ramifications of this requirement. Just because you have the ability to add multiple languages doesn’t mean you have the content. Too many of my clients have insisted on multilingual support and yet have never used it. They have failed to consider where they are going to get the content translated and how they intend to pay for it.

    Conclusions

    Features are an important part of the CMS selection process, but they are not everything. It is also important to consider issues like licensing, support, accessibility, security, training and much more.

    I leave you with a word of warning – Don’t let your list of requirements become a wish list. Keep your requirements to a minimum, but at the same time keep an eye on the future. Its a fine line to walk. On one hand you don’t want to pay for functionality you never use. On the other, you do not want to be stuck with a content management system that no longer meets your needs.

    This has been an extract from the Website Owners Manual - now available as an ebook and for preorder in print.

    10 ways to Battle Site Bureaucracy

    Running a large institutional website is frustrating. Your site is often held back by internal politics and bureaucracy. Let me show you 10 ways to cut through the crap and get results.

    My recent post ‘10 harsh truths about corporate websites‘ generated a huge number of comments both on my own blog and on Smashing Magazine. I seemed to tap into an undercurrent of frustration that exists within the industry.

    However, although there was a lot of agreement about the points I raised, there was also resignation. There was a feeling that little could be done to overcome these problems because institutional websites are too entrenched in bureaucracy and politics.

    Although I can sympathise with this position and have myself suffered from the problem, I am not one to give up! Over the last decade of working on these sites, I have developed a number of techniques which (sometimes) help to smooth their evolution. Hopefully they will help you too.

    1. Educate and inform

    At the heart of any technique for dealing with politics and bureaucracy has to be education.

    Although there are occasions when people are just ‘trying to be difficult’, in most cases their objections are based on ignorance.

    You cannot expect people to be as knowledgeable as you about the web. If you want people to make informed, sensible decisions you must educate them.

    Education is also not just about giving them the background to a specific decision so they understand ‘why you are right’. It is about increasing your organisations general understanding of the web.

    Run workshops, publish email newsletters, do anything that informs people about the latest web innovations. Increasingly I am invited into organisations to run short seminars on everything from accessibility to facebook! This kind of ongoing education means people are better informed when tough decisions need to be made.

    2. Hold stakeholder interviews

    One technique that we find very effective at Headscape are stakeholder interviews.

    Stakeholder interviews involves meeting individually with anybody who has a ‘stake’ (interest) in the website. This is typically members of the marketing and IT teams, as well as departmental heads and senior management. However it should also include suppliers, customers and users of your website.

    These one-to-one meetings provide two opportunities…

    • Requirements gathering – It is easy for website owners to live in isolated bubbles, separate from the rest of the organisation. These meetings provide an opportunity to understand the real needs and objectives of others within the business. It will highlight ways that your website can help, which you might not have previously considered.
    • To be inclusive – Stakeholder interviews offer a ‘political benefit’ as well. By meeting with people individually they feel included in the process. They feel their opinions are valued and listened to (which they should be!). People are much less likely to object if they have been consulted before a decision is reached.

    People often complain about the website in stakeholder interviews. Allow them to do this and avoid becoming defensive. They will feel more favourably towards you and your website, if you listen to their concerns. We all like to be heard.

    3. Avoid group committee meetings

    The key to stakeholder interviews is their one-to-one nature. Group meetings can be very destructive. This is for a number of reasons…

    • The need to defend – In large organisations that have internal politics, everybody feels the need to defend their own ‘turf’. If somebody criticise the website, you are forced to defend it to ‘save face’ in front of others. Equally others feel the need to defend their own positions for the same reason.
    • A tendency to compromise - When two individuals in a group reach an impasse, the others try to find a compromise. This kind of ‘design on the fly’ inevitably leads to a bland solution. It will neither offend or inspire anybody. Unfortunately, to create a successful website you need to make tough choices that some will not like. A group approach does not lend itself to this.
    • A loss of control – It is easy for you to loss control in a group meeting. One-to-one meetings work better because you can divide and conquer. Only you know what the other stakeholders said. This puts you in charge and allows you to ‘cheery pick’ the feedback you receive. In a group meeting things can easily get out of hand and decisions are made without your buy-in.
    • The dominant individual - Every group has one or two dominant individuals. These are the people who bounce the rest of the group into agreeing with them, forcing their agenda through. A dominant individual drowns out quieter members, who become resentful later that nobody listened to them. Meeting with people individually prevents this because the dominant individuals cannot force their point of view on others or overwhelm quieter ones.

    One cannot expect a larger organisation to run its website without some form of committee. However, there is no reason why that committee needs to meet as a group.

    4. Target your influencers

    Talking of dominant individuals, another successful tactic is to target influencers.

    An influencer is somebody that others respect and follow. Their opinion is incredibly valuable and if you can sway them to your cause, others will fall into line. However, be careful not to confuse dominant people with influencers. A dominant person will ‘bully’ others into publicly agreeing with them. An influencer will fundamentally alter somebody’s attitude.

    Identify who influences your decision makers and speak to them personally. This person might not even be a decision maker themselves, but they carry enough clout to make them worth your time.

    When you meet with your influencers, really listen to what they have to say. They often have valuable insights which may change your strategy significantly. Do not go into a meeting with an influencer simply intent on pushing your own agenda. Instead try and shape your approach around their perspective.

    If you get an influencer enthusiastic about your project it can make a huge difference.

    5. Use third party experts

    A variation on the influencers technique is to back up your ideas with third party expert opinion. This can be done in two ways…

    • Reference the work of a third party expert – For example, if you wish to discourage internal stakeholders from overwhelming users with options on the homepage, you might refer them to Steve Krug or Jakob Nielsen who have both written on the subject.
    • Hire a third party expert - I often find myself brought into companies simply to confirm what in-house staff have already been saying. Unfortunately, decision makers often doubt the opinion of their web team because they either undervalue them or feel they are pushing a hidden agenda. An independent expert can add creditability to your opinions.

    Of course, for this approach to work the stakeholders need to respect the expert. There is no point referencing Steve Krug or hiring Jakob Nielsen, if the decision makers have never heard of them. It is often necessary to sell the credibility of your expert first.

    6. Rely on evidence, not opinion

    Sometimes it is better to avoid personal opinion entirely (even if that is the opinion of an expert). In such cases statistics can be your friend.

    Nothing is more powerful for driving home a point than referring decision makers to Google Analytics. However web stats are not the only evidence you can draw upon. Others include…

    • Surveys and polls are an excellent way of getting feedback from your users that can then be presented to decision makers.
    • Twitter search and Google Alerts can be used to gauge how people view your site and brand. These can be powerful testimonials to present decision makers.
    • Heat maps can be used to take some of the subjectivity out of design.

    Of course one of the most powerful evidence you can present is the results of usability testing.

    7. Focus on the user

    As website owners we know that a successful website is user focused. However, not all our decision makers will understand this and even those who do may get ‘distracted’ sometimes.

    It is therefore important to constantly move our decision makers away from their own personal preferences and back on the needs of users.

    User testing is one way of doing this. Being able to show decision makers how real users interact with your website is incredibly powerful. It helps them empathise with the needs of users rather than thinking only about their own agenda. Play them video clips of users interacting with your site or at the very least quote them the feedback of users.

    However, even if you involve decision makers in user testing, they can still get caught up in their own agendas. One gentle way of preventing this is to word your questions carefully. When you need a decision makers response to something don’t ask…

    What do you think?

    Instead ask them…

    How do you think users will respond to this?

    This will keep them focused on the needs of users.

    8. Control the feedback

    As well as wording questions carefully there is also a need to control the feedback you receive. This is important if you want the decision makers to make considered decisions.

    Take for example design sign off – never ask a decision marker if they like a design. It is too broad a question that will lead to a plethora of uninformed and ill considered responses. Instead ask them more specific questions such as…

    • Does the design conform to the brand guidelines?
    • Does the design meet the needs of our users?
    • Does the design emphasis the right content?
    • Does the design have a clear call to action?
    • Does the design fulfil our business objectives?

    This prevents the decision maker from falling back on their gut reaction (i like it / I dislike it). It forces them to focus on the issues that define whether the design is successful or not and ignore personal preference for specific colours or layout.

    Of course, sometimes you will not like the answer to these specific questions. When that happens you need to ask why.

    9. Ask why

    This is probably the most powerful of all the techniques I have listed here and yet by far the simplest.

    When you face opposition to your plans, always ask why. Too often we switch to defensive mode and focus on better communicating our own position rather than understanding the opinion of the person opposing us. This is a mistake.

    The question why is powerful for three reasons…

  • It informs – Often the objection raised initially is not the true underlying issue. By asking why you get to the root of the problem and that allows you to offer alternative solutions. Asking why ensures you have all the information required to deal with the issue.
  • It can confound – Most of us make decisions based on an intuitive leap. We do not always think through our decisions and so find it hard to articulate the underlying reason. By asking why you force people to stop and consider their logic. When they struggle to express the underlying reasons, they weaken their position.
  • It shows interest – By asking why you allow them to have their say. You demonstrate an interest in their opinion and establish empathy with their point of view.
  • Ultimately asking why avoids the disagreement from turning into an argument with entrenched position.

    10. Avoid confrontation

    I avoid confrontation at all costs. Going head-to-head with somebody especially in front of their colleagues achieves nothing. You can rarely get somebody to shift their position through confrontation.

    Once a disagreement escalates into a confrontation, nobody can afford to ‘lose face’ by backing down. It becomes a matter of ego, where pride dictates the outcome. Your website will almost certainly be caught in the cross fire.

    A better approach is to agree. The word yes can be immensely powerful. Whenever somebody suggests something to me, no matter how stupid, I will do the following…

    • Acknowledge and thank them for their input.
    • Say yes we could do that.
    • Go on to explain the consequences if we did.
    • Offer an alternative which could achieve the same aims.

    In short I tend to go around problems rather than bashing my head against them. I always look to work with others rather than against them.

    Conclusions

    So there you go, 10 techniques for battling site bureaucracy. I do not claim these techniques are foolproof. Neither do I suggest they are always appropriate. However, they are useful techniques in your arsenal which you may want to call upon from time to time.

    Finally, this is not a definitive list. I could have written more but then it wouldn’t have been a ‘top ten list!’ However, I would be interested to hear what works for you. Post your techniques in the comments.

    A demonstration of graded browser support

    In my post ‘Effective Browser Support‘ I explained how we should not be looking to make sites identical in all browsers, but rather focusing on usability and accessibility. In this post I demonstrate how that works in practice.

    I recently launched a new Headscape service called the Consultancy Clinic. As part of this launch I created a small single page website. Let me use this site to demonstrate how graded browser support can work.

    Remember – the idea of graded browser support is to support all browsers so that your site is usable, accessible and at least reasonably attractive. With that in mind lets start with the lowest common denominator.

    Starting with the basics – HTML

    All web browsers can support HTML. So as a bare minimum I needed to ensure my new website was usable and accessible in raw HTML format. To test this I used the free Lynx Viewer and it returned this…

    Consultancy Clinic site viewed in Lynx

    So far so good. But what about those browsers who think they understand CSS but don’t render it properly?

    The pretenders

    Unfortunately when it comes to CSS support things are not black and white. Although some browsers support styling flawlessly, others think they know what they are doing when they do not.

    Poor implementation of CSS is the curse of older browsers. Browsers like Netscape 4 and IE 5 offer very limited CSS support and badly implementing what it does provide.

    Instead of ignoring these browsers I create a basic CSS file which does some simple formatting. Instead of compromising the design to accommodate the limitations of these browsers, I deliver a simplified version which is usable and accessible.

    Consultancy Clinic Website viewed in IE 5

    As you can see the design focuses on some simple layout and typography. That way it avoids anything IE 5 may have trouble displaying correctly.

    Dealing with IE6 and above

    The next step was to create a more sophisticated design for browsers such as IE 6,7 and 8. These browsers understand CSS well but lack some of the more modern enhancements.

    It was necessary to hide this enchanced stylesheet from ‘the pretenders’ who would render it badly. To do this I had to use a CSS hack, which was unfortunate. However, older browsers now completely ignore it.

    How I did that is outside of the scope of this article. However if you want to know, view the source on the site and look for default.css.

    This new design now renders perfectly well in the more modern versions of IE.

    Consultancy Clinic website in IE 7

    A watermark image is highlighted in this screenshot

    There are however, subtle differences between the versions of IE. For example IE6 does not support transparent PNGs and so in IE 6 the watermark on the form does not appear. Although it would have been possible to force IE6 to display this image, it was more sensible to simply not show it. After all the watermark is an embellishment to the design, not a fundamental part of it.

    The bells and whistles

    Finally I have added some further embellishments to the design for more advanced browsers. For example both Firefox and Safari support border-radius. This allowed me to add curved corners, which are simply ignored by browsers who do not support that style.

    Consultancy Clinic Website in Firefox

    I was even able to go a step further in Safari because it supports dynamic shadows.

    Consultancy Clinic website in Safari

    Conclusions

    Design enhancements like drop shadows and rounded corners are important, but not to the same degree as usability and accessibility. With finite time and budget, we are better spending our time making sure the site is usable on all browsers rather than getting it looking identical in a few.

    With the time I saved not trying to force IE6 to display a rounded corner correctly, I was able to ensure the site looked good in older browsers with a limited understanding of CSS.

    Once you accept that your site will not look identical in all browsers, you will be able to build sites faster, cheaper and ensure a broader range of devices can access them. Surely that is worthwhile?

    10 harsh truths about corporate websites

    We all make mistakes running our websites. However the nature of those mistakes varies. As your site and organisation grow, the mistakes begin to change. This post addresses common mistakes in larger organisations.

    Most of the clients I work with at Headscape are larger organisations – Universities, large charities, public sector institutions and large companies.

    Over the last 7 years I have noticed certain reassuring misconceptions within these organisations. The idea of this post is to dispel these illusions and encourage people to face the harsh reality.

    The problem is that if you are reading this post you are probably already aware of these things. However, hopefully this article will be a useful tool for convincing others within your organisation.

    Anyway, here are my 10 harsh truths about larger websites.

    1. You need a separate web division

    In most organisations I work with the website is managed by either the marketing or IT department. However, this inevitably leads to a turf war and the site becoming the victim of internal politics.

    In reality running a web strategy is not particularly suited to either group. IT maybe excellent at rolling out complex systems but they are not suited to developing a friendly users experience or establishing an online brand.

    Marketing on the other hand is little better. As Jeffrey Zeldman puts it in his article ‘Let there be web divisions‘:

    The web is a conversation. Marketing, by contrast, is a monologue… And then there’s all that messy business with semantic markup, CSS, unobtrusive scripting, card-sorting exercises, HTML run-throughs, involving users in accessibility, and the rest of the skills and experience that don’t fall under Marketing’s purview.

    Instead the website should be managed by a single unified team. Again Zeldman sums it up when he writes:

    Put them in a division that recognizes that your site is not a bastard of your brochures, nor a natural outgrowth of your group calendar. Let there be web divisions.

    Screenshot of Zeldman's website

    2. Managing your website is a full time job

    Not only is the website often split between marketing and IT, it is also normally under resourced. Instead of having a dedicated web team, those responsible for the website are often expected to run it alongside their ‘day job’.

    Where a web team is in place they are often over stretched. The vast majority of their time is spent on day to day maintenance rather than longer term strategic thinking.

    This situation is further exaggerated because the people hired to ‘maintain’ the website are junior members of staff. They do not have the experience or authority to push the website forward.

    It is time for organisations to seriously investing in their websites by hiring full time senior web managers to move their web strategies forward.

    3. Periodic redesign is not enough

    Because corporate websites are under resourced they are often neglected for long periods of time. They slowly become out of date both in terms of content, design and technology.

    Eventually the site becomes such an embarrassment that management step in and demand it is sorted. This inevitably leads to a complete redesign at considerable expense.

    As I point out in the website owners manual this a flawed approach. It is a waste of money because when the old site is replaced the investment put into it is lost. It is also tough on cash flow with a large expenditure happening every few years.

    A better way is continual investment in your site, so allowing it to evolve over time. Not only is this less wasteful it is also better for the users as is pointed out in Cameron Moll’s post ‘Good Designers Redesign, Great Designers Realign‘.

    Screenshot of Cameron Molls Article

    4. Your site cannot appeal to everyone

    One of the first questions I ask our clients is ‘who is your target audience?’ I am regularly shocked at the length of the reply. Too often it includes a long and detailed list of diverse people.

    Inevitably my next question is which of those many demographic groups are most important. Depressingly the answer is that they are all equally important.

    The harsh truth is that if you build a site for everybody it will appeal to nobody. It is important to be extremely focused in your audience and cater your design and content around them.

    Does this mean you have to ignore your other users? Not at all. Your site should be accessible by all and should not offend or exclude anybody. However, it does need to have a clearly defined audience that the site is primarily aimed at.

    5. Your site is not all about you

    Where some website managers want their websites to appeal to everybody, others want it to appeal to themselves and their colleagues.

    A surprising number of organisations choose to ignore their users entirely and build their websites entirely around an organisational perspective. This typically manifests itself in inappropriate design that caters to the managing directors personal preferences and content full of internal terminology and jargon.

    A website should not be about pandering to the preferences of staff but about meeting the needs of users. Too many designs are rejected because the boss doesn’t like green. Equally too much website copy uses acronyms and terms that are only used internally within an organisation.

    6. Design by committee brings death

    Illustration showing why design by committee fails

    The ultimate expression of a larger organisations approach to website management is the committee. A committee is formed to tackle the website because internal politics demand everybody has their say and all considerations are taken into account.

    To say that all committees are a bad idea is naive and to suggest that a large corporate website could be developed without consultation is fanciful. However when it comes to design, committees are often the kiss of death.

    Design is subjective. The way we respond to a design can be influenced by culture, gender, age, childhood experience or even physical conditions (such as colour blindness). What one person considers great design another could hate. This is why it is so important that design decisions are informed by user testing rather than personal experience. Unfortunately this approach is rarely followed when a committee is involved in design decisions.

    Instead, design by committee becomes about compromise. Because different committee members have different opinions about the design, they looks for ways to find common ground. One person hates the blue colour palette while another loves it. This leads to design on the fly when the committee instructs the designer to ‘try a different blue’ in the hopes of finding a middle ground. Unfortunately this can only leads to bland design which neither appeals to, or excites, anybody.

    7. You’re not getting value from your web team

    Whether they have an in-house web team or use an external agency many organisations fail to get the most from their web designers.

    Web designers are much more than pixel pushers. They have a wealth of knowledge about the web and how users interact with it. They also understand design techniques including grid systems, white space, colour theory and much more.

    Post from Twitter complaining about being a pixel pusher

    It is therefore wasteful to micro manage them by asking for ‘the logo to be made bigger’ or to ‘move that 3 pixels to the left’. By doing so you are reducing their role to that of software operator and wasting the wealth of experience they have.

    If you want to get the maximum return from your web team present them with problems not solutions. For example, if you have a site aimed at teenage girls and the designer goes for corporate blue, suggest that the audience might not respond well to the colour. Do not tell them to change it to pink. That way the designer has the freedom to find a solution which might be even better than your choice of pink. You allow them to solve the problem you have presented.

    8. A CMS is not a silver bullet

    Many of the clients I work with have amazingly unrealistic expectations about content management systems. Those without one think it will solve all of their content woes, while those who do have one moan about it because it hasn’t!

    It is certainly true that a content management system can bring a lot of benefits. They…

    • reduce the technical barriers of adding content,
    • all more people to edit and add content,
    • facilitate faster updates,
    • allow greater control.

    However, many content management systems are less flexible than their owners wish. They fail to meet the changing demands of the websites they manage.

    Website managers also complain that their CMS is hard to use. However, in many cases this is because those using them have not been given adequate training or are not using it regularly enough.

    Finally, a content management system may allow for the easy updating of content, but that does not ensure it will be updated or even that the quality of copy will be maintained. Many content managed websites still have out of date content or are filled with poor quality copy. This is because the internal processes have not been put in place to support the content contributors.

    If you are looking to a content management system to solve your site maintenance issues you will be disappointed.

    9. You have too much content

    Part of the problem with content maintenance on larger corporate websites is that there is too much content in the first place. Most of these sites have ‘evolved’ over years with more and more content being added. At no stage has anybody ever reviewed that content and asked what can be taken away.

    Many website managers fill their sites with copy nobody will read. This happens because of:

    • A fear of missing something – By putting everything online they believe users will be able to find whatever they want. Unfortunately, with so much information being made available, it is hard to find anything.
    • A fear users will not understand – Whether it is a lack of confidence in their site or in their audience, many website managers feel the need to provide endless instructions to users. Unfortunately, users never read this copy.
    • A desperate desire to convince - Many website managers are desperate to sell their product or communicate their message. Text becomes bloated with sales copy which actually conveys little valuable information.

    Steve Krug in his book ‘Don’t make me think’ encourages website managers to ‘Get rid of half the words on each page, then get rid of half of what’s left’. This will reduce the noise level of each page and make useful content more prominent.

    10. You are wasting money on social networking

    I have been encouraged that increasingly website managers are recognising that a web strategy is about more than running a website. They are using tools like Twitter, Facebook and YouTube to increase their reach and engage with new audiences.

    However, although they are using these tools, too often they are doing so ineffectively. Corporate twitter accounts and posting sales demonstrations to YouTube miss the essence of social networking.

    Social networking is about people engaging with people. Individuals do not want to build relationships with brands or corporations. They want to talk with other people. Too many organisations are throwing millions into facebook apps and viral videos when could be spending that money on engaging with people in a transparent and open away.

    Instead of having a corporate twitter account or indeed even a corporate blog, encourage your employees to start tweeting and blogging themselves. Provide guildelines on acceptable behaviour and the tools they need to start engaging directly with the community that surrounds your products and services. This not only demonstrates a commitment to your community but also a human side to your business.

    Screenshot of Microsoft's Channel 9 website

    Conclusions

    Large organisations do a lot right in the running of their websites. However, they also face some unique challenges that can lead to painful mistakes. Resolving these problems will involve accepting mistakes have been made, overcoming internal politics, and changing the way you control your brand. However, doing so will give you a significant competitive advantage and allow your web strategy to become more effective over the long term.

    For more information on how you can make your site more effective read the Website Owners Manual or discuss your site with Paul personally.

    There is a followup to this post entitled ‘10 ways to battle site bureaucracy.’ Check it out!

    Video: Introduction to WCAG 2

    I recently gave an internal presentation at Headscape about WCAG 2. A number of people expressed an interest in seeing it so I made a point to record it.

    At the end the presentation I references a stripped down version of the guidelines found here.

    I also refer to a quick reference guide to WCAG 2 that can be found here.

    Apologises

    Apologises for the poor audio quality of this video. Unfortunately the decision to record the presentation was made at the last minute and so we didn’t have a proper mic setup arranged. You can also tell it is not quite as slick as my normal presentations :)

    I would also like to apologise for the lack of transcript of this video. Again, it was not my initial intention to put this video online as this was an internal presentation containing my initial thoughts on WCAG 2. I am still learning a lot about the new guidelines and will publish a more considered article when I have a better understanding of the subject.

    Feedback

    On that subject, I would be interested to hear your feedback on the thoughts I present. Do you agree with my interpretation of the new guidelines? Have I misunderstood anything? Are there other elements I should have addressed? Your thoughts would be appreciated in the comments.

    Update: We now have a transcript!

    Thanks go to Anna Debenham who braved the horrendous audio to transcribe the presentation. If you cannot face the video we do at least now have a written version!

    Paul: Ok, this has worked out a little bit weird because the idea initially with this presentation was that it was really about bringing us up to speed with WCAG2 now that WCAG2 has been released. But I made the mistake of mentioning it online and several people said “ooh, can you record that?” so now it’s a little bit of both, a little bit of a presentation to you guys and a little bit of a presentation that will go on the web.

    Paul: So as you guys probably know, WCAG2 has now been released, and as accessibility is a big part of what we deliver and we talk a lot about accessibility, we need to be up to speed on it and we need to know what we’re doing. Obviously accessibility has become such a part of what we do day in and day out that we don’t necessarily think too much about it, it’s almost an intrinsic part of what we do, but with changes to WCAG2, or with the arrival of WCAG2, there have been differences, changes, things that have altered, so I want to make sure that everybody is up to speed with it. Feel free to butt in with questions, that’s absolutely fine.

    Audience: Will the video be able to see the screen?

    Paul: The video will be able to see the screen. Ok, so, WCAG2. Basically, WCAG1 came out in 1999 which is a good old time ago, in Internet terms that’s like forever, and there was a real need to make some changes and improve WCAG1. Let me just pop back and just explain.

    The Journey to WCAG2

    Paul: So, yeah, like I said, WCAG1 came out in 1999, it quickly dated as technology evolved, and some of the guidelines actually became harmful in a way. So you guys know that for example, we don’t always take note of what they say about Access Keys, we don’t always take note of what they say about “make sure you put text in an empty form field” and things like that. And WCAG1 was very much built with HTML in mind, and obviously the web is a lot broader than that and there are a lot more formats about. But unfortunately development of WCAG2 was very slow, and also fraught with controversy. I mean, famously with Joe Clarke who is an accessibility expert wrote on A List Apart “to hell with WCAG2″ because it basically had become a bit of a joke, because it was very generic; they were trying to write a set of guidelines that really made no effort to mention specific technology because they didn’t want it to date like WCAG1, but the result is it became unreadable and nobody could understand it.

    WCAG2 Reborn

    Paul: But, things did change. Major changes were made to the WCAG2 draft and things did improve dramatically. They really listened to the community, and the language in it now is much clearer. So what I want to do now is talk a little bit through what WCAG2 includes and what it doesn’t, and how we’re then going to go about implementing it and how it affects us.

    Principles

    Paul: Ok, so let’s look at the structure of WCAG2. Basically WCAG2 has 3 tiers to it that you need to know about. Tier number 1 is the idea of Principles. So this is kind of the most generic of the tiers, you know, it’s really kind of aimed at the kind of things you would tell a board of directors that doesn’t really understand anything technical, that doesn’t really understand accessibility at all. And there are 4 principles which are the foundations of web accessibility and these principles I’ll come onto a little bit later.

    Guidelines

    Paul: Underneath each of those principles are Guidelines. So, within each principle there are 3 or 4 guidelines or a number of guidelines that is different for each principle. But there are a total of 12 guidelines, and these are goals that you should be working towards in order to make your content more accessible to users.

    Success Criteria

    Paul: Under each guideline, there are Success Criteria. So now we’ve really hit the nitty-gritty, these are kind of specific, measurable goals that you’ve got to achieve. And this is how you judge whether your site is WCAG2 compliant, if you like. So, this is the really important level if that makes sense, but it’s organised within this hierarchy of guidelines and principles.

    Techniques

    Paul: Now, actually, there is kind of a 4th tier as well which is techniques. So you’re trying to, maybe as designers, you’re trying to conform to the Success Criteria, well there’s a whole load of different ways and different techniques that you can do that and you could read about those, and you could make up your own techniques if you wanted to, but there are some laid down that can help you get going.

    Working with WCAG2

    Paul: So those are the 3 levels that WCAG2 is built around. Now let’s dive into those a little bit. I had to think about how much detail I want to go into in this room. Obviously we don’t want to go into every technique that you could possibly apply and we don’t even want to go into necessarily every success criteria. That’s really for you guys to look through afterwards. What we are going to do is look at those guidelines and those principles, and hopefully help you to understand where WCAG2 stands over stuff.

    Perceivable

    Paul: Ok, so, the first… heh, totally illegible text, isn’t that great. Very accessible!

    Audience: (laughter)

    Paul: So the number 1 principle is Perceivable, and that’s 1 of your 4 principles that you’ve got here. And perceivable is basically talking about “information and user interface components must be presentable to users in ways that they can perceive”

    Audience: (laughter)

    Paul: Unlike that! (points to presentation)

    Audience: (laughter) Is the rest of the presentation like this?

    Paul: Yes.

    Audience: (more laughter)

    Paul: You actually don’t need to read this anyway which is very useful. So, Perceivable is basically about “can you see it?”, that is it as far as the principle is concerned, and the answer is “no you can’t”. But perceivable then breaks down into a series of guidelines. So, let’s have a look at what these guidelines are. So basically, perceivable is broken down into 4 guidelines. And if we talk through each of those it should give you an idea.

    Text Alternatives

    Paul: The first one is text alternatives. So this is stuff we already know. “Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.” So this really applies to things like video, audio, forms that you create, and interestingly CAPTCHA is particularly mentioned here. And that is a particular accessibility problem that hasn’t been particularly well solved I don’t think.

    Time Based Media

    Paul: The next way that Perceivable works itself out is in time-based media. What we’re talking about here is that you need to provide an alternative for anything that is time-based. So here we’re talking about captions for video, sign-language maybe, media alternatives, but it also applies to live and pre-recorded video. So if you’re streaming stuff, then you need to think about this as well as with stuff that’s pre-recorded. Now, it does take into account the difference between “crap, how are we going to make streaming video accessible?”. If you read into the guidelines it does give some good advice there. So that’s not quite as scary as it first sounds.

    Adaptable

    Paul: Anything that we produce needs to be adaptable. In other words, content can be presented in different ways. For example, a simpler layout maybe for people with cognitive disabilities for example. Really, this boils down to things like using semantic markup, meaningful order in your HTML so that if the CSS is stripped away it still makes sense in the order that it is presented, and not relying on colour and other sensory elements to convey information.

    Distinguishable

    Paul: And then finally it’s got to be distinguishable. So it’s about making it easier for users to see and hear content including separating foreground from background and that kind of stuff. So we’re talking here about contrast, colour, and control over things like audio and video, that kind of stuff. So that’s where we’re at with perceivable.

    Operable

    Paul: Let’s move onto the next principle which is Operable. So, Operable is about user interface components and navigation, and making them easy to use so that somebody can use them whatever disability they may have. So this again breaks down into 4 different guidelines, the most obvious of which is Keyboard Access. So everything that we produce has to be accessible via a keyboard. So, for example, the Flash video that we’re currently creating for the Wiltshire Farm Foods home page needs to be keyboard operated, alright? Which I bet it isn’t at the moment! And to be fair, it’s part of production, I’m sure they’d put that in at the end if I hadn’t reminded them. That existed under WCAG1, so there’s nothing different there. So everything needs to be keyboard accessible.

    Enough Time

    Paul: You also need to provide enough time for people to take in the information that they’re being presented with. So giving the ability to pause, stop and control time based material is really important as well.

    Seizures

    Paul: You’ve got to take into account seizures, some people can have seizures triggered by animation and that kind of thing, so there are various limits that the guidelines lay down about flashing objects and stuff like that.

    Navigable

    Paul: And then finally it’s got to be navigable. So this includes things like skipping content, having descriptive page titles, tab order, links that make sense out of context, lot’s of headings, that kind of stuff. Is this all making sense?

    Audience: Yes, apart from time-based media, I don’t understand that.

    Paul: Time-based media, we’re talking about video and audio. So let’s say you had… one of our podcasts. So, there are certain things we need to ensure. One is that it is operable, in other words, a user can pause the podcast if we get annoying, or they want time to take in the information that we’ve said, but the other thing is that we also need to provide an alternative way of them getting it which is why we provide the show notes that we do and the transcripts and stuff like that.

    Audience: Ok, well that kind of fits under Text Alternatives and giving it control so it’s under Operable… I just don’t get where it is under perceivable, as a perceivable thing, it has to be perceivable?

    Paul: Yeah, basically.

    Audience: Video, audio… all has to be perceivable then?

    Paul: Yes. Some of these principles and certainly some of the guidelines do overlap to some degree. But when you draw down to the Success Criteria level, of how you actually apply these things, then there are more specific techniques. I think what they did is create a load of success criteria, and then kind of chunked them together in meaningful groups, but sometimes they’re not so meaningful. But it is a vast improvement on WCAG1 as far as being able to understand it.

    Understandable

    Paul: Ok, talking of understanding it, our next one is Understandable. So this is the next one of our 4 top-level principles, so everything you produce has to be understandable. So what does that mean? Well that results in 3 guidelines. It has to be Readable, Predictable and has to be able to provide Input Assistance. So how does that work itself out in practice?

    Readable

    Paul: With Readable, we’re talking about making content readable, text content mainly. So this works out in things like setting the language in your HTML, you know, setting what the language is in the header, avoiding using jargon, finally we’ve got a decent reason to go back to clients and say, you know, “you can’t use that kind of language, nobody understands it!”. Also things like abbreviations need to be explained, and also reading level as well, and that’s something I really want to get through to a lot of our clients because a lot of our clients, especially the public sector clients that we have, have this attitude of “well of course, people that look at our site are of post-graduate degree people, and they have excellent reading level”, but that doesn’t take into account things like people that speak English as a 2nd language, who can be very intelligent but not particularly good at reading, also people with Dyslexia can be incredibly intelligent but not particularly good at reading. So reading level is an important aspect of it.

    Predictable

    Paul: For it to be understandable it also needs to be predictable. So with this we’re talking about things like consistent navigation, and no uninitiated changes. And this is a particularly important one in our world of AJAX and JavaScript and all this cool stuff that we’re doing where we can often trigger events without asking the user’s permission first. When I say “asking for permission” I mean they haven’t clicked on link or they’ve not initiated it in any way. Users need to initiate these actions… and no pop-up windows without them clicking first to trigger a pop-up and being aware of what’s going to happen. It’s all about making it understandable and making them aware of what’s going on.

    Input Assistance

    Paul: The last guideline under Understandable is Input Assistance. So this is going into the realms of when we do forms, how do we handle errors, what kind of feedback do we give to the user, what labels – are things clearly marked up as labels, are they descriptive of the fields and the forms and that kind of stuff. We’re also talking about help, what additional help are you provided in terms of tool tip and contextual help and anything else that you care to mention. So that’s Understandable, that’s what that principle is driving at.

    Robust

    Paul: The final principle is Robust. “Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.” In other words, what we build has to work on everything.

    Audience: What about AJAX?

    Paul: I think that’s where we get into the realm of progressive enhancement, that it’s fine to use something like AJAX as long as, if the AJAX is taken away, it still operates. Or, you provide an alternative version, the guidelines do actually accept that you can do alternative versions of something. So Gmail is a good example of that, Gmail, it actually doesn’t work if AJAX is turned off but they do provide an HTML only version of it which does the same thing. I’m not a great fan of that because it’s twice as much stuff to maintain, and one version become out of date and all the rest of it. My preferred technique is to build it so it works normally, and then to layer on the JavaScript and AJAX on top of it to provide enhanced functionality, which is what we guys have been doing pretty much all along and we need to continue in doing that.

    Compatibility

    Paul: So that Robust principle actually only comes down to one guideline which is Compatible, so that’s about maximising compatibility with current… listen to the wording of this… Maximise compatibility with current and future user agents, so we also need to be looking forward as well and predicting the future which is always good. But that’s where it comes back to using solid, good code that is’nt reliant on lots of hacks in order to get it to work, and it goes back to the conversation that we’ve been having recently about browser testing, upgraded browser support and that kind of stuff as well. So Compatibility and Robustness is the last principle. The other thing I should have mentioned with Compatibility is this also includes things like validation, making sure that your code validates, and just generally other markup type stuff.

    What, no AAA, AA, A?

    Paul: Ok, another thing that might have occurred to you is AAA, AA, A.. Priority 1, 2 and 3. Priority 1, 2 and 3 are still there, there are still those levels of conformance, but I get a real sense from the tome of this document, and this is just my personal opinion, people watching this video who know a lot more about accessibility might jump all over me on this, but my sense is that they were playing down those 3 levels of conformance. To be honest, I think I’m pretty keen on that. I don’t think those levels of conformance have done a lot of good generally speaking, because I think it’s kind of developed a checkbox mentality amongst some of our clients “We must be AA compliant” or “We must be A compliant” and they’re not actually thinking about the needs of the users, they’re just ticking the boxes so they meet some quota that has been established somewhere. One of the things that’s quite interesting, and I’m not sure if it’s a change from WCAG1 or not, I couldn’t find the reference in WCAG1 but again someone will correct me no doubt, but conformance in WCAG2 seems to be on a page-by-page basis. So you’re no longer in a situation where you want to claim conformance so you’re claiming conformance for an entire site, but you’re rather conforming on a page-by-page basis. And this allows you to basically pick-and-mix the level of conformance you want to reach on any particular page which is much, much more sensible because there are some elements where you might be building a particularly complex application that really isn’t going to manage being AAA compliant, whereas the rest of the site is AAA, and this one page isn’t. So it’s giving you the ability to mix and match. In fact, in the guidelines it says “It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content. In other words they’re saying it’s just not possible to be AAA in some situations, so don’t even try.

    Start With Basics

    Paul: So how does this relate to what we do on a day-to-day basis? Well, I think the language we use with our clients pretty much will remain consistent with how it was with WCAG1 which is that we need to start of by encouraging all our clients to start with the absolute basics. A lot of people are put off of accessibility because of the enormity of it, of all the things they’ve got to do. And even to be single A compliant there is quite a lot to do if you’ve got a site that has never been built to be single A compliant before. So I think our attitude has got to be that you work towards this over time, it is an ongoing process, you don’t need to do it all in one big go and that you need to start with the absolute basics, the quick wins, the stuff… you know, it’s the 80/20 rule, 80% of the problems that people are going to encounter from an accessibility point of view is caused by 20% of the accessibility issues if that makes sense. So we can solve a small number of issues but have a big impact on the site. So we’ll start off with some real basic stuff. Things like putting in “alt” and “title” attributes, providing alternatives to media, things like video and audio, being aware of JavaScript and the problems that JavaScript can create if it’s not implemented correctly, providing resizable text so that the user has the ability to either increase or decrease the text size on sites, to build everything to be standards based because that makes it so much easier in future.

    Audience: Aren’t we moving away from resizable text?

    Paul: We’re moving away from the resizable interface where the whole thing scales up and down, but there’s no reason why we can’t keep the text itself rescaleable. The layers should be able to push up and down. It has to be said with resizeable text, it is becoming less of an issue. The reason it’s becoming less of an issue is because browsers now have this zoom functionality built into them. But I don’t think we’re quite there yet to be able to drop resizable text entirely is my current feeling… I’ve got mixed feelings about it. But the obvious aim we’re going for here is to be single A compliant.

    Build Over Time

    Paul: So all of this is about building accessibility over time. Taking the guidelines by themselves is not going to be enough, and taking this checkbox mentality that I talked about earlier is not going to be enough. Once you’ve done these quick fixes, the next step on from that is to start consulting with your community. We need to encourage our clients to start talking to their users and find out what accessibility concerns they have. I also think, which I think we’re quite poor at, that we need to start testing with real users some of the accessibility stuff that we do, and the big problem there is persuading clients to pay for that. It’s really hard to get clients to pay for that kind of testing but I do think that it’s a really useful thing to do, and there are organisations out there that provide people you can get in to do testing, or that you can send sites out and they test with them. So, testing with real disabled users is really worthwhile. I think it’s about identifying major issues and dealing with those first, just pragmatic kind of prioritisation of issues, something you do with usability. With usability you look for the quick wins and the showstoppers and those you deal with first, exactly the same with accessibility. Now, what the major showstoppers are for those navigating the site need to be dealt with. And over time you build towards AA and AAA compliance if you can. But you only do that maybe on some pages. The big concern clients have and the reason they get into this check-box mentality of saying “we’ve got to be double A or we’ve got to conform to the WCAG guidelines” is fear, a fear of litigation. Especially our bigger clients, they’re really worried they’re going to get serious issues. But I think it’s important to stress with clients that litigation doesn’t happen overnight. You don’t suddenly have come through the post a writ saying “you need to come into court about this accessibility issue on your site”. It doesn’t happen like that. What happens in reality is the user complains. And if the user is repeatedly not heard and not listened to, and not responded to and not cared about and rejected, they get angry enough to maybe approach someone like the RNIB who then take it on into litigation for them. That’s the reality of what happens.

    Quick Response

    Paul: So as a result, you can diffuse that by responding to complaints quickly. So as you’re building up over time with the accessibility policy, if someone does complain, you need to write back to them and you need to deal with that issue straight up. Ok, so that’s how the client should be dealing with all this and there’s loads more I could say on this but I don’t want it to go on forever.

    Headscape’s Approach

    Paul: Let’s briefly talk about Headscape and our approach and how we should be approaching the subject of accessibility.

    Establish Approach With Client

    Paul: Well first of all I think everything that we do in our approach should be in conjunction with the client. I don’t think necessarily we talk enough to the client about accessibility. Some clients are just so bamboozled by it that they want us to take control, others want a say in it and what to be reassured that we’re doing something about it. So I think there’s a dialogue that we need to make sure happens. And if a client just wants us to take control of it, that’s great. If they want to be involved in the process, then that’s great to but we need to engage with the client and talk to the client more about it.

    Remain Pragmatic

    Paul: The second thing and I think this is really important is that we need to remain pragmatic in our approach to accessibility. Everything I’ve been talking about before like building up accessibility gradually, about doing the quick wins first and the show stoppers and that kind of stuff, that’s all pragmatic. I don’t want us on one hand to ignore accessibility, and it needs to be an integral part of everything we do, but on the other hand you can become extremist about it. We could spend hours and hours trying to get something to work in every conceivable user agent in the world and we can worry about every type of disability to the point where it becomes like a paralysis that stops us actually doing anything. So there’s a real balance that we need to strike here. And we need to strike that with our clients and working with our clients.

    Have a rationale

    Paul: Now I think it’s worth saying that if we decide not to comply with a guideline for whatever reason, we need to have a rationale for that. So we might not conform even to single A compliance in certain situations, although to be honest I can’t think of any off the top of my head, but if we do decide not to conform, we need a damned good reason why not. In other words, we need to have thought about it. And the other thing about accessibility is that we always think about it at the end of the project. It’s too late by then, we’ve built everything. So it really needs to become an intrinsic part of everything that we do.

    Responsibilities.

    Paul: Let’s talk about the idea of responsibility here and whose responsibility accessibility is within Headscape. Basically I’m going to say, everybody. One of the absolute great things about WCAG2 is because it’s got this 3 tiered approach, it is “accessible” to everybody. It’s understandable by everybody. So therefore it can be everybody’s responsibility to keep an eye on accessibility. And so this is how I think it should split down.

    Sales/Client – Principles

    Paul: Marcus and Chris and the Client should be worried about principles. The Operable, the Perceivable, those basic top-level principles. And you should be looking at anything that goes out from the company and going “well is that really operable?” So you can take a very top-level approach to it. And I think as you talk to clients as well you take this very top-level approach to it. That’s the level you guys should be working at.

    Guidelines – Project Managers

    Paul: Project managers, I think you need to be looking and understanding from the guidelines point of view. So you need to go in and read what those guidelines are, and you need to be sure that you understand them. And as you look at any work that goes out from the company, you need to be thinking “does it conform to those guidelines?” You don’t necessarily care about the nitty-gritty of how those are measured, or the nitty-gritty of how they’re achieved, but has that guideline been met? That’s the level you need to be working at.

    Success Criteria – Designers and Developers

    Paul: Then when it comes to the designers and developers, you need to get right into these guidelines. And you need to understand the success criteria and how to apply the guideline and how to make them work in practice.

    Check Everything

    Paul: So basically, we need to be checking everything that goes out the company for accessibility. And I have to say I’m making the mistake of saying this on camera, but I think we’ve got a bit lax recently when it comes to accessibility. We reached a point where it was becoming quite intuitive to us, and we were doing it quite naturally, and then as a result of that, we stopped checking because it was the natural process of what we were doing, and then bad habits start to seep in again. So WCAG2 is a great opportunity for us to say “ok, we need to start reviewing everything we’re doing as it goes out again”. So I’d really, really encourage you to check everything.

    Needs to be second nature

    Paul: basically we need to get to the point where this is second nature to us, so that we’re doing this intuitively again, but not to the point where we’re no longer checking.

    Audience: Clients often say “what’s the difference? If I just got for single A compliancy, what won’t my site be reaching?”

    Paul: I have to say that I think I would stop talking about double A, triple A and single A compliancy. I don’t think there’s really any value any more in talking about that to the clients.

    Audience: I think there is because having the page by page conformance is a really good thing and that we can now argue that yes, we can now make the majority of your site triple A compliant, but for a page full of videos, we can make it single A compliant.

    Paul: Ok

    Audience: Clients will continue to reference it in briefs. You can’t not talk about it.

    Audience: I think it’s actually quite a strong thing.

    Audience: is it a page by page compliance, or template by template compliance?

    Paul: I think it has to be page by page because the content that goes into the page, into the template, could invalidate it. This is why I think it’s something that should be downplayed. I accept the clients will still talk to us about it, but clients still talk to us about doing speculative design, it doesn’t mean we do it. I think there’s an education thing there whereby we need to move clients away from being obsessed by double A, single A compliance, and to start thinking about accessibility policies. What is there accessibility policy and what is it that they are trying to achieve on their site? Our base mark is going to be single A, it’s always single A, and I think it should continue to be single A.

    Audience: but if you don’t talk to them about it, you could argue that less caring clients would just say “well why would I do anything about it, bottom line?”

    Paul: Yeah, I said you shouldn’t talk about single A, double A, triple A, but that doesn’t mean you can’t talk to them about accessibility and the improvements that accessibility brings because for people that have got that sort of attitude you don’t want to talk about the disabled if they don’t care about the disabled, you talk about search engines, and that’s the best way to sell accessibility, by talking about search engine placement. That’s the reason you want to be accessible for people who have that kind of attitude. For those that care, and are talking about single A, double A and triple A, you need to say to them “well actually, conforming with any level, it’s great that you want to do accessibility, and certainly single A should be an absolute minimum, but we’d encourage you to start working up an accessibility policy and looking at your site as a whole and say could this area do more in your site, your accessibility policy should do real world testing with real users…” all kinds of things.

    Audience: So you think that we should be encouraging large organisations that have accessibility policies themselves that refer to double A, triple A, to try and persuade them to kind of move away from that?

    Paul: No, not necessarily, I wouldn’t go that far. Don’t get me wrong, I’m not saying that they’re a bad thing, I’m saying they’re not the be-all and end-all. And at the moment I feel like the vast majority of clients think they are the be-all and end-all. They’re obsessed with putting that little badge on the bottom of the page. And it’s not about putting badges on the page. The trouble with institutions that have these policies of single A, double A and triple A is that these policies are in place for the institution, not for the user. And that’s my problem with them. That’s why I think we should try to break that mentality with clients. And I accept that sometimes we’re going to lose, and that’s fine. Exactly the same goes when we were talking about browser support. I accept sometimes we’re going to lose that battle as well. But it doesn’t mean we shouldn’t try and fight it.

    Audience: I just wondered why WCAG2 still does it, because yes, you’re right basically, and accessibility requirements should be based on user requirements and not ticking boxes, so why is it still in there?

    Paul: I think it’s in there because… my impression… I hate talking about accessibility on camera! You remember what happened last time in the podcast? It was just a nightmare! I think the reason it’s still in is because some of those success criteria are hard to meet. Some of them are damn difficult. When you start talking about streaming video, you’ve got some difficult challenges there that need to be met. So I think as a result, what the W3C is saying there is that we accept that some of these things are difficult to do. And we accept that you’re not always going to be able to do them, so we’re going to make them triple A. But come on guys, some of this stuff is dead simple and we should be doing it, that’s single A. That’s my impression of the mentality behind it, and that’s a great mentality, but it’s when someone changes that to being guidelines, which is what they are, to being rules, really instilled by Moses and presented to the people. You know it’s not that and I think that’s an important differentiation to make.

    Where to Start

    Paul: I know what you guys are like, especially designers. Ok I’m making sweeping generalisations here. But, if you guys go along to the WCAG website and you look at the WCAG2 guidelines, it’s horrible! It’s intimidating and it’s scary and it goes on for pages. And there’s a lot of text around it.

    Audience: There’s no pictures? (laughter)

    Paul: There’s no pictures! The design isn’t even very good. So what I’ve done is I’ve taken that page, I’ve literally all I’ve done is I’ve stripped out the explanation text in front of it, and the waffle at the end of it, and I’ve left you with just the set of guidelines so it looks like a slightly less intimidating list. Not much but slightly. So that’s up at http://www.headscape.co.uk/WCAG2 so if you go to that, you can get just the actual list of criteria. There’s also, on the WCAG2 website, there’s a thing where you can go and you can say my site uses tables, my site uses video, my site has this and that, and you untick the ones that it doesn’t have and it narrows down the list of success criteria to only show you the ones that you need to care about. So you might want to check that one out as well. Ok, so that’s basically all I have to say, are there any other questions before we wrap up?

    Questions

    Audience: Clients are going to ask us the 1 minute elevator pitch. What’s the difference between WCAG2 and WCAG1? What would you highlight as differences?

    Paul: I think there’s a bigger acceptance of things in the world other than HTML, so things like Flash, PDFs, all that kind of stuff, there’s much more reference to that kind of thing. It’s much better written, much better organised. I think it’s more pragmatic. It’s a little bit more… I think it will last the test of time more. It’s hard to pin down exactly what I mean by that. There is actually a document out that talks about the specific differences between WCAG1 and WCAG2 if you wanted to get into that level of detail. And to be honest, I couldn’t tell you what that is yet because I haven’t looked at it in that much depth myself.

    Audience: I think you and I do need a couple of the more detailed stuff, to get the guidelines, just one or two examples basically. Something that’s new between WCAG1 and WCAG2, and also some of the differences between single A, double A and triple A. The streaming video is an excellent example.

    Paul: Just go along to http://www.headscape.co.uk/WCAG2 and you’ll be able to see those different levels.

    Audience: It seems like, an almost unwritten principle, or unwritten in your list of principles. It’s technology agnostic.

    Paul: WCAG2 started off as so technologically agnostic that it wasn’t understandable.

    Audience: WCAG1, the first line is all about “it must be W3C technologies”.

    Paul: Yeah, it will pretty much accommodate anything. You know, it talks in terms of audio and video. It doesn’t mention Flash for example specifically, at least I don’t think it does, but it refers to those kinds of things. It refers to documents that are not HTML. I’m saying this as much for the video as anything else, I’m still learning about it as well. So I think it’s going to be a learning process for a while for us to really get to grips with this, and truth be told we probably should have started a little sooner than this, but it’s not radically different from WCAG1. This is as much getting us back into the habit of thinking about accessibility as anything else really. Ok?

    Audience: 1 more question. Are they new Keynote animations?

    Paul: Yeah, they are new Keynote animations.