Separator.
A quiet boundary between related things.
Use semantic separation only when it communicates structure. Decorative lines should not add unnecessary announcements.
Make it yours
Preparing the example…
Composition
AnatomySeparator is a single semantic divider rather than a compound family. Orientation comes from Base UI. Emphasis adjusts visual contrast without changing semantics.
Separator (orientation, emphasis)A place to start
UsageImport the stylesheet once at your application root. This complete example reflects the properties selected above.
Loading example…
Details that make a difference
Examples & statesEmphasis
Compare subtle and strong separators within the same content.
Loading source…
Orientation
The owning primitive controls layout and keyboard behavior as documented above.
Loading source…
The finer details
API referenceGenerated from Dixy’s local TypeScript interfaces. Native and Base UI Separator props are forwarded; this table covers the options Dixy adds.
Separator
| Prop | Type / description | Default |
|---|---|---|
emphasis | "strong" | "subtle"Divider emphasis. | subtle |
Built from the same foundations
Styling tokensChange 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.
| Token | Purpose |
|---|---|
--dixy-primitive-gap | The component-specific starting point. |
--dixy-font-label-md | Control label font and line height; body roles remain readable in text inputs. |
--dixy-color-background-selected | Selected surfaces use semantic color across appearances. |
--dixy-color-border-focus | Focus indication remains visible independently of shadows. |
--dixy-spacing-inset-sm | Density-aware component padding. |
--dixy-motion-transition-feedback | Short state feedback, reduced by the inherited motion setting. |
Consider everyone
AccessibilityUse semantic separation only when it communicates structure. Decorative lines should not add unnecessary announcements. Provide meaningful names and verify the complete interaction with a keyboard. Color alone must not communicate state.
Target: WCAG 2.2 AA. Automated tests cover selected behavior; manual screen-reader, contrast, and zoom validation remain part of the release checklist.
Build it. Then understand it.
Use semantic separation only when it communicates structure. Decorative lines should not add unnecessary announcements. Component aliases reference Dixy semantic tokens; refs, events and render composition are forwarded unchanged.
--dixy-primitive-gap