InputsComponentBeta

Form.

A complete path from input to feedback.

Form remains a native form and keeps Base UI validation. Field names connect server errors to controls. gap changes spacing only; it does not replace submit handling or error recovery.

Make it yours

Preparing the example…

PROPERTIES2

Composition

Anatomy

Form remains a native form and keeps Base UI validation. Field names connect server errors to controls. gap changes spacing only; it does not replace submit handling or error recovery.

Component structure
Form (onSubmit, errors)
├── Field.Root → label + control + help/error
└── Button type=submit

A place to start

Usage

Import the stylesheet once at your application root. This complete example reflects the properties selected above.

Loading example…

Details that make a difference

Examples & states

Field spacing

Spacing changes independently of validation and field semantics.

Example loads as it comes into view.

Loading source…

The finer details

API reference

Generated from Dixy’s local TypeScript interfaces. Native and Base UI Form props are forwarded; this table covers the options Dixy adds.

Form

PropType / descriptionDefault
gap"sm" | "md" | "lg"

Space between fields without changing validation.

md
Explore the full Base UI API

Built from the same foundations

Styling tokens

Change Theme settings above to compare appearance, accent, neutral, radius, spacing density, motion and direction. Override component aliases on a Theme root so custom properties follow portaled content too. The wrapper merges className, style, refs and render composition with its owning primitive.

TokenPurpose
--dixy-primitive-gapThe component-specific starting point.
--dixy-font-label-mdControl label font and line height; body roles remain readable in text inputs.
--dixy-color-background-selectedSelected surfaces use semantic color across appearances.
--dixy-color-border-focusFocus indication remains visible independently of shadows.
--dixy-spacing-inset-smDensity-aware component padding.
--dixy-motion-transition-feedbackShort state feedback, reduced by the inherited motion setting.
Explore theme customization

Consider everyone

Accessibility

Form coordinates validation and submission. Native required, name and submit semantics remain valuable. Provide meaningful names and verify the complete interaction with a keyboard. Color alone must not communicate state.

Tab / Shift + TabMove through the available controls.
Arrow keys / SpaceUse the primitive’s directional or activation behavior where applicable.

Target: WCAG 2.2 AA. Automated tests cover selected behavior; manual screen-reader, contrast, and zoom validation remain part of the release checklist.

THE THINKING BEHIND IT

Build it. Then understand it.

Form coordinates validation and submission. Native required, name and submit semantics remain valuable. Component aliases reference Dixy semantic tokens; refs, events and render composition are forwarded unchanged. Visual settings follow Dixy shirt sizes, contextual radii and semantic tokens where applicable. Static finishes are optional, and reduced motion is immediate. Base UI keeps refs, state, events, keyboard and presence; this implementation pass does not establish WCAG conformance.

A token to follow--dixy-primitive-gap

Nothing up our sleeves

Source
UP NEXTMenu