Content · Web Development · HTML

HTML Accessible Rate-Your-Experience Form

Accessible Rate-Your-Experience Form: One shared name allows only one rating. The legend tells a screen reader what the group is asking. 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


One shared name allows only one rating. The legend tells a screen reader what the group is asking.

Try the Example


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

<form action="/rating" method="post">
    <fieldset>
        <legend>How was your experience?</legend>
        <label><input type="radio" name="rating" value="1" required> 1 — Poor</label>
        <label><input type="radio" name="rating" value="3"> 3 — Okay</label>
        <label><input type="radio" name="rating" value="5"> 5 — Great</label>
    </fieldset>
    <button type="submit">Send rating</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.
  • type: Type changes what sort of control or resource the browser uses.
  • name: The name is the key used for the submitted value.

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) rating. 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 the missing 2 and 4 choices with readable descriptions.

Common Beginner Mistakes


  • Copying the example without giving the fields a clear label and a usable name.
  • Numbers alone can be unclear, so write what the endpoints mean.

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.