Forms

A form is a set of fields in the order a person can answer them, plus the validation, error reporting and submit behaviour that decides whether those answers survive. The layout carries more than it appears to: one column, a heading wherever the subject changes, and two fields on a row only where the values are read as a single thing, a first and last name, and not much beyond that. The primary action comes last, on its own.

The submit path is where forms are won and lost. When something fails, say what failed at the top, link each item to its field, move focus to the first problem, and keep every value already typed: a form that empties itself on an error is worse than one that never submitted at all. Steps deserve the same scrutiny. They are justified when a later section depends on an earlier one, and they are pure friction when the sections are independent and a single scroll would have done the job.

9 blocks

Contact form

A marketing or support form that tells people who reads it, when they hear back, and what to fix when something is off

Contact form, thread

A contact form that feels like writing to a person: you see where your words went and who answers

Contact form, route

A contact form for several kinds of messages that go to different people

Contact form · stacked

A contact form that uses the page's width: the banner answers when you hear back and how else to reach the team, the form takes a phone and a brief

Contact form · stacked, sentence

A short enquiry that should feel like writing a line, not filling a form

Contact form · stacked, preview

A form where seeing the result helps: the person watches the email the team will receive take shape, then watch it arrive

Application form

A form long enough to need steps, where nobody should lose five steps of answers to a refresh

Application form, rail

A long application where people want to see what they have answered and how long is left

Application form, receipts

An application that reads as one page, where each answered step folds away

01

Using Forms

Reach for it when

  • A contact or support request short enough to answer in one sitting
  • An application long enough that one page would hide its own end, where a later section depends on earlier answers
  • Settings a person edits and saves, read out of order by somebody hunting one control
  • Any flow where a rejected answer has to be reported without losing the accepted ones

Reach for something else when

  • One value changes and applies at once: a switch or an inline field that saves itself, with no Submit to press
  • There is a single question: a prompt with two buttons, or one field in a dialog, costs far less than a form does
  • Steps are being added for their own sake: if nothing in the last section depends on the first, one column and a scroll is faster than Back and Next
02

Where it shows up

01

Contact and support requests

A marketing page asks for a name, an email address and a message, with the message counted so its limit is visible while it is being written. The banner carries the ask and the column carries the answers.

02

Multi-step applications

An application collects enough that one page would hide its own end. A step indicator names the sections, each step gets a heading, and the last reviews what the earlier ones collected before anything is sent.

03

Account settings

Settings are read out of order by people looking for one control, so each field keeps a visible label and its own hint, and the save action stays at the foot where the changed values end.

04

Checkout details

Billing and address entry pairs a first and last name on one row because they are read as one value, keeps the rest in a single column, and reports a declined card at the top without clearing the fields.

03

Questions

Should form labels sit above the field or inside it?

Above. A placeholder used as a label disappears the moment somebody types, so they lose the name of the field exactly when they are checking their answer, and it behaves badly for screen readers and browser autofill. Keep the label visible above the input, and use the placeholder, if at all, for an example of the format expected.

When should a form validate, while typing, on blur, or on submit?

All blocks
The Orvain Dispatch

Premium components, free in your inbox.

Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.

Just components, never spam. You can unsubscribe anytime.