Range filters use accessible input widgets (not freeform text)

Range filters rendered as freeform text inputs (<input type="text">) violate WCAG 2.2 SC 1.3.5 (Identify Input Purpose) and SC 4.1.2 (Name, Role, Value) — screen readers cannot convey the expected value type, and users relying on step controls or browser autofill get nothing. Beyond accessibility, freeform text introduces validation surface area: users enter "10-50", "$10 to $50", or "ten dollars" and the backend must parse all variants or return unexpected results. Semantic number or range inputs constrain input to a machine-readable format without custom parsing.

Replace freeform text range inputs with paired <input type="number"> elements, each carrying an explicit label and aria-label. In components/PriceFilter.tsx:

<label htmlFor="price-min">Minimum price</label>
<input
  id="price-min"
  type="number"
  value={min}
  onChange={e => setMin(e.target.value)}
  aria-label="Minimum price"
/>
<label htmlFor="price-max">Maximum price</label>
<input
  id="price-max"
  type="number"
  value={max}
  onChange={e => setMax(e.target.value)}
  aria-label="Maximum price"
/>

Alternatively, use shadcn/ui's Slider component, which ships with full ARIA support out of the box.