Choose the right field for each form question

Use written answers when the visitor supplies the wording

A short text field suits a brief answer such as an organisation name. A message field gives room for an explanation. Do not make someone describe a complicated problem in a field that visually suggests a few words, or ask for an essay when your team only needs a short identifying detail.

Use the email, telephone and URL types when the answer has that purpose. Treat reference codes differently from quantities: an enquiry number such as 00427 is an identifier, not an amount to calculate. A text field preserves that distinction. For quantities, tell people what the number measures and choose limits that match the service.

Decide whether one or several choices can apply

Radio buttons are for one answer from a group; checkboxes allow several. This distinction is reflected in GOV.UK's component guidance. Start with the meaning of the question: “Preferred contact method” asks for one preference, while “Days you are available” may have several true answers.

Write choices at the same level of detail. A list containing “Website”, “Support” and “New accessibility review for a large site” mixes subject, task and scope. A simpler list might separate the request type from the details. Include a reasonable route when none of your choices fits; do not make people pick an inaccurate answer just to continue.

• Use “Choose one” when a single-choice instruction adds clarity.
• Use “Choose all that apply” for a multiple-choice question.
• Check overlapping choices before publishing.
• Do not combine an exclusive “None” option with other checkboxes unless the behaviour prevents contradictory answers.

Use a dropdown only when it helps the task

For a short list that needs comparison, start by considering visible choices. GOV.UK advises caution with selects in public services and suggests reducing long option lists where possible. A dropdown saves space, but that alone does not establish that it is easier to answer.

Review a long list for your own internal structure. Visitors should not have to understand every department to decide where a message belongs. It may be better to ask what they need and let the team handle the handoff. Where a dropdown remains appropriate, use clear option names and test finding an option with both keyboard and touch.

Test the whole question, including its choices

A choice group needs a question as well as names for its individual options. W3C describes grouping related controls visually and programmatically. In Accessible Forms, radio and checkbox groups provide that structure; you still need to write a question that explains what the group means.

Try realistic edge cases: two available days, an unfamiliar organisation name, an answer that fits none of your categories and a quantity at a permitted boundary. Watch whether people change a correct answer to satisfy the control. That is a signal to revisit the field or question, rather than add more instructions around it.

Using Accessible Forms

Choose a question's type in the builder, then write its label, instructions and options together.

In Free: Free includes text, email, telephone, URL, number, date, time, message, dropdown, radio, checkbox, consent and section-heading types. Radio and checkbox groups use a shared group label.