InputsComponentBeta

Field.

The relationship around an input.

Field connects labels, controls, help and errors. TextField adds the richer input visuals; Field.Control remains the low-level input contract. Horizontal layout keeps help and errors with the control.

Make it yours

Preparing the example…

PROPERTIES3

Composition

Anatomy

Field connects labels, controls, help and errors. TextField adds the richer input visuals; Field.Control remains the low-level input contract. Horizontal layout keeps help and errors with the control.

Component structure
Field.Root (name, invalid, disabled)
├── Field.Label
├── TextField or Field.Control
├── Field.Description
└── Field.Error

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

Orientation

The owning primitive controls layout and keyboard behavior as documented above.

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 Field props are forwarded; this table covers the options Dixy adds.

FieldRoot

PropType / descriptionDefault
orientation"horizontal" | "vertical"

Arrange a field and its label.

vertical

TextField

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

The height and type size of the control.

md
variant"soft" | "outline"

The visual surface treatment.

outline
radius"none" | "sm" | "md" | "lg" | "full"

Input rounding.

Theme.radius
material"matte" | "glossy" | "soft" | "metal" | "paper"

Optional static finish; import materials.css.

Theme.material
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-input-borderThe 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

Field.Label and Field.Description establish accessible relationships. Field.Error describes recovery; never rely on border color alone.

TabFocus the labeled control.

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.

Field is a relationship between parts. Control and Item retain registration and validation context; Validity exposes the current validation state without rendering a control. 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-input-border

Nothing up our sleeves

Source
UP NEXTButton Group