A form should feel easy to use. The visitor sees a question, gives an answer, and needs to know what will happen next.
What You Need to Know
Here is a small, realistic example focusing on meter.
In this example: show disk capacity usage.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<label for="battery">Battery level</label>
<meter id="battery" min="0" max="100" low="20" high="80" optimum="100" value="65">65%</meter>
<p>Battery is at 65%.</p>Let’s Read the Code
- <label>: The label tells people what the input is for. A matching for/id pair makes the label clickable.
- <meter>: The meter element represents a measurement within a known range.
- for: For connects a label or output with a control by ID.
- id: An id uniquely identifies an element on this page.
What the example shows: The markup gives the browser a clear starting point for meter. Look at the labels, names, and values rather than only the visual appearance.
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.
Keep the form understandable. Put each label next to the right control, group related questions, and make the submit action clear. A good form is more than a collection of inputs.
Your Turn
Change one meaningful attribute, submit the form, and compare the result with the original.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- A browser may render the control differently from another browser without changing the HTML meaning.
Key Takeaways
- Choose the HTML feature that explains this task clearly.
- <label>: The label tells people what the input is for. A matching for/id pair makes the label clickable.
- Test the behavior you expect rather than trusting how the snippet looks in your editor.