With the arrival of FireFox 3 (and its record-breaking amount of downloads in its first 24h) more and more of us web architects and web developers are getting rid of their beloved FireFox 2 installation and are moving all their bookmarks, themes and extensions to version 3 of the popular browser. And rightfully so, version 3 is faster, much more stable and its updated Gecko engine is displaying your website creations in the best possible way… or is it?
I came across a couple of odd bits when developing a website – it seems like Firefox 3 is displaying a floated element’s width of 100% correctly, whereas FF2 would not fully acknoledge the width unless the element was previously set to “clear: both;” (or something along those lines, unfortunately I am still relatively new to the CSS cut-up world.
So we decided to install FireFox 2 again on the design-machines next to an existing FireFox 3 installation without causing any issues with the extensions or other settings between the browsers. I got it to work pretty much instantly on the first go, but since colleagues and friends were asking about how to get FireFox 2 to work with FireFox 3, here is a quick step-by-step guide after the break. Continue Reading
Following my previous article we are now going to put our website prototype to a first test before we begin developing the website. While the functionality and navigation makes sense to us – after all, we just spent the last week(s) working on it – we need to ensure it works the same way for others as well. We understand how we get from a destination page to the product or trip we are after and finally to the enquiry page – but will anyone else do so as well?
Usability testing will reveal if the flow of the site works, and accessibility testing will ensure that our site complies to any relevant accessibility guidelines.
Following my previous article about Information Architecture and user-testing you we came to the point where we have researched quite a bit into the client’s company: we know the brand, we know the product(s) and its userbase, and we have acquired demographics of the target market. It is now up to us to design and develop the client’s website.
Many of the designers I worked with in the past have then gone and worked on first mock-ups of the home page and a product page – nicely designed and with a bit of flash here or there – which they then sent to the client to get feedback and develop a new or final draft of these pages. And then they went off and started developing the website, without much (or any at all!) time spent on the information architecture or usability (and accessibility) of the client’s website. In today’s article I want to go through a couple of best practice approaches to information architecture and usability for Business-to-customers (B2C) websites. Continue Reading