Think of filling out a sign-up page. Clear fields make the job simple; confusing fields make people leave.
What You Need to Know
Inputmode=decimal suggests a keyboard suited to decimal entry while the underlying control remains text.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<form action="/price" method="get">
<label for="price">Price</label>
<input id="price" name="price" type="text" inputmode="decimal" placeholder="12.50">
<button type="submit">Continue</button>
</form>Let’s Read the Code
- <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.
- id: An id uniquely identifies an element on this page.
Read the named elements and attributes together. They explain how the browser connects this feature to the rest of the page.
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) price. 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
Move through the example without a mouse. Read each control name and current state aloud as if describing it to a friend.
Common Beginner Mistakes
- Copying the example without giving the fields a clear label and a usable name.
- Decimal separators vary by locale, and inputmode does not validate numeric content.
Key Takeaways
- Choose the HTML feature that explains this task clearly.
- <form>: The form groups controls and identifies where submitted data goes.
- A meaningful HTML element is usually a stronger starting point than adding an ARIA role to a generic div. Also check what happens using only the keyboard.