Duplicating browser functions on your web site...don't (mostly)
January 2, 2010 Best Practices
Usability has taken its rightful place as a critical (if not the critical) element in web design. Sure, the overall presentation might look great but if user's can't actually use the site to find what they want then all of the pretty colours and fancy images are pretty much in vain.
Usability starts with sound design decisions based on the designer's experience and insight into user behaviours. There are, however, some key usability no-no's to remember that even the most talented designers often miss. One of those items is the duplication of browser functions on web sites.
It's a waste of time and resources
Some argue that users aren't aware of many of the features in web browsers, such as resizing text or printing pages. It's my opinion that we shouldn't waste development time in adding functions on web pages that are already built in to the browser itself. Clients need to stay within budget and adding redundant functionality onto a web site is not just a waste of money but also time. (You of course want to get the client's project launched on time, right?)
Users are smarter than you think they are
One of the misconceptions that exists and is more and more becoming recognized as false is that users don't know how to browse a web site and need their hand held at every turn. I submit that regardless of the age or experience of the user, a web site that focuses on following best practices for both design and usability will accomodate everyone. I also don't believe that just because a web site's demogaphic has a high number of, say, users over 40 years old, that it must be necessary to add functions which are already available in the browser itself or other elements that serves only to perpetuate the notion that the users don't know what they're doing. As developers we simply cannot treat our users in this manner.
OK, let's just get to the specifics here
Here are the six most commonly used redundant <cough>tools</cough> added to web sites. I've also included situations where you may still want to use them. Those situations are rare but, let's face it, they happen.
1. Opening links in a new window
If a user wishes to open a link in a new window or tab then they will do so on their own. Another reason against this practice is that it can damage your analytics tracking, specifically with page referrals. If you absolutely MUST force a new window on a user then place an icon next to the URL so they know what to expect.
When you may still want to do it: When you link to demonstration pages or PDFs and other documents.
2. Increasing/decreasing font size on the page
This is most often placed into a web site's UI to make up for poor typography practices. If your font sizes are balanced and your pages are easy to read then there is no need to add this function. If the user wants, they can resize the text via the browser themselves.
When you may still want to do it: Never. It's has no value.
3. 'Print this page'
Again, no need to do this if the function prints the entire page. The only instance in which I would recommend the addition of a print function on a page is when you will only be printing a section of a page or content in a modal element.
When you may still want to do it: When you want to print only a section of a web page, which can be done with Javascript and CSS.
4. 'Print Friendly'
In the old days, it was very common to see a link at the top of an article that opened a plain text version of the copy for the user to print for reading later. This is another lazy excuse for poor typography practices.
When you may still want to do it: Never. Spend the time improving your site's typography implement a print.css file.
5. 'Add to Bookmarks'
I don't get a whole lot of requests to include this function on sites I build anymore and thank Odin for that!
When you may still want to do it: I can't really think of any situation that would call for it. Anyone?
6. 'Go Back'
Of all the browser functions available, the 'back' button is arguably the most used. Adding it to a page is unnecessary. If you are concerned about users' ability to navigate your site, consider improving your navigation menu. Perhaps you need to employ breadcrumbs or pagination. If your site's usability and accessibility is on track with your users' needs and behaviors then those pesky 'back' functions (typically done in Javascript and notorious for 'breaking' and interfering with analytics tracking) are utterly useless.
When you may still want to do it: Never. Focus on improving your navigation practices instead.
What if the client insists on you developing these functions?
There will be situations in which your client is insisiting on having browser functions added to their web site whether it be because they think it's 'cool' to be able to see their site 'do that' or because they simply feel it's necessary. Whatever their reasons, you have two options:
- Patiently and clearly educate the client on the issues associated with adding the functions from both a best practices and practical perspective. Be confident in the knowledge that they have hired you because you are the expert and this is an opportunity to educate and guide them.
- Just do it. There are times when you need to set aside your own opinions on best practices whether you are right or not and do what the client wants. There's no shame in that. You haven't sold out. You are a service provider and you are being paid to produce what they have requested. If you want to insist, use a diplomatic degree of influence and let the client make the final decision.
Of course, I'm just giving you my opinion. You may have a different view. I'm eager to hear yours!
Stay well.
You might also like:
- No comments yet.
125 Subscribers
