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 autofocus.
Try the Example
Take a look at the example. We’ll explain the important lines right below it.
<dialog id="welcome-dialog">
<p>Choose how to continue.</p>
<button type="button" autofocus>Continue</button>
</dialog>
<script>
document.querySelector("#welcome-dialog").showModal();
</script>Let’s Read the Code
- <dialog>: Dialog provides a browser-managed dialog container; modal display may need showModal or a supported command.
- <button>: The button offers an action; its type or command determines what happens.
- id: An id uniquely identifies an element on this page.
- type: Type changes what sort of control or resource the browser uses.
What the example shows: The markup gives the browser a clear starting point for autofocus. 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
- A control needs a clear label and, when submitted, a meaningful name and value.
- <dialog>: Dialog provides a browser-managed dialog container; modal display may need showModal or a supported command.
- 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.