Archive for June, 2010

Forms and Usability

Tuesday, June 22nd, 2010

Forms are something that should be on every campaign website no matter how big or small the campaign is. These forms might be to collect contact information, request volunteers, or sign up for events. In any case, the first question always asked when drafting a form is “What information do we need to collect?”

The first reaction to that question is always something like “We need x, and y, and z would be nice…oh, and we can’t forget etc, etc” From a campaign stand point, the more information is the better. The more information you have the better you can mine the data for information about your supporters and the more ways you will have to contact your constituents. Before you go creating a hundred form fields…stop. Think about the form from a user perspective. As a user, do you want to answer a hundred questions? Do you want to have to go through pages and pages of text boxes without knowing when it ends? Most likely the answer is going to be “No.” Your die hard fans may spend the time, but they are going to turn up to vote for you on election day no matter what. The simpler your form is, the more likely visitors will actually fill out the form.

A second issue is with trust. In other words, what information does the visitor trust giving over to your website. There are multiple concerns here such as who sees the data? Where is the data stored? How is the data used? And, is the data secure? You will never be able to answer these questions in a way that will satisfy your visitors. The best solution is to only ask for information that people do not mind having floating around in a server.

One thing I notice a lot of forms do not have is form validation. This is to validate the information itself. For example, an email should have an “@” symbol followed by some sort of domain such as “gmail.com”. If you caught a possible typo in the email, how are you going to get it corrected…by emailing them? Also, you should give them an error message telling them specifically what field is broken. If they put letters in the phone field, say “Invalid characters for phone. Please only enter numbers.” It will also deter bots and people who want to fill your form out with junk. It is worth while to collect only the good data.

Finally, consider layout. I could go on and on about layout, but all I am going to say make it easy to navigate and fill out. Your form should be all on one page and form fields should be obvious. Layout also includes the means of navigating to the form. It should be very obvious how to get to the form and what it is. For example, if I want to volunteer, I do not want to spend a bunch of time searching for that form.

Everyone does forms slightly different. The important thing is to make it usable. There is a balance between simplicity and getting the information you want. You don’t want to ask a million questions, but one question is probably not helpful. A good example of a simple and usable form is Kasich’s Sign Up form. It is short and easy to understand. Better yet, he has a short little video at the top that you can play. Bonus: videos are more engaging and easier to watch than reading a bunch of text.

The next post will be July 5th.

Why 404 Errors Matter

Tuesday, June 8th, 2010

We have all seen the “Page Not Found” error while surfing the web. This is commonly called a “404 Error.” All websites, political or not, face this issue. Lost pages come from many sources. They may be old links or the user has a typo in their url address. Either way, it is your responsibility to help the user find the content they are actually looking for. It can be a challenge to figure out where to send the user after the error.

There are several different ways websites handle this problem. Senate hopeful Rand Paul from Kentucky has his error page be the home page. If you go to http://www.randpaul2010.com/not-a-real-page you will not be able to tell that it was an error. The only sign of an error is in the title of the page. If you are using a browser that supports tab browsing, you will see the tab entitled “Nothing found for Not-a-real-page.” While it is unlikely that anyone would be intending to find Rand Paul’s page on “not-a-real-page,” the point is the error could be much more helpful. An average user would think the error was the website’s fault since there was no alert that the intended content is missing.

A second solution is to tell the user that the page was not found with a custom 404 error page. Another Senate hopeful just north of Paul’s state, is Rob Portman of Ohio. If you go to http://www.robportman.com/not-a-real-page you will see that his site explicitly states there was an error. This is helpful because, 1) it helps the user figure out the problem and 2) it’s honest. It even has a link to go back to the home page. I would suggest Portman go a bit farther and have a “Are you looking for…” section with a handful of popular links like “Donate” and “Volunteer.” At the very least you want to give the user enough information to find the solution. As in all web design, the less work you place on the user means the more likely they are to stay and engage your content.

The worst is to do nothing. Take a look at New York’s Republican party’s error at http://www.nygop.org/not-a-real-page. Most visitors would try the url once or twice more and then give up entirely. By doing nothing, you will annoy visitors interested in your campaign and may also lose a volunteer or even a donor.

No one ever wants to plan for having a broken website. That’s not what you pay your webmaster to make. However, users will find ways to make it to non-existent pages. It will happen and the best approach is to capture those lost users. They will appreciate it and in return will engage your content and if you are luck, they will donate.

The next post will be on June 22nd.