RangeSlider

Two knobs on one rail for a span (a price range, a time window), with the rail lit between them. Slider's rail and knobs, with Slider's mass: the value moves at once and each knob catches up on a spring. They never cross; minGap keeps them apart. Each knob is its own slider for assistive tech, named from label.

Feel Two molded knobs on one lit rail, each with the weight of the Slider's.

Or let the agent fetch it: get_component("range-slider") on the Echo MCP server.

Installation

npx echo-ui-cli add range-slider

First time? Run npx echo-ui-cli init once — it sets the project up, and add refuses to run before it.

At a glance

Version: 0.3.0
Weight: 888 B · 42.6 KB with what it imports · 1.0 KB of CSS (minified and gzipped; React not counted)
Needs: @base-ui/react, gsap, slider (Echo, brought with it)
Keyboard: Two sliders, "{label}, minimum" and "{label}, maximum", each with arrow keys, Page Up/Down, Home and End.
Reduced motion: The knobs sit at their values without catching up.
Sound: tap per step, inside a SoundProvider.

Usage

tsx

import { RangeSlider } from "@/echo/range-slider";

<RangeSlider label="Hours" min={0} max={24} defaultValue={[9, 17]} />

Composition

RangeSlider → one rail with two Slider knobs (Base UI Slider with two thumbs)

Examples

Price

Knobs that read as money.

tsx

<RangeSlider label="Price" defaultValue={[20, 80]} max={200} step={5} formatValue={(v: number) => `$${v}`} />

Accessibility

Two sliders, "{label}, minimum" and "{label}, maximum", each with arrow keys, Page Up/Down, Home and End.
The knobs can't cross, so neither key path can make the span inverted.
formatValue sets each knob's aria-valuetext, so "$40" is read, not "40".

Tested against WCAG 2.2 AA on every release:

axe — No axe violations, in the component's own gallery and on its page.
keyboard — Every action is reachable and operable from the keyboard alone.
focus-visible — Focus is visible on every focusable part, in normal and forced-colors mode.
forced-colors — State stays visible when the look's colours are replaced by the system's.
target-size — Every target's real hit area is at least 24×24px, at every density.
reflow — Content reflows into 320px and survives a doubled text size.

Not covered: screen-reader: not yet verified by a person. Everything above is a machine check; a person has not yet driven this component with a screen reader.

Motion & sound

Motion tokens: springs
Reduced motion: The knobs sit at their values without catching up.
Sound: tap per step, inside a SoundProvider.

Props

RangeSlider props
Prop	Type	Default
`id`The element's id, so a <label for> or an aria-describedby can reach it.	`string`
`name`The field's name in a form submission, and the key react-hook-form registers.	`string`
`disabled`	`boolean`	`false`
`required`	`boolean`
`readOnly`	`boolean`
`autoFocus`Focus this control when it mounts. One per page, at most.	`boolean`
`onBlur`Fired on focus loss. react-hook-form validates onTouched and onBlur with it.	`function`
`onFocus`Fired when the control takes focus.	`function`
`onKeyDown`Keyboard handling you own — Enter to send, Escape to clear. Runs before Echo's.	`function`
`label` requiredWhat the span is ("Price"); the knobs are named "Price, minimum" and "Price, maximum".	`string`
`value`Controlled [low, high].	`unknown`
`defaultValue`	`unknown`	`[25,75]`
`onValueChange`Called with [low, high].	`function`
`min`	`number`	`0`
`max`	`number`	`100`
`step`	`number`	`1`
`minGap`How many steps the knobs keep between them; they never cross.	`number`	`1`
`size`As Slider: md is the fader, sm for dense rows.	`"sm" \| "md"`	`"md"`
`formatValue`How a value reads for assistive tech ("$40").	`function`

Anti-patterns

Never use a RangeSlider where exact values matter more than the feel of the span: give two NumberFields.

Changelog

