Is it ok not to have a button for a search box?

Question

I was wondering if it was ever ok not to have a submit button (Ok, Go or Search for example) near a search box in Web pages.

I know that hitting enter is much faster and that it will perform the search.

However, is it an accepted convention for the average non tech savvy user or only for the tech community?

For example, the search box here at stackoverflow doesn't have a submit button, but I don't think anyone is complaining (and I sure don't).

On the other hand, someone suggested using Google as an example: would people notice if the buttons were removed?

I just started reading Don't Make Me Think by Steve Krug and he mentions that every search box should have something that tells me I can click on it to launch the search.

Your thoughts?

Answer 1

Why you should have a button:

• Not everyone knows they can hit enter, so you are leaving some less savvy people out in the cold.
• Some devices like phones and consoles may not have a way to submit without a button. The PC based browser is still dominant but don't assume it is the only way people access your site.

You may not have a button if (both conditions must be satisfied):

• Your audience is tech savvy (as on SO)
• You provide a visual cue that the search box actually is a search box
  • By adding text inside it mentioning it should be used to search
  • By adding an icon inside the box

Generally I would think that hitting enter is a shortcut to submit rather than the primary means.

Answer 2

I think for a non-tech person some sort of submit button is needed. Think about people who don't use computers very much. They often click all of the buttons needed instead of hitting enter because they don't realize enter does the same thing. My opinion...if it isn't for tech guys only then it should be as simple as possible.

Answer 3

I think it depends on your target market. If you are StackOverflow it's not too hard too think they know how to use a browser (using a back button on a browser to navigate is a similair design convention) and pressing Enter = submit for search.

However if your target market is say mechanics (no offence to mechanics) that don't use a browser/computer often then look at how Google does it (and they target the broadest scope) - they have a button to submit.

There is a middle ground you could look at, which is have a water mark like StackOverflow which tells users "Click here, type in search values and press enter to search" - or something like that (hopefully shorter) where you actually catering for users of all levels.

Answer 4

It depends on your audience. Steve's audience is everybody. Majority of which are so far from IT you'd need a telescope to see them. If your auditory is a single user, you might skip all clues: button (with or w/o names), in-box label.

For my own login window I leave two fields: no labels, no buttons, no javascript to tell you which one is which. But that's not a public project.

Answer 5

"Don't Make Me Think" - so gimme a button.

There will always be someone using the application for the first time; don't make them think either. And your screen shouldn't be so fussy that it is impossible to fit the button in comfortably - that would indicate a different set of problems.

Answer 6

A while ago there was an article on Smashing Magazine about this. There were some alternatives like a looking glass or another icon, but basically there is always a button, or something which represents it.

Answer 7

Having a button makes it clearer that the text field is a search field. Merely having the text field itself indicate this in its contents is unsufficient.

Answer 8

Whether or not a button is required depends on the audience. Here are issues to consider:

• Technically oriented users may not need a button and will usually not have to think about hitting enter to submit a search request.
• Conversely non-technical people may not even know it is possible to hit enter to submit a search request. So no amount of thinking might work for them.
• There may be technology limitations that require a button. If you expect your audience to be browsing your form from a platform that does not provide an implicit way to submit a search request then you may need to provide an explicit button.

So essentially you need to know your audiences and determine where the edge cases lie and how critical they are. Using SO as an example, it is directed at technical users so an explicit button probably isn't required. However for a site like google where you need to be accessible to every single user using every possible platform, a clear explicit search button is a must.