Actions in progress
Video: Actions in progressSometimes even when we get to the end of the form and hit the primary action, things might take a bit. That is, you may need to process some information, calculate some data or even upload a file. In these situations we want to provide feedback that actions are in progress. Here is a situation we'd like to avoid. Do not click the Submit button twice; you may actually get your credit card billed twice. Look at the amount of legal text in the second one. We run the risk of having our credit card charged. The issue here is that the burden has been put on the user, on our customer, instead of being taken on us.
Viewers: in countries Watching now:
In this course, interaction designer Luke Wroblewski shows how to create web forms that encourage visitors to enter information and covers ways to capture input without the use of forms. The course covers boosting conversion rates and customer satisfaction, organizing the structure of forms, aligning and grouping form elements, assigning the correct input field types, validating input, and handling data entry errors. The last chapter highlights alternatives to static forms, such as using dynamic inline forms, using web services, and leveraging device capabilities, which can be used to gather additional information or replace a traditional form altogether.
- Understanding why forms matter
- Deciding on the form length and structure
- Adding tabs to a form
- Creating required fields
- Adding input masks
- Creating selection-dependent inputs and actions
- Displaying success and error messages
- Adding inline validation
- Understanding gradual engagement
- Enabling touch and audio input on devices
Actions in progress
Sometimes even when we get to the end of the form and hit the primary action, things might take a bit. That is, you may need to process some information, calculate some data or even upload a file. In these situations we want to provide feedback that actions are in progress. Here is a situation we'd like to avoid. Do not click the Submit button twice; you may actually get your credit card billed twice. Look at the amount of legal text in the second one. We run the risk of having our credit card charged. The issue here is that the burden has been put on the user, on our customer, instead of being taken on us.
The system should instead of giving this type of message, disable the primary action so that people can't make a mistake, and then provide a little bit of feedback about what's going on. Let's see how that can actually happen. On the 37signals' site, Basecamp, we can see an example of this principle in action. When I click Post this message with an attached file you'll note the primary action turns into an animation. That is, it's letting me know that something is going on. I can no longer click that button again; therefore, I can no longer make a mistake.
Up at the top we see another animation that actually tells us why things are in progress. A file is being attached, that may take a bit to upload, okay, now I understand what's going on here. The feedback and the disabling of the Submit button actually let me know that actions are in progress. Disabling the Submit button doesn't mean hiding things from people until they're ready. So on this example of a form for getting online, how do I actually submit the form? That's right, the primary action has been removed until I click a single radio button, which then pops up this Activate link.
This isn't what I mean by disabling the Submit button. What I am talking about disabling the Submit button, I mean, letting people know that something's been in progress and that their action has been registered. Not that they need to hunt around for how to actually complete a form. While we are on the topic of streamlining actions, a very common pattern at the bottom of the form is the Agree and Submit. That is, you need to agree to a series of legal terms or privacy policies and then hit a submit button. Problem with this approach is that many times the Accept and Agree Checkbox is unchecked, because lawyers are expecting us to actually take an affirmative action indicating that we agree to that.
What happens is, people go through the form, don't see that checkmark, click Join Now, and get an error. A much easier solution at least in terms of streamlining, is to actually put in text like this. By clicking on the button below, I agree to the Terms of Service. Therefore no checkbox to miss, and there's still an affirmative action gained by clicking on the button. eBay Express has gone even further and removed the I Agree type of language, instead making the button really aligned with what people are trying to achieve. In this case they are trying to register.
A file is being uploaded, some data is being calculated, whatever it may be. Last but not least, while we are talking about Streamlining Actions, consider an opportunity to streamline legal requirements. This is a common area where people get tripped up in web forms and end up with errors. You can simply move things to a single action and have that action labeled, the primary thing that people are trying to complete. Purchase, Register, that'll get people through forms more quickly and on their way to the good stuff.
There are currently no FAQs about Web Form Design Best Practices.