When to use
A form is how people send something to Family Express: the For Business requests (fleet, gift cards, wholesale fuel, a Contract Bakery quote), the donation and sponsorship requests on Community, the three-step Fleet Card application and the email sign-up of the Home popup. All of them are built from one field, one radio card and one button, so a request for pricing reads exactly like a request for a donation.
The store search on the Home is a form too, with a single field and an attached submit; its full behavior lives in Search and filters.
Anatomy
| Part | Rule |
|---|---|
| Label | Hanken Grotesk at UI size (15 to 17 px, weight 500), always above the control. Required fields end in an asterisk; the rest end in (optional) at caption size. |
| Hint | Caption size (13 to 14 px), between the label and the control. Optional: no current form needs one. |
| Control | Paper fill, 1px ink edge, 16 px radius, 20 px side padding, body text (16 to 18 px) in ink. 64 px tall. |
| Example text | Inside the empty field, ink at 75 %. An example of the answer, such as e.g. 2,000, never the label. |
| Error line | UI size in ink, led by a small ink oval (16 × 10 px). Says how to fix the answer. |
Errors are ink, never red: red belongs to ORDER FOOD and the other primary actions. What marks a field as wrong is the edge doubling to 2 px, the oval and the words.
Text, date and select
Radio cards
| Part | Rule |
|---|---|
| Row | 16 px radius, 1px ink edge, 16 px top and bottom and 20 px side padding, 16 px between the mark and the text. The whole row is clickable. |
| Mark | The browser’s radio, 20 px, in ink. |
| Text | The option at UI size; a description under it at body S (15 to 17 px). |
| Group | Rows 12 px apart. Radio cards are used when each option needs a line of explanation; a plain list of short answers is a select. |
Checkbox
The consent box is the only checkbox in a form. The checkboxes that filter the menu are documented in Search and filters.
Actions
Form actions use the ink tone, not red: the red ORDER FOOD button stays the one primary action of the site. The actions sit at the end of the form, aligned right from 768 px. Under them, every For Business form closes with the same caption: We use these details only to respond to your request. and a link to Privacy.
On phones the actions span the full width and stack with the primary action on top, so the thumb reaches Continue before Back.
Stepped form
- Your info
- Card preference
- Confirm
- Contact name
- Dana Ruiz
- Business name
- Ruiz Landscaping
- Phone
- (555) 010-0144
- dana@example.com
- Number of vehicles
- 12
- Which program fits your fleet?
- Fleet Perks+
- One form, shown a step at a time. Every step lives in the same form; Continue checks only the fields of the current step. Enter in a field continues, as it would send a one-step form.
- The step title moves focus. After Continue, Back or Edit, focus lands on the new step’s title, announced as Step 2 of 3: Card preference.
- Without JavaScript all steps show at once with the submit button, so the application always works.
- Errors found on sending take people back to the first step that has one.
Store search
Messages
- First name: Enter your first name.
- Email: Enter an email address in the format name@example.com.
The inline errors use the same few sentences everywhere, each one saying what to do:
- Enter your first name. or Choose a product type.: the field’s own message when a required answer is missing.
- Enter an email address in the format name@example.com.
- Enter a valid phone number, or leave this blank.
- Enter a whole number, for example 2000.
- Enter a date, for example 2027-03-15.
- Keep this under 2,000 characters. (200 for one-line answers)
States
| State | Field edge | Under the field |
|---|---|---|
| Default | 1px ink | nothing, or the hint above the control |
| Focus | 1px ink, plus the 3 px ink focus ring | nothing |
| Error | 2 px ink | the oval and the message |
| Chosen (radio card) | 2 px ink, surface fill | nothing |
Errors appear only when people press Continue or send, never while they type, and stay until the next attempt. Under reduced motion the button fill and the rolling label change instantly.
Sizes
Form buttons are 44 px tall with 24 px side padding on phones and tablets and 48 px with 32 px from 1024 px; the popup keeps the 44 px size everywhere. Fields sit in two columns from 640 px with 24 px between them; the textarea, radio cards and wide fields span both.
Usage
- Ask for little. Name, company and email, then only what the team needs to reply. Phone is optional everywhere except the Fleet Card application.
- Name the send button after the request. Send to gift cards team, Request pricing, Submit application. Never Submit alone.
- Keep answers safe. When sending fails, every answer stays in place and the panel above says to try again.
- Same parts everywhere. A new form reuses this field, radio card, button and these messages as they are.
Accessibility
- Every control has a visible label tied to it; hints and errors are linked with
aria-describedby, so they are read with the field. - An invalid field is marked
aria-invalid, not only drawn with a thicker edge. Radio groups carry the error on the fieldset. - Browser validation is off so every error uses this one pattern: on Continue or send, focus moves to the error summary, which links to each field.
- The sent message is a status; the error summary and the not-sent panel are alerts.
- Buttons and radio rows are at least 44 px tall. The focus ring is always visible: 3 px ink, 3 px offset.
- A hidden field catches bots; people and assistive technology never meet it.
Source
- Figma
- Form field Form stepper
- Website
-
components/forms/Field.tsxcomponents/forms/BusinessForm.tsxcomponents/forms/StoreSearchForm.tsxcomponents/sections/HomePromoPopup.tsxcomponents/ui/OvalButton.tsxdata/business-forms.tslib/forms/business-forms.ts