Content · Web Development · HTML

HTML Form Accessibility: Errors, Hints, and Field Groups

Form Accessibility: Errors, Hints, and Field Groups: The fieldset names the group and the hint text explains the purpose of the email field. Includes a practical HTML example and an explanation.

1 views Published Oct 19, 2026 Updated Oct 19, 2026 Admin

Imagine asking a friend for some information on a webpage. The field should explain exactly what you need.

What You Need to Know


The fieldset names the group and the hint text explains the purpose of the email field.

In this example: annotate a password requirement hint.

Try the Example


Take a look at the example. We’ll explain the important lines right below it.

<form action="/sign-up" method="post">
    <fieldset>
        <legend>Account information</legend>
        <label for="account-email">Email</label>
        <input id="account-email" name="email" type="email" aria-describedby="email-hint" required>
        <p id="email-hint">We will use this email for account messages.</p>
    </fieldset>
    <button type="submit">Continue</button>
</form>

Let’s Read the Code


  • <form>: The form groups controls and identifies where submitted data goes.
  • <fieldset>: The fieldset keeps related choices together.
  • 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) email. 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


Add a password field with a visible label and a short hint.

Common Beginner Mistakes


  • Copying the example without giving the fields a clear label and a usable name.
  • Placeholder text is not a reliable replacement for a real label.

Key Takeaways


  • A control needs a clear label and, when submitted, a meaningful name and value.
  • <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.
Share this resourceSend this page to someone who may find it useful.