v0.3.0 · 2026-10-12 · ChangedEvery item needs echo-ui-core 0.3.0 (all components). The drawn device, readability past AA and the design tests live in core, and the components that use them are built against it, so each item now declares echo-ui-core >=0.3.0 <0.4.0. Update core with the items: npm install echo-ui-core@^0.3.0 (or your package manager's), then npx echo-ui-cli update. An item whose files didn't change is the same code under a new version; the 0.2.0 files stay published.
v0.2.0 · 2026-10-04 · AddedThe rest of the inputs: Toggle, Toolbar, Meter, RangeSlider, and two instruments, Knob and LevelMeter. Plus start and end on Field. - Toggle / ToggleGroup: the quiet toolbar key. On is the cap held down in its well, not a light; a group shares one well, with arrow keys between its keys, multiple or at most one. - Toolbar / ButtonGroup: caps sharing one long well. A Toolbar is one tab stop with the arrow keys, Home and End along it, and sm controls; Toggles and ToggleGroups inside join its order by themselves. A ButtonGroup is the look alone. - Field start / end: a search icon or a currency sign engraved into the well before the text; a unit or a small key (clear, show password) after it. - Meter: a measurement in a range (storage, battery), a tube of lit plastic that settles to its level with a small slosh; marks engrave a limit without a second colour. - RangeSlider: two of Slider's knobs on one rail for a span, named "…, minimum" and "…, maximum"; they never cross. - Knob: a rotary cap with a lit scale. Drag it, wheel it once focused, or use the slider keys; it clicks at each step and settles onto each detent on a spring. - LevelMeter: a live level as LED cells with real ballistics and a held peak. It draws without re-rendering, stops once it's still, and tells a screen reader its level at most once a second.
v0.2.0 · 2026-10-04 · ChangedComments only, no behaviour change. Comments in the component source used to cite documents, milestones and ticket numbers from Echo's own planning, none of which exist in your project. The citations are gone and the sentences around them stay. Where a comment was only a citation, it now says what it meant. Three development warnings (HardwareButton's engraved/caption checks and StatusDot's missing-label check) also dropped the ticket code at the end of the message. echo-ui diff will show changes in most items; none of them are to code.
v0.2.0 · 2026-10-04 · ChangedAn item's version is now a function of declared data, not of how the changelog is formatted. The version an item ships under is published once and never rewritten, and it used to be inferred from prose: a regex for a bolded "Breaking" run across the whole unreleased section, and attribution by "does a bullet mention this name in backticks". One breaking entry therefore moved every item that changed that cycle, and an entry explaining that "Menu and Sheet are unchanged here" filed itself as a change to Menu and Sheet — which it really had.
v0.2.0 · 2026-10-04 · ChangedThe agent brief says Echo has not shipped. llms.txt and the MCP server's instructions led with npx echo-ui-cli init, and that name on npm is a reserved stub with no executable — so a model following the brief wrote an install step that fails with npx's own error. The brief now opens with the caveat, and the docs carry it on every surface that shows a command. One switch (CLI_RELEASED) silences all of them at launch, and a test refuses to let one move without the others. Affects all components only in what the brief says about installing them; no item's props, CSS or rendered semantics change.
v0.2.0 · 2026-10-04 · ChangedEcho's home is echo-ui.com. The registry, the docs and the packages all move to it from echo.nawwara.studio. Nothing was published under the old host, so no echo.json anywhere points at it and there is nothing to migrate — this is the last release where that is true.
v0.2.0 · 2026-10-04 · ChangedWeights, line heights, letter-spacing, z-index, border widths and icon sizes come from the theme scales in all components, with the old value as a fallback, so components keep working with echo-ui-core@0.0.1. Strays moved to the nearest step: most by under a pixel; HardwareButton icons are 14/16/20px (were 15/17/19).
v0.2.0 · 2026-10-04 · FixedContent now reflows into a 320px screen (400% zoom) and survives a doubled browser text size (WCAG 1.4.10, 1.4.4), across all components. Select's 180px floor, NumberField's readout, Segmented and Steps as flex items, EmptyState's grid columns, and Avatar's fixed-pixel disc all gave way; Panel counts its padding inside a width you set (box-sizing: border-box), so a <Panel style={{ width: 220 }}> is now 220px wide overall rather than 260px.

Preview