Lead:  Liav Nadler

...

A form is a collection of input fields, allowing users to enter data that is then sent for further processing.
Forms may appear in workspaces, dialog popups, popovers,wizards,filter panes, details panes and cards.

...

• A form consists of two areas: the input area and the action area.

• The input area may contain any set of input fields, including text fields, dropdown menus, checkboxes, radio buttons etc.

• The action area usually consists of a submit button (Save, or Create, or Update etc.) and additional actions, if needed.

• In dialog popups, wizards,filter panes, details panes and cards, it is common to have an additional Cancel button.

...

• Where possible, field labels will appear above the input field (for example, above a text field or a set of radio buttons).

• Where relevant, a red mandatory indicator (*) will show next to the label.

• Where relevant, a help icon will appear next to the label (aligned to the right side of the field, if possible).

• A collection of related fields can be grouped into a section. For example, fields like Email and Phone can be found under a section called Contact Information.

• For forms with inline inputs, see Inline Inputs.

...

• The action area will always be visible:

  • In case the form takes up the entire workspace, the action area will appear at the top of the page.

  • In any other case, the action area will appear below the form, separated by a horizontal line.

    • In dialog popups, popovers,wizards,filter panes, details panes and cards, the action area will appear at the bottom of the container.

    • In workspaces:

      • If the form does not exceed the height of its container, the action area will appear below the last field of the form.

      • If the form exceeds the height of its container, the action area will stick to the bottom of the container, allowing users to scroll the form above it.

...

• In general, form fields should have one column. Closely related fields (e.g., first name and last name) can appear side by side.

• A collection of related fields should be grouped under a clear title (see examples above).

Issues to cover

• Ask Femi about web SDK form guidance

Examples

Accessibility compliance

Unless otherwise specified, see our general compliance information in Fundamentals - Accessibility

text highlight when using a keyboard + using arrows when in edit mode (left, up or home to set the insertion point at the beginning; right, down or end to set it at the end).

Design

...