Why you should eliminate “I agree” checkboxes
The “I agree” checkbox has become an interface standard on registration forms. “I agree to the terms and conditions.” While it’s purpose is generally understood by the consumer, it is a key source of frustration for people registering for accounts.
Why it’s overlooked:
- Checkboxes are small, particularly ones which aren’t grouped in a fieldset;
- They are typically at the bottom of a form – Out of sight out of mind;
- They are placed in close proximity to a larger button which takes the focus.
This checkbox is completely unnecessary, and it’s purpose can be handled in a much more graceful manner. Most popular websites have fixed this issue, while most less popular websites have not.
The “I agree” checkbox is the leading cause of form validation errors. In my research, about 1/3 of participants in our studies miss the checkbox the first time around. Even though the problem is easily corrected, people occasionally abandon the form altogether when it fails validation the first time.
This error pattern sticks out like a sore thumb when you see it in action, but goes completely unnoticed when you aren’t observing real people using your form.
Replace with a quick sentence: “By clicking the ‘submit’ button, you agree to our terms of service.” The legal contract is the same (as far as I know), without the added point of failure.
Twitter’s registration form is pretty straightforward and simple. However, by placing the “I agree” sentence beneath the button, it will lose some attention.
Google gets it perfect on their YouTube registration page by visually grouping the sentence with the submit button.
As usual, 37Signals takes it a step further and emphasizes this with excellent copyrighting and design on their Basecamp signup page.
1 Comment »
Search
Popular Posts
- 50 Tips To A User Friendly Website
- My Favorite Pomodoro Timers
- How to build a Gantt Chart with the Google Charts API
- Why Flash is Mostly Bad
- Sharing the Grid
- Why You Should Outsource Usability Testing
- 10 Tips to Better Google Wave Conversations
- The difference between User Research and Usability Testing?
- How to Label Submit Buttons
- Our New Development Process





Nate Klaiber
This has been a pet peeve of mine for a while now. This seems like another case where we put the burden on the user instead of making the experience better. I have heard cases in the past where organizations don’t care that the person misses the checkbox – they want them to realize it’s there and agree to the terms.
The worst part of this experience is that most of these developers don’t add labels to the checkbox text. I get frustrated when I fail validation because of it, and in my frustration quickly try and click the text, then I become more frustrated.
I love the examples you pointed out – you should do a series of form elements like this, and how to make the experience better by putting the burden on the developer, not the end customer.
February 10, 2010