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.
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.
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.
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.
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.
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.
Validate on blur for the first pass, so nobody is told they are wrong halfway through typing an email address. Once a field has been marked invalid, re-check as they type, so the error clears the moment it is fixed. On submit, list everything that failed at the top, link each entry to its field, and move focus to the first one.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
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.
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.
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.
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.
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.
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.
Validate on blur for the first pass, so nobody is told they are wrong halfway through typing an email address. Once a field has been marked invalid, re-check as they type, so the error clears the moment it is fixed. On submit, list everything that failed at the top, link each entry to its field, and move focus to the first one.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.