Slider
Provide the governed NexWell Slider contract for input & control interfaces.
Purpose
Provide the governed NexWell Slider contract for input & control interfaces.
NexWell tokens and WCAG behavior are authoritative; missing source fields remain explicit gaps.
When to use
Use Slider only for its documented input & control purpose.
When not to use
Do not repurpose Slider as an unrelated interaction or bypass its tokens.
Anatomy
- trigger or container
- content
- state indicator
Specifications, variants, sizes, and states
Specifications
- Exact dimensions, padding, gaps, icon sizes, radius, and typography: source-verification-required.
- Implementation behavior is inspectable below; it is not evidence of founder approval.
Variants and sizes
default
source-verification-required: no governed component-specific size matrix is available
States
default · focus-visible · disabled where actionable · responsive · reduced motion
Measurements and typography
Every field is represented. A status is not a value: unresolved evidence cannot be converted into an implementation number.
source-verification-requiredNo approved exact value may be inferred.source-verification-requiredNo approved exact value may be inferred.partialNo approved exact value may be inferred.source-verification-requiredNo approved exact value may be inferred.source-verification-requiredNo approved exact value may be inferred.source-verification-requiredNo approved exact value may be inferred.State matrix
Actual implementation states are listed below. Requested universal states not supported by the component API remain explicitly unclaimed.
React and TypeScript API
Public properties
approved-current Generated from the package registry; controls expose only the supported subset listed here.
labelvalueminmaxonChangeimport { Slider } from "@nexwellaifactory/components";
// label
// value
// min
// max
// onChange
export function Example() {
return <Slider />;
}Usage and content
Do
Use Slider with a clear accessible name and evidence-backed behavior.
Don’t
Do not repurpose Slider as an unrelated interaction or bypass its tokens.
Content rules
- Use concise, task-specific labels.
- Do not communicate state through color alone.
- Allow localized text to wrap without hiding critical actions.
Accessibility, keyboard, responsive, and RTL
Accessibility
- Programmatic name
- Programmatic state
- Logical focus order
- No color-only meaning
Keyboard
- Native behavior where available
- Arrow-key composite navigation where required
- Escape dismissal and focus restoration for overlays
Responsive and RTL
Reflows, scrolls, or becomes a bounded overlay without hiding critical actions.
Logical properties; arrow meaning follows spatial direction.
Actual package output
Interactive example
Preview width changes the bounded canvas; use the RTL control below to inspect logical layout.
Token mapping and source evidence
Traceable implementation
Uber-derived structural evidence, adapted through approved NexWell decisions.
semantic colorfoundation spacingfoundation shapefoundation motiondocs/source-audit/component-evidence-matrix.csv :: slider
Missing fields in the source remain documented source absence, not requirements invented by the implementation.
Evidence completeness
10 associated local source records. Statuses below come directly from the DS-13 Checkpoint 1 component evidence matrix.
overviewpartialanatomypartialvariantspartialsizespartialdimensionssource-verification-requiredpaddingsource-verification-requiredgapspartialicon_sizessource-verification-requiredtypographysource-verification-requiredwidth_behaviorsource-verification-requiredcontent_behaviorsource-verification-requiredtruncation_wrappingsource-verification-requiredstatespartialaccessibilitypartialkeyboardpartialresponsivepartialrtlsource-verification-requiredmotionsource-verification-requiredreact_apipartialtoken_mappingsource-verification-requiredimplementation_mappingsource-verification-requiredvisual_redlinessource-verification-requiredtestssource-verification-requiredCross-platform implementation
React / TypeScript: current package API is shown above.
Flutter: source-verification-required — no canonical Flutter API or implementation mapping exists, and this web portal does not infer one.
AI agents: consume approved records only; preserve proposed and unresolved statuses and import the public component instead of recreating it.