Posts Tagged ‘Web Forms’

WordPress and Scheduled Posts

Monday, September 22nd, 2008

If you run a blog and hope to keep the content on it fairly fresh, utilising any sort of future scheduled post functionality it really important.  It means the difference between updating your blog when you’re out of the contry or not.  When using such a feature, there are certain aspects that must be clearly conveyed to the user.  With that in mind, let’s take a critical look at the current (Version 2.6.2) WordPress implementation of scheduled posts.

WordPress Post Status Options

The image to the right is a screenshot of the controls used to schedule (or backdate) a post in WordPress.  The date controls aren’t visible by default, but rather are accessed by clicking an Edit button next to the “Publish Immediately” text. This is replaced by the word “Cancel” when clicked.

An immediate problem you’ll notice is the Cancel option itself.  Being placed to the right of the text “Publish Immediately” implies that clicking it will cancel the immediate publication.  That isn’t the purpose of the option.  The text “Publish Immediately” also remains, even after a new date has been chosen (it remains after the post has been auto saved and will only update when the post is saved by the user, or published.  Many users will publish posts without ever saving them first, and as such won’t ever see the updated text).  This is completely misleading and confusing.  In short, the design leaves the user with some serous doubts as to when the post will be published, if at all.

Once you’ve selected your published date and time, you have two options.  You can either “Publish” or “Save”.  Once again, the options are ambiguous.  If I click publish, will I actually be publishing the post, or will it be published when the date and time I have chosen is reached?  Likewise, if I save the post now, with a status of “Unpublished”, but with a future publish date, will the status of the post change when the date is reached?

All entirely valid questions that could be answered with better form design.  Thankfully, Automattic are looking at a thorough reworking of the WordPress back end for the next release (2.7), let’s hope they put a little more thought into it this time.

Popularity: 28% [?]

Usability Review – webuyanycar.com

Thursday, May 29th, 2008

Overall, I genuinely think that usability in websites and web applications is improving.  But every now and then I stumble across a site that completely bucks the trend and manages to provide a truly shocking user experience.  One that ensures that I, and many others, will never use their service.  Today was one of those days.

I heard a radio advert for a new service called webuyanycar.com.  The theory is that they will buy your car from you direct, to save you going through the hassle of advertising and sorting out a private sale.  So, being curious as to how a service like this would actually work, I checked them out.  Now I wished I hadn’t.  Quite simply, it’s one of the least usable sites I’ve ever come across.  Poor layout, badly worded copy, buggy forms, unclear graphics, this site has it all!

So taking it step by step, let’s see where they go wrong.  Firstly, you have to enter the registration number of your car.  Once you’ve done this you get presented with a drop-down box where you select the year.  The button next to this field is labelled “VALUE MY CAR”.  This is misleading as there are a number of steps required before you actually get the value of your car (which, by the way, was at least 30% lower than current realistic market value).  When creating a multi-page or multi-step process, it’s key to keep users informed as to how far they are through the process.  Suggesting it’s near to the end, and then not fulfilling that expectation results is a high number of abortions mid-process.

The next step in the process is identifying any damage on the car.  This is done through a flash object (as pointed out in the comments, this isn’t a Flash object, it’s actually Javascript mixed with image maps).  I defy anyone to look at the Damage Assessment Tool’s interface they have chosen and tell me which end is the front of the car.  In fact, I believed that the right hand side was the front because of the shape of the headlights.  This isn’t the case.  There are tool tips when you hover over the section but these are badly formatted and buggy.  All in all, if you have to record any damage, it’s an absolute chore and very hit and miss.

Once you’ve added any damage, you then get to the screen which requires your personal details.  I’ve added a screenshot of this screen to the right, just so you can see what it looks like in FireFox 3.  Note that FireFox 3 is currently in the “Release Candidate” stage, meaning that it’s not entirely ready for mass consumption (although once a software project reaches release candidate stage, typically only defect fixes are included and features are not changed).  FireFox is the world’s second most popular browser, used by about 25% of Brits.  As you can see, it’s horribly broken.  To make matter worse, even if you can figure out what fields require what information, you get random validation failure messages (for no apparent reason) that don’t seem to be attributed to a specific field (because the layout is too broken to figure out where they are supposed to be positioned).  And as the icing on top of the cake, the submit button doesn’t appear to work in FireFox.  So even after battling through badly designed and horrendously implemented forms, you can’t get a valuation in the end anyway.

One other oddity you’ll find regards the privacy policy.  As with most websites that require personal information, they will try and sell it unless you tell them not to.  Yet look at the wording for the option.  This was obviously written by someone who either doesn’t understand the fundamentals of web form design, and what the different input types do, or doesn’t understand basic English.  But most likely both.  The first thing you’ll notice is that it says “Click Here”.  “Click Here” is appalling when used as the text for a link, it’s an abomination when used as part of a form.  You’ll also notice the ambiguity is introduces.  If I click there, I’ll deselect the check box.  Usually these are opt-meaning I would want the check box checked.  And what if I click there, forget, and then click there again?  No doubt my details would be winging their way to all and sundry before I know it.  Quite why they can’t just clearly state whether that element of the form needs to be selected or unselected in order to achieve the desired result is beyond me.

This truly is one of the trend bucking sites I touched on in the introduction.  Considering this is primarily a web based business, launching with such a clearly under-designed, incompetent, not-fit-for-purpose website could be a huge mistake.  if they can’t handle something as simple as a web form, how on earth am I supposed to trust them to buy a car off me?  Not a chance.  One of the worst user experiences I’ve had in a long time.

Popularity: 51% [?]