The <form> Element

Technical Summary

Definition / Categories

Nested forms are not a conforming document structure. When DOM manipulation or HTML parsing is involved, inspect source structure separately from the constructed DOM and the resulting form owners.

Content attributes

Form owner / Association

Form-associated elements can have a form owner: the form element with which they are associated. By default, a control is associated with its nearest ancestor form element.

A listed form-associated element can use the form attribute to explicitly associate with a particular form element in the same tree. This does not create nested forms; it separates control placement from ownership.

<form id="preferences" action="/save" method="post">
  <button type="submit">Save</button>
</form>

<input form="preferences" name="theme" value="dark">

Here the input is not a descendant of the form, but form="preferences" identifies its form owner. The ID match, same tree, and listed-element conditions still apply.

Form submission attributes

Submission attributes can be specified on the form element and on a submit button. Submitter attributes such as formaction, formmethod, formenctype, formnovalidate, and formtarget provide per-route overrides.

<form action="/search" method="get">
  <input name="q" type="search">
  <button type="submit">Search normally</button>
  <button type="submit" formaction="/export" formmethod="post">Export</button>
</form>

When one form exposes several submission routes, determine whether the form-level or submitter-level attribute supplies each value.

Submission model

user activation / requestSubmit()
  ↓
interactive constraint validation
  ↓
submit event (cancelable)
  ↓
construct the entry list
  ↓
encode it according to enctype
  ↓
submit and navigate according to action and method

This is an explanatory flow. The actual submission algorithm also branches on sandboxing, navigation, events, submitter state, entry-list construction, and encoding.

form.submit() bypasses interactive constraint validation and does not fire a submit event. form.requestSubmit() requests a normal-style submission that includes constraint validation and the submit event. Passing a submitter also brings that button's submission attributes and value into the process.

Entry list / Submittable controls

Being visible in the interface is not the same as being included in the entry list. Element type, form owner, name, disabled state, checkedness, and submitter state must be evaluated together.

Constraint validation

Submission can involve constraint validation of eligible form controls. The conditions may include required, type, range, length, pattern, and custom validity.

• novalidate or a submitter's formnovalidate suppresses validation during submission.
• A disabled control is barred from constraint validation.
• checkValidity() checks constraints statically; reportValidity() performs an interactive check that informs the user when invalid controls exist.
• Client-side validation is a user-experience feature, not a security mechanism. The server must validate received data too.

DOM interface

The form element is exposed through the HTMLFormElement interface. It provides form attributes, an elements collection, length, reset, validation, and submission-related APIs.

const form = document.querySelector('form');
form.elements;
form.checkValidity();
form.reportValidity();
form.reset();
form.requestSubmit();

API results also depend on form owners, control state, submitters, event listeners, and whether the document can navigate.

Fact / Evidence

Key facts are mapped to their conditions, review status, and evidence locations. Unresolved scope remains visible in the Coverage section below.

Evidence

1. HTML Standard: The form element — categories, content model, content attributes, and HTMLFormElement interface
2. HTML Standard: Categories — form-associated, listed, submittable, and resettable classifications
3. HTML Standard: Association of controls and forms — form owners and explicit association
4. HTML Standard: Constraints — constraint validation, validation APIs, and the security boundary
5. HTML Standard: Form submission — submission algorithm, entry lists, encoding, and submitters
6. HTML Accessibility API Mappings: form — starting point for platform accessibility mapping

Implementation Evidence

Implementation observations are recorded separately from normative claims. Unrun items are not treated as reviewed.

Shared fixture / record: Inside <form id="evidence-form" method="get">, the fixture includes an input with no type, explicit for/id association, implicit association with an input inside a label, required, disabled, and submit plus type-omitted button controls. Environment: Chrome 152.0.0.0 (Windows NT 10.0) / checked 2026-09-12.

Use the WPT repository for test mapping and the HTML-AAM form mapping for accessibility criteria.

Coverage / Open Issues

• ReviewedCategories, content model, main content attributes, form owners, submission attributes, key entry-list conditions, and the HTMLFormElement overview
• ReviewedThe validation and submit-event boundary between submit() and requestSubmit()
• OpenComplete entry-list branches, the formdata event, encodings, and special submitter conditions
• OpenMulti-browser implementation differences, exact WPT mapping, HTML-AAM, and assistive-technology observations
• OpenHistorical changes, server-side processing, compatibility, and Expert-gap Review

This is initial coverage. It does not claim that all facts about the form element have been verified or that every implementation produces the same result.

Related surface

For a first form, minimal examples, action and method, labels, and input checks, see the form element page in Yugien. For method="dialog" and dialog results, see the dialog element; for displayed calculation results that are not submitted, see the output element; for labelable association, see the label element; for multiline values and validation, see the textarea element; for control-side states, also see the input element and button element.