Think of filling out a sign-up page. Clear fields make the job simple; confusing fields make people leave.
What You Need to Know
This example uses the browser’s built-in image control, so you do not have to create a picker from scratch.
In this example: use a labeled image as a form submission control.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/search" method="get">
<label for="query">Search books</label>
<input id="query" name="query" type="search">
<input type="image" src="images/search-button.png" alt="Search books" width="100" height="40">
</form>Let’s Read the Code
- type: Type changes what sort of control or resource the browser uses.
- <form>: The form groups controls and identifies where submitted data goes.
- <label>: The label tells people what the input is for. A matching for/id pair makes the label clickable.
- for: For connects a label or output with a control by ID.
What the example shows: Clicking the image submits the form and adds coordinates for the clicked point.
What Happens in the Browser?
The HTML controls work in the browser, but saving an answer requires the example action path to be handled by a real server.
Where does the answer go? The example uses the submitted name(s) query. Those names help the receiving server identify each answer. A label is for people; a name attribute is for the form data; an ID connects elements in the page.
Your Turn
Inspect the query parameters after pressing the image button on a working server.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Provide meaningful alt text because the image acts as a button.
Key Takeaways
- A control needs a clear label and, when submitted, a meaningful name and value.
- type: Type changes what sort of control or resource the browser uses.
- Remember that HTML form rules help the visitor, but server-side code must decide whether received data is valid.