@umriss-ui/charts 0.42.0 → 0.43.0

package/docs/llms-full.md

@@ -1,4 +1,4 @@
-# @umriss-ui/charts 0.42.0
+# @umriss-ui/charts 0.43.0
 
 > React canvas chart library for data-dense dashboards - line, area, bar, box plot, scatter, control and Pareto charts. Few chart kinds, drawn well, fast.
 
@@ -181,7 +181,7 @@ export default function WatchLatency() {
           }
         />
         <CardBody>
-          <Chart height={260} syncId="checkout" ariaLabel="Checkout latency today against its objective">
+          <Chart height={260} syncId="checkout" aria-label="Checkout latency today against its objective">
             <XAxis value="t" time domain={TODAY} />
             {/* Tick labels as wide as the error rate's keep the two crosshairs in one column. */}
             <YAxis label="ms" />
@@ -196,7 +196,7 @@ export default function WatchLatency() {
       <Card data-callout="4">
         <CardHeader title={`${CHECKOUT.name} failed requests`} />
         <CardBody>
-          <ErrorChart height={140} syncId="checkout" ariaLabel="Checkout error rate today">
+          <ErrorChart height={140} syncId="checkout" aria-label="Checkout error rate today">
             <XAxis value="t" time domain={TODAY} />
             <YAxis label="%" tickCount={3} tickFormat={(v) => v.toFixed(1)} />
             <LimitLine value={ERROR_ALERT} severity="alarm" label={`Alert at ${ERROR_ALERT} %`} inExtent />
@@ -408,7 +408,7 @@ const DRIVING_NOW = FLEET.filter((one) => one.driving).length;
 function FleetLanes() {
   const { Chart, XAxis, YAxis, StateBand } = useChart(FLEET[0]!.points);
   return (
-    <Chart height={320} ariaLabel="What each vehicle has done today, lane by lane">
+    <Chart height={320} aria-label="What each vehicle has done today, lane by lane">
       <XAxis value="t" time domain={DAY} />
       <YAxis grid={false} />
       {FLEET.map((one) => (
@@ -430,7 +430,7 @@ function FleetLanes() {
 function IdleMinutes() {
   const { Chart, XAxis, YAxis, Bar } = useChart(FLEET);
   return (
-    <Chart height={200} ariaLabel="Idle minutes per vehicle so far today">
+    <Chart height={200} aria-label="Idle minutes per vehicle so far today">
       <XAxis value={(d) => d.vehicle.plate} />
       <YAxis label="min" tickCount={4} />
       <Bar value="idle" name="Idle" color={VEHICLE_STATES[IDLE]!.color} barWidth={0.6} />
@@ -534,7 +534,7 @@ const monthName = (month: string) => new Date(`${month}-01T00:00`).toLocaleStrin
 function GapPerCentre() {
   const { Chart, XAxis, YAxis, Bar } = useChart(YEAR);
   return (
-    <Chart height={240} ariaLabel="Outlook minus budget for the year, per cost centre">
+    <Chart height={240} aria-label="Outlook minus budget for the year, per cost centre">
       <XAxis value="name" />
       <YAxis label="k€" tickFormat={euros} />
       {/* One series per sign, stacked on one another so that each bar stands centred on its cost centre. */}
@@ -555,7 +555,7 @@ function GapPerCentre() {
 function MarketingByMonth() {
   const { Chart, XAxis, YAxis, Bar, Line } = useChart(MONTHLY);
   return (
-    <Chart height={260} ariaLabel="Marketing's budget, actual and forecast per month">
+    <Chart height={260} aria-label="Marketing's budget, actual and forecast per month">
       <XAxis value="month" categoryLabel={monthName} />
       <YAxis label="k€" tickFormat={euros} />
       <Bar value={(d) => thousands(d.budget)} name="Budget" color="var(--uc-color-text)" barWidth={0.7} format={euros} />
@@ -733,7 +733,7 @@ const HOLDERS: readonly Holder[] = PEOPLE.map((person) => ({
 function SprintBurnDown() {
   const { Chart, XAxis, YAxis, Line } = useChart(BURNDOWN);
   return (
-    <Chart height={280} ariaLabel={`${SPRINT.name}: hours left per working day against an even pace`}>
+    <Chart height={280} aria-label={`${SPRINT.name}: hours left per working day against an even pace`}>
       <XAxis value={dayOf} label="Working day" />
       <YAxis label="Hours left" domain={[0, BURNDOWN[0]!.ideal]} />
       <Line value="ideal" name="Even pace" color="var(--uc-color-text)" dash={[4, 4]} strokeWidth={1} />
@@ -747,7 +747,7 @@ function SprintBurnDown() {
 function OpenPerPerson() {
   const { Chart, XAxis, YAxis, Bar } = useChart(HOLDERS);
   return (
-    <Chart height={200} ariaLabel="Estimated hours of unfinished items per person">
+    <Chart height={200} aria-label="Estimated hours of unfinished items per person">
       <XAxis value="name" />
       <YAxis label="h" tickCount={4} />
       <Bar value="open" name="Estimate" barWidth={0.6} />
@@ -974,7 +974,7 @@ const clock = (minute: number) => {
 function LengthInControl() {
   const { Chart, XAxis, YAxis } = useChart(SHIFT.samples);
   return (
-    <Chart height={280} syncId="tiles" ariaLabel="Control chart of the tile length over the early shift">
+    <Chart height={280} syncId="tiles" aria-label="Control chart of the tile length over the early shift">
       <XAxis value="minute" domain={DOMAIN} ticks={HOURS} tickFormat={clock} />
       <YAxis label="mm" />
       <LimitLine value={SPEC.nominal + SPEC.tolerance} severity="alarm" label="USL" inExtent />
@@ -996,7 +996,7 @@ function LengthInControl() {
 function KilnZone() {
   const { Chart, XAxis, YAxis, Line } = useChart(SHIFT.readings);
   return (
-    <Chart height={200} syncId="tiles" ariaLabel="Kiln zone 3 temperature over the early shift">
+    <Chart height={200} syncId="tiles" aria-label="Kiln zone 3 temperature over the early shift">
       <XAxis value="minute" domain={DOMAIN} ticks={HOURS} tickFormat={clock} />
       <YAxis label="°C" tickCount={4} />
       <LimitBand from={KILN.tolerance[0]} to={KILN.tolerance[1]} severity="warning" label="Tolerance" />
@@ -1090,7 +1090,7 @@ const SIGN_INS = [
 export default function FirstChart() {
   const { Chart, XAxis, YAxis, Line } = useChart(SIGN_INS);
   return (
-    <Chart height={240} ariaLabel="Sign-ins per hour today">
+    <Chart height={240} aria-label="Sign-ins per hour today">
       <XAxis value="t" time />
       <YAxis label="Sign-ins per hour" />
       <Line value="signIns" name="Sign-ins" />
@@ -1196,7 +1196,7 @@ const SIGN_IN = metrics("sign-in");
 function Requests({ width, height }: { width?: number; height: number }) {
   const { Chart, XAxis, YAxis, Line } = useChart(SIGN_IN);
   return (
-    <Chart width={width} height={height} ariaLabel="Sign-in requests per minute today">
+    <Chart width={width} height={height} aria-label="Sign-in requests per minute today">
       <XAxis value="t" time />
       <YAxis />
       <Line value="requests" name="Requests per minute" />
@@ -1242,12 +1242,6 @@ From `ChartProps` — the full table stands on [Chart](#chart-1).
 | [`height`](#chart-1) | `number` | fills the frame, at least 300 px | Height in CSS pixels, fixed. Left out, the chart fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 300 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). |
 | [`children`](#chart-1) | `ReactNode` | — | The axes, series and companions of this chart. They draw nothing themselves: each registers its configuration and the scene draws it, and the order in the JSX is the drawing order. |
 
-###### Accessibility
-
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| [`ariaLabel`](#chart-1) | `string` | — | Required in DEV through a warning. |
-
 From `XAxisProps` — the full table stands on [Axis](#axis).
 
 | Prop | Type | Default | Description |
@@ -1345,7 +1339,7 @@ const DEPOT_DAYS: readonly DepotDay[] = (() => {
 export default function Mixed() {
   const { Chart, XAxis, YAxis, Bar, Area, Line, Scatter } = useChart(DEPOT_DAYS);
   return (
-    <Chart height={320} ariaLabel="North depot: pallets in, out and on hand over fourteen days">
+    <Chart height={320} aria-label="North depot: pallets in, out and on hand over fourteen days">
       <XAxis value="day" label="Day of March" tickCount={7} />
       <YAxis label="Pallets" />
       <Bar value="arrived" name="Arrived" />
@@ -1377,7 +1371,7 @@ const NOTHING: Reading[] = [];
 function Latency({ empty }: { empty?: string }) {
   const { Chart, XAxis, YAxis, Line } = useChart(NOTHING);
   return (
-    <Chart height={220} ariaLabel="Latency of a service without readings" empty={empty}>
+    <Chart height={220} aria-label="Latency of a service without readings" empty={empty}>
       <XAxis value="t" time />
       <YAxis label="ms" />
       <Line value="p95" name="Refunds" />
@@ -1515,14 +1509,14 @@ export default function KeyboardAndScreenReader() {
   const { Chart: Diagramm } = german;
   return (
     <div>
-      <Chart height={200} ariaLabel="Search latency over last week">
+      <Chart height={200} aria-label="Search latency over last week">
         <XAxis value="t" time domain="data" zoomable />
         <YAxis label="ms" />
         <Line value="p95" name="p95" />
         <Line value="p50" name="p50" />
         <Tooltip mode="x" />
       </Chart>
-      <Diagramm height={200} ariaLabel="Antwortzeiten der Suche in der letzten Woche" wording={GERMAN_CHARTS_WORDING}>
+      <Diagramm height={200} aria-label="Antwortzeiten der Suche in der letzten Woche" wording={GERMAN_CHARTS_WORDING}>
         <XAxis value="t" time domain="data" zoomable />
         <YAxis label="ms" />
         <Line value="p95" name="p95" />
@@ -1619,7 +1613,7 @@ const monthName = (month: string) => MONTH_NAMES[Number(month.slice(5)) - 1] ??
 function Forecasts({ encoding }: { encoding?: "marks" }) {
   const { Chart, XAxis, YAxis, Line } = useChart(LEDGER);
   return (
-    <Chart height={240} ariaLabel="Forecast of four cost centres per month" encoding={encoding}>
+    <Chart height={240} aria-label="Forecast of four cost centres per month" encoding={encoding}>
       <XAxis value="month" categoryLabel={monthName} />
       <YAxis label="€" />
       {CENTRES.map((c) => (
@@ -1710,7 +1704,7 @@ const DEPOT_DAYS: readonly DepotDay[] = (() => {
 export default function MarksOnEveryKind() {
   const { Chart, XAxis, YAxis, Bar, Area, Line, Scatter } = useChart(DEPOT_DAYS);
   return (
-    <Chart height={320} ariaLabel="North depot's pallets, told apart by marks" encoding="marks">
+    <Chart height={320} aria-label="North depot's pallets, told apart by marks" encoding="marks">
       <XAxis value="day" label="Day of March" tickCount={7} />
       <YAxis label="Pallets" />
       <Bar value="arrived" name="Arrived" />
@@ -1964,7 +1958,7 @@ const STATES = vehicleDay("v2");
 function BatteryAndStates() {
   const { Chart, XAxis, YAxis, Line, StateBand } = useChart(BATTERY);
   return (
-    <Chart height={280} ariaLabel="An e-van's battery against its reserve, above its states" encoding="marks">
+    <Chart height={280} aria-label="An e-van's battery against its reserve, above its states" encoding="marks">
       <XAxis value="t" time label="Time" tickCount={4} />
       <YAxis domain={[-40, 100]} ticks={[0, 20, 40, 60, 80, 100]} label="%" />
       {/* One lane, and four places of room above it for the course. */}
@@ -1982,7 +1976,7 @@ function BatteryAndStates() {
 function SuccessCells() {
   const { Chart, XAxis, YAxis, Matrix } = useChart(SUCCESS_BY_HOUR);
   return (
-    <Chart height={280} ariaLabel="Successful requests per service and hour, by limits and by marks" encoding="marks">
+    <Chart height={280} aria-label="Successful requests per service and hour, by limits and by marks" encoding="marks">
       <XAxis value="hour" ticks={[0, 6, 12, 18]} tickFormat={(v) => `${v}:00`} label="Hour" />
       <YAxis />
       <Matrix
@@ -2044,7 +2038,7 @@ const NOTHING: Reading[] = [];
 function Latency({ rows, loading, label }: { rows: Reading[]; loading: boolean; label: string }) {
   const { Chart, XAxis, YAxis, Line } = useChart(rows);
   return (
-    <Chart height={220} ariaLabel={label} loading={loading}>
+    <Chart height={220} aria-label={label} loading={loading}>
       <XAxis value="t" time />
       <YAxis label="ms" />
       <Line value="p95" name="Refunds" />
@@ -2127,7 +2121,7 @@ const BY_SERVICE = [...new Set(ERRORS.map((row) => row.service))].map((service)
 export default function SeriesFromLongRows() {
   const { Chart, XAxis, YAxis, Line } = useChart(ERRORS);
   return (
-    <Chart height={260} ariaLabel="Failed requests per service and hour this morning">
+    <Chart height={260} aria-label="Failed requests per service and hour this morning">
       <XAxis value="t" time />
       <YAxis label="Errors %" />
       {BY_SERVICE.map(({ service, rows }) => (
@@ -2161,7 +2155,7 @@ export default function SeriesFromLongRows() {
 
 #### Accessibility
 
-The plot is an image named by `ariaLabel` and described by a summary: the series, the visible stretch and each series' lowest and highest value in it. With a `Tooltip` it becomes one tab stop, the role `application` read as "chart", and the summary adds the keys. Pass `ariaLabel`: without it the plot has no name, and the development build warns.
+The plot is an image named by `aria-label` and described by a summary: the series, the visible stretch and each series' lowest and highest value in it. With a `Tooltip` it becomes one tab stop, the role `application` read as "chart", and the summary adds the keys. Pass `aria-label` (or `aria-labelledby`): without it the plot has no name, and the development build warns.
 
 When a key comes to rest, a polite live region beside the plot reads the active position and every series' value there, as the tooltip shows it; a pointer announces nothing. A reader who wants every value at once opens the `DataTable` (on [Tooltip](#tooltip)), a plain table of what the chart shows.
 
@@ -2173,15 +2167,16 @@ Under forced colours the chart draws in the system colours and tells its series
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
+| `ref` | `Ref<HTMLDivElement>` | — | The root element, the `<div>` that `className`, `style`, `id` and the `data-*` attributes reach. |
 | `width` | `number \| "100%"` | `"100%"` | Width in CSS pixels, or `"100%"` for the host's: the chart measures its host and follows it through a ResizeObserver.<br>Shown in: [Size a chart by its container (Installation)](#installation) |
-| `height` | `number` | fills the frame, at least 300 px | Height in CSS pixels, fixed. Left out, the chart fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 300 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)).<br>Shown in: [Mix series kinds](#chart-1), [Say there is nothing to show](#chart-1), [Read it by keyboard and screen reader](#chart-1) and 74 more |
+| `height` | `number` | fills the frame, at least 300 px | Height in CSS pixels, fixed. Left out, the chart fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 300 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)).<br>Shown in: [Mix series kinds](#chart-1), [Say there is nothing to show](#chart-1), [Read it by keyboard and screen reader](#chart-1) and 75 more |
 | `padding` | `number \| Partial<``Padding``>` | — | Outer spacing of the plot area in CSS pixels.<br>Shown in: [Fix the domain and name the ticks (Axis)](#axis) |
 | `empty` | `ReactNode` | the wording's `empty` | Shown in the middle of the plot area when no visible series has a point to show - no data, only gaps, or every series hidden. Axes and frame stay. Not while `loading`.<br>Shown in: [Say there is nothing to show](#chart-1) |
 | `loading` | `boolean` | `false` | The rows are on their way, as the table's `loading` says ([ADR-0042](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0042-a-rows-height-never-follows-what-it-shows.md)). A course already drawn stays: it dims after a moment and takes no pointer until the answer is in. Where there is nothing to show, the empty message waits. The plot is `aria-busy` meanwhile.<br>Shown in: [Show that rows are on their way](#chart-1) |
 | `wording` | `Partial<``ChartsWording``>` | `DEFAULT_CHARTS_WORDING` | The chart's words ([ADR-0031](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0031-the-charts-carry-their-own-wording.md)); entries left out fall back to English. Its `locale` also formats every number and every date or time label the chart makes itself (`en-GB`, `de-DE`; the browser's language is not read) - a `tickFormat` or `format` of your own stays in charge of its axis or series. German: `GERMAN_CHARTS_WORDING` from `@umriss-ui/charts/wording/de`.<br>Shown in: [Read it by keyboard and screen reader](#chart-1) |
 | `encoding` | `"color" \| "marks"` | `"color"` | How series are told apart. `"color"`: by their colour. `"marks"`: by a dash and a marker shape as well - a line, an area and a scatter -, and by a hatch - a bar, a state, a matrix cell, a limit band -, chosen by the same palette place as the colour, so that a reader who does not see the colours still tells them apart; the legend's chips show the same. A caller's own `dash` wins over the place's.<br>Shown in: [Tell series apart without colour](#chart-1), [Mark every kind](#chart-1), [Mark bands, limits and cells](#chart-1) |
 | `syncId` | `string` | — | Charts with the same id share the pointer's x position, in domain units: each draws its crosshair there, the tooltip stays with the chart under the pointer. Zoom is not shared this way: charts zoom together by sending each other their view (`useChart`'s `onViewChange` and `setView`).<br>Shown in: [Keep charts in step (Zoom and pan)](#zoom-and-pan), [Watch latency against its objective (Scenarios)](#watch-latency-against-its-objective), [Hold the tile length in control (Scenarios)](#hold-the-tile-length-in-control) |
-| `children` | `ReactNode` | — | The axes, series and companions of this chart. They draw nothing themselves: each registers its configuration and the scene draws it, and the order in the JSX is the drawing order.<br>Shown in: [Mix series kinds](#chart-1), [Say there is nothing to show](#chart-1), [Read it by keyboard and screen reader](#chart-1) and 74 more |
+| `children` | `ReactNode` | — | The axes, series and companions of this chart. They draw nothing themselves: each registers its configuration and the scene draws it, and the order in the JSX is the drawing order.<br>Shown in: [Mix series kinds](#chart-1), [Say there is nothing to show](#chart-1), [Read it by keyboard and screen reader](#chart-1) and 75 more |
 
 ###### Events
 
@@ -2193,7 +2188,7 @@ Under forced colours the chart draws in the system colours and tells its series
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `ariaLabel` | `string` | — | Required in DEV through a warning.<br>Shown in: [Mix series kinds](#chart-1), [Say there is nothing to show](#chart-1), [Read it by keyboard and screen reader](#chart-1) and 74 more |
+| `ariaLabel` | `string` | — | *Deprecated* since 0.43 - use `aria-label`. Accessible name of the plot. Without a name, `aria-label` or `aria-labelledby`, the chart warns in development. |
 
 ###### Styling
 
@@ -2202,6 +2197,8 @@ Under forced colours the chart draws in the system colours and tells its series
 | `className` | `string` | — | Goes to the root element, as it does everywhere in this workspace. |
 | `style` | `CSSProperties` | — | Goes to the root element, after the chart's own styles: a `height` or `minHeight` set here wins. The plot area is observed in both directions and the scene follows it. |
 
+Also takes every attribute of `<div>` – without `children`.
+
 ##### Types on this page
 
 ###### `Padding`
@@ -2267,9 +2264,9 @@ Measurements of the instrumentation for the benchmark page.
 #### Known limits
 
 - No error state of its own: where the rows could not be loaded, show an `Alert` from @umriss-ui/core. Waiting for them is `loading`.
-- No pie, donut, radar or candlestick, no smoothing, animation or export, no WebGL ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md)).
+- No pie, donut, radar or candlestick, no smoothing, animation or export, no WebGL ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Axis
 
@@ -2334,7 +2331,7 @@ function WeekTooltip({ hit }: { hit: TooltipHit<Week> }) {
 export default function Configuration() {
   const { Chart, XAxis, YAxis, Line } = useChart(BOOKED);
   return (
-    <Chart height={280} padding={{ top: 12, right: 16, bottom: 8, left: 8 }} ariaLabel="Share of capacity booked per team and week">
+    <Chart height={280} padding={{ top: 12, right: 16, bottom: 8, left: 8 }} aria-label="Share of capacity booked per team and week">
       <XAxis value="week" label="Week" tickCount={6} />
       <YAxis domain={[0, 100]} tickFormat={percent} label="Booked" />
       <Line value="web" name="Web" markers="always" strokeWidth={2} />
@@ -2393,7 +2390,7 @@ const LOAD_TEST: readonly LoadTestPoint[] = (() => {
 export default function Axes() {
   const { Chart, XAxis, YAxis, Line } = useChart(LOAD_TEST);
   return (
-    <Chart height={340} ariaLabel="A load test: CPU, throughput and latency on three y axes">
+    <Chart height={340} aria-label="A load test: CPU, throughput and latency on three y axes">
       <XAxis value="minute" label="Minute of the test" />
       <XAxis id="seconds" position="top" value={(d) => d.minute * 60} label="Seconds into the test" />
       <YAxis id="cpu" position="left" label="CPU %" />
@@ -2461,7 +2458,7 @@ const weekdayAndTime = (v: number) =>
 export default function WorkingTime() {
   const { Chart, XAxis, YAxis, Line } = useChart(SORTED);
   return (
-    <Chart height={280} ariaLabel="Parcels sorted per hour across last week's sorting hours">
+    <Chart height={280} aria-label="Parcels sorted per hour across last week's sorting hours">
       <XAxis
         value="t"
         calendar={SORTING_HOURS}
@@ -2572,7 +2569,7 @@ const CHECKOUT = metrics("checkout");
 export default function TimeAxis() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={260} ariaLabel="Checkout's error rate today">
+    <Chart height={260} aria-label="Checkout's error rate today">
       <XAxis value="t" />
       <YAxis label="Errors %" />
       <Line value="errorRate" name="Error rate" />
@@ -2690,7 +2687,7 @@ const SEARCH_WEEK = week("search", 5 * 60_000);
 export default function AlignedTicks() {
   const { Chart, XAxis, YAxis, Line } = useChart(SEARCH_WEEK);
   return (
-    <Chart height={260} ariaLabel="Search requests and latency over last week on one grid">
+    <Chart height={260} aria-label="Search requests and latency over last week on one grid">
       <XAxis value="t" time />
       <YAxis label="Requests/min" />
       <YAxis id="latency" position="right" label="ms" alignTicks />
@@ -2873,7 +2870,7 @@ const HOURS = hourly(SHIFT);
 export default function EveryKind() {
   const { Chart, XAxis, YAxis, Line, Area, Bar, Scatter } = useChart(SHIFT.readings);
   return (
-    <Chart height={340} ariaLabel="The kiln's temperature by the minute above the tiles it fired by the hour">
+    <Chart height={340} aria-label="The kiln's temperature by the minute above the tiles it fired by the hour">
       <XAxis value="minute" domain={[0, SHIFT_MINUTES]} label="Minute of the shift" />
       {/* This axis reads the hourly rows its series bring, so it names their type. */}
       <XAxis<HourCount>
@@ -2921,7 +2918,7 @@ const NAMES: Record<string, string> = { mon: "Monday", tue: "Tuesday", wed: "Wed
 export default function Categories() {
   const { Chart, XAxis, YAxis, Bar } = useChart(LATE);
   return (
-    <Chart height={260} ariaLabel="Minutes late per working day">
+    <Chart height={260} aria-label="Minutes late per working day">
       <XAxis value="day" categories={WEEK} categoryLabel={(day) => NAMES[day] ?? day} />
       <YAxis label="Minutes late" />
       <Bar value="minutes" name="Late" />
@@ -2941,7 +2938,7 @@ The keys of [Chart](#chart-1) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `value` *required* | `AxisField``<T> \| ((d: T, index: number) => ``AxisValue``)` | — | Where a row lies on this axis: a field of the row, compared by its name, or a function of it, compared by its source text as a series' is (`ValueFunction`) - with the same closure limit. A number is a position, a `Date` an instant, a string a category: every distinct one gets a place of its own, in the order the rows bring them, a tick and its name as the label ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)). The type decides, never the content - `"2024"` is a category, `2024` a number - and a row without a value has no place. The axis reads the rows of every series bound to it; where those bring their own `data`, name their row: `<XAxis<HourCount> value="hour" />`.<br>Shown in: [Fix the domain and name the ticks](#axis), [Add axes for other magnitudes](#axis), [Leave out the hours nobody works](#axis) and 74 more |
+| `value` *required* | `AxisField``<T> \| ((d: T, index: number) => ``AxisValue``)` | — | Where a row lies on this axis: a field of the row, compared by its name, or a function of it, compared by its source text as a series' is (`ValueFunction`) - with the same closure limit. A number is a position, a `Date` an instant, a string a category: every distinct one gets a place of its own, in the order the rows bring them, a tick and its name as the label ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)). The type decides, never the content - `"2024"` is a category, `2024` a number - and a row without a value has no place. The axis reads the rows of every series bound to it; where those bring their own `data`, name their row: `<XAxis<HourCount> value="hour" />`.<br>Shown in: [Fix the domain and name the ticks](#axis), [Add axes for other magnitudes](#axis), [Leave out the hours nobody works](#axis) and 75 more |
 | `domain` | `"nice" \| "data" \| readonly [number, number] \| readonly [Date, Date]` | `"nice"` | `"nice"` widens the data's extent to ticks - to named `ticks` where there are any, on a time axis to whole units of a step of hours or longer -, `"data"` keeps it, a pair is fixed: numbers, on a time axis milliseconds or two `Date`s, on a category axis places. On a `zoomable` axis it is the start: what the axis shows while the chart's view names no span for it.<br>Shown in: [Bind every kind of series to a second axis](#axis), [Read it by keyboard and screen reader (Chart)](#chart-1), [Gestures and keys (Zoom and pan)](#zoom-and-pan) and 11 more |
 | `position` | `"bottom" \| "top"` | `"bottom"` | Which edge the axis stands at. A second x axis on the opposite edge is how a series counts in a unit of its own.<br>Shown in: [Add axes for other magnitudes](#axis), [Bind every kind of series to a second axis](#axis) |
 | `time` | `boolean` | — | The values are instants: milliseconds since the epoch, or with `time` said ISO 8601 strings as an API sends them, read by the platform's rule - a date with a time and no offset is local time, a date alone is UTC; a string that is none is not drawn. Rows that hold a `Date` put the axis in time without `time`. Ticks on local boundaries from the minute to the month, labels by level in en-GB with a 24-hour clock - `15:00`, `17 Mar`, `Mar 2026` - and the date on the first tick and on the first of a new day (`17 Mar 00:00`); a day tick there carries the year. The tooltip's x value carries the seconds where the readings lie less than a minute apart. Another language is a `tickFormat`, which is handed the instant in milliseconds. `calendar` implies it.<br>Shown in: [Align a second axis to the grid](#axis), [Draw a first chart (Installation)](#installation), [Size a chart by its container (Installation)](#installation) and 36 more |
@@ -2949,9 +2946,9 @@ The keys of [Chart](#chart-1) apply here.
 | `zoomable` | `boolean` | `false` | Zoom and pan: Ctrl or ⌘ with the wheel - and a pinch - zoom around the pointer, a drag, a horizontal wheel or Shift with the wheel pan, a double click goes back to `domain`; with the focus on the chart, + and − zoom, Shift with ← or → pans and 0 goes back. The span shown is part of the chart's view, by this axis' `id` (`useChart`'s `initialView`, `onViewChange`, `setView`, `setDomain`). The plain wheel always scrolls the page.<br>Shown in: [Read it by keyboard and screen reader (Chart)](#chart-1), [Gestures and keys (Zoom and pan)](#zoom-and-pan), [Limit the zoom (Zoom and pan)](#zoom-and-pan) and 6 more |
 | `zoomLimits` | `ZoomLimits` | at most the data's extent or this axis' own `domain`, whichever is wider, at least three data steps | The narrowest and the widest span zoom may reach, in the axis' units - milliseconds on a time axis.<br>Shown in: [Limit the zoom (Zoom and pan)](#zoom-and-pan) |
 | `id` | `string` | `"x"` | Axis id, through which series bind themselves.<br>Shown in: [Add axes for other magnitudes](#axis), [Align a second axis to the grid](#axis), [Bind every kind of series to a second axis](#axis) and 7 more |
-| `label` | `string` | — | Axis title.<br>Shown in: [Fix the domain and name the ticks](#axis), [Add axes for other magnitudes](#axis), [Leave out the hours nobody works](#axis) and 66 more |
+| `label` | `string` | — | Axis title.<br>Shown in: [Fix the domain and name the ticks](#axis), [Add axes for other magnitudes](#axis), [Leave out the hours nobody works](#axis) and 67 more |
 | `tickCount` | `number` | — | Target value; the 1-2-5 algorithm may deviate.<br>Shown in: [Fix the domain and name the ticks](#axis), [Leave out the hours nobody works](#axis), [Mix series kinds (Chart)](#chart-1) and 8 more |
-| `tickFormat` | `(v: number) => string` | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity.<br>Shown in: [Fix the domain and name the ticks](#axis), [Leave out the hours nobody works](#axis), [Bind every kind of series to a second axis](#axis) and 21 more |
+| `tickFormat` | `ValueFormat` | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity. Or `NumberOptions`: Intl's options in the wording's locale, compared by value; the step's places stay unless the options set digits.<br>Shown in: [Fix the domain and name the ticks](#axis), [Leave out the hours nobody works](#axis), [Bind every kind of series to a second axis](#axis) and 21 more |
 | `grid` | `boolean` | only on the first axis of its orientation | Grid lines.<br>Shown in: [One vehicle through the day (StateBand)](#stateband), [Give each one a lane (StateBand)](#stateband), [See where the vans stand idle (Scenarios)](#see-where-the-vans-stand-idle) |
 | `ticks` | `readonly number[]` | — | Fixed tick values instead of the 1-2-5 algorithm, on a numeric axis: an hour axis' named hours, a lane grid. An axis that reads categories needs none - every category has its tick.<br>Shown in: [Bind every kind of series to a second axis](#axis), [Mark bands, limits and cells (Chart)](#chart-1), [Compare progress with a plan (Line)](#line) and 7 more |
 | `categories` | `readonly string[]` | — | The categories of the axis, in their order. Without it they stand in the order the rows first bring them. With it the list is the order and the extent: a category no row carries keeps its empty place, and a row whose category is not listed is not drawn - DEV names it. It makes the axis a category axis whatever the rows hold ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)).<br>Shown in: [Fix the order and keep an empty place](#axis) |
@@ -2965,9 +2962,9 @@ The keys of [Chart](#chart-1) apply here.
 | `alignTicks` | `boolean` | — | On a further y axis: take the first y axis' tick count and widen this axis' domain until its ticks fall on that one's grid lines, the steps still 1-2-5 - one grid serves both. `tickCount` then does not apply; on the first y axis it changes nothing.<br>Shown in: [Align a second axis to the grid](#axis) |
 | `position` | `"left" \| "right"` | `"left"` | Which edge the axis stands at. Several y axes per side are stacked outwards, so that extents of clearly different magnitude stay readable.<br>Shown in: [Add axes for other magnitudes](#axis), [Align a second axis to the grid](#axis), [Bind every kind of series to a second axis](#axis) and 7 more |
 | `id` | `string` | `"y"` | Axis id, through which series bind themselves.<br>Shown in: [Add axes for other magnitudes](#axis), [Align a second axis to the grid](#axis), [Bind every kind of series to a second axis](#axis) and 7 more |
-| `label` | `string` | — | Axis title.<br>Shown in: [Fix the domain and name the ticks](#axis), [Add axes for other magnitudes](#axis), [Leave out the hours nobody works](#axis) and 66 more |
+| `label` | `string` | — | Axis title.<br>Shown in: [Fix the domain and name the ticks](#axis), [Add axes for other magnitudes](#axis), [Leave out the hours nobody works](#axis) and 67 more |
 | `tickCount` | `number` | — | Target value; the 1-2-5 algorithm may deviate.<br>Shown in: [Fix the domain and name the ticks](#axis), [Leave out the hours nobody works](#axis), [Mix series kinds (Chart)](#chart-1) and 8 more |
-| `tickFormat` | `(v: number) => string` | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity.<br>Shown in: [Fix the domain and name the ticks](#axis), [Leave out the hours nobody works](#axis), [Bind every kind of series to a second axis](#axis) and 21 more |
+| `tickFormat` | `ValueFormat` | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity. Or `NumberOptions`: Intl's options in the wording's locale, compared by value; the step's places stay unless the options set digits.<br>Shown in: [Fix the domain and name the ticks](#axis), [Leave out the hours nobody works](#axis), [Bind every kind of series to a second axis](#axis) and 21 more |
 | `grid` | `boolean` | only on the first axis of its orientation | Grid lines.<br>Shown in: [One vehicle through the day (StateBand)](#stateband), [Give each one a lane (StateBand)](#stateband), [See where the vans stand idle (Scenarios)](#see-where-the-vans-stand-idle) |
 | `ticks` | `readonly number[]` | — | Fixed tick values instead of the 1-2-5 algorithm, on a numeric axis: an hour axis' named hours, a lane grid. An axis that reads categories needs none - every category has its tick.<br>Shown in: [Bind every kind of series to a second axis](#axis), [Mark bands, limits and cells (Chart)](#chart-1), [Compare progress with a plan (Line)](#line) and 7 more |
 | `categories` | `readonly string[]` | — | The categories of the axis, in their order. Without it they stand in the order the rows first bring them. With it the list is the order and the extent: a category no row carries keeps its empty place, and a row whose category is not listed is not drawn - DEV names it. It makes the axis a category axis whatever the rows hold ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)).<br>Shown in: [Fix the order and keep an empty place](#axis) |
@@ -3022,12 +3019,32 @@ schedule's shape.
 | `min` *required* | `number` | — | <br>Shown in: [Limit the zoom (Zoom and pan)](#zoom-and-pan) |
 | `max` *required* | `number` | — | <br>Shown in: [Limit the zoom (Zoom and pan)](#zoom-and-pan) |
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 #### Known limits
 
-- No logarithmic and no band scale: compute the logarithm in `value`; a category is a place on the linear scale ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md), [ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)).
+- No logarithmic and no band scale: compute the logarithm in `value`; a category is a place on the linear scale ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md), [ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)).
 - umriss shows the reader's time ([ADR-0060](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0060-validation-and-a-layout-editor-are-never-time-zones-not-yet.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Zoom and pan
 
@@ -3155,7 +3172,7 @@ const SEARCH_WEEK = week("search", 60_000);
 export default function GesturesAndKeys() {
   const { Chart, XAxis, YAxis, Line } = useChart(SEARCH_WEEK);
   return (
-    <Chart height={260} ariaLabel="Search latency over last week, a reading a minute, zoomable">
+    <Chart height={260} aria-label="Search latency over last week, a reading a minute, zoomable">
       {/* The span shown is the chart's own: `domain` is where it starts. */}
       <XAxis value="t" time domain="data" zoomable />
       <YAxis label="ms" />
@@ -3274,7 +3291,7 @@ const SEARCH_WEEK = week("search", 60_000);
 export default function ZoomLimits() {
   const { Chart, XAxis, YAxis, Line } = useChart(SEARCH_WEEK);
   return (
-    <Chart height={260} ariaLabel="Search latency over last week, zoomable between an hour and two days">
+    <Chart height={260} aria-label="Search latency over last week, zoomable between an hour and two days">
       {/* Never closer than an hour, never wider than two days - the week
           shows at the start and once more after a double click. */}
       <XAxis value="t" time domain="data" zoomable zoomLimits={{ min: HOUR, max: 2 * DAY }} />
@@ -3398,7 +3415,7 @@ export default function VisibleDomain() {
     initialView: { domains: { x: [SATURDAY + 16 * HOUR, SATURDAY + 22 * HOUR] } },
   });
   return (
-    <Chart height={260} ariaLabel="Search latency on Saturday evening, the y axis fitted to it">
+    <Chart height={260} aria-label="Search latency on Saturday evening, the y axis fitted to it">
       <XAxis value="t" time domain="data" zoomable />
       <YAxis label="ms" domain="visible" />
       <Line value="p95" name="p95" />
@@ -3545,7 +3562,7 @@ function Channel({ channel: c, peers }: { channel: (typeof CHANNELS)[number]; pe
     return () => void peers.delete(c.name);
   }, [peers, c.name, setView]);
   return (
-    <Chart height={140} syncId="images" ariaLabel={`Image service ${c.name} over last week`}>
+    <Chart height={140} syncId="images" aria-label={`Image service ${c.name} over last week`}>
       <XAxis value="t" time domain="data" zoomable />
       <YAxis label={c.unit} domain="visible" tickCount={4} />
       <Line value={c.value} name={c.name} />
@@ -3565,7 +3582,7 @@ The keys of [Chart](#chart-1) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `value` *required* | `AxisField``<T> \| ((d: T, index: number) => ``AxisValue``)` | — | Where a row lies on this axis: a field of the row, compared by its name, or a function of it, compared by its source text as a series' is (`ValueFunction`) - with the same closure limit. A number is a position, a `Date` an instant, a string a category: every distinct one gets a place of its own, in the order the rows bring them, a tick and its name as the label ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)). The type decides, never the content - `"2024"` is a category, `2024` a number - and a row without a value has no place. The axis reads the rows of every series bound to it; where those bring their own `data`, name their row: `<XAxis<HourCount> value="hour" />`.<br>Shown in: [Gestures and keys](#zoom-and-pan), [Limit the zoom](#zoom-and-pan), [Fit the y axis to what is visible](#zoom-and-pan) and 74 more |
+| `value` *required* | `AxisField``<T> \| ((d: T, index: number) => ``AxisValue``)` | — | Where a row lies on this axis: a field of the row, compared by its name, or a function of it, compared by its source text as a series' is (`ValueFunction`) - with the same closure limit. A number is a position, a `Date` an instant, a string a category: every distinct one gets a place of its own, in the order the rows bring them, a tick and its name as the label ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)). The type decides, never the content - `"2024"` is a category, `2024` a number - and a row without a value has no place. The axis reads the rows of every series bound to it; where those bring their own `data`, name their row: `<XAxis<HourCount> value="hour" />`.<br>Shown in: [Gestures and keys](#zoom-and-pan), [Limit the zoom](#zoom-and-pan), [Fit the y axis to what is visible](#zoom-and-pan) and 75 more |
 | `domain` | `"nice" \| "data" \| readonly [number, number] \| readonly [Date, Date]` | `"nice"` | `"nice"` widens the data's extent to ticks - to named `ticks` where there are any, on a time axis to whole units of a step of hours or longer -, `"data"` keeps it, a pair is fixed: numbers, on a time axis milliseconds or two `Date`s, on a category axis places. On a `zoomable` axis it is the start: what the axis shows while the chart's view names no span for it.<br>Shown in: [Gestures and keys](#zoom-and-pan), [Limit the zoom](#zoom-and-pan), [Fit the y axis to what is visible](#zoom-and-pan) and 11 more |
 | `position` | `"bottom" \| "top"` | `"bottom"` | Which edge the axis stands at. A second x axis on the opposite edge is how a series counts in a unit of its own.<br>Shown in: [Add axes for other magnitudes (Axis)](#axis), [Bind every kind of series to a second axis (Axis)](#axis) |
 | `time` | `boolean` | — | The values are instants: milliseconds since the epoch, or with `time` said ISO 8601 strings as an API sends them, read by the platform's rule - a date with a time and no offset is local time, a date alone is UTC; a string that is none is not drawn. Rows that hold a `Date` put the axis in time without `time`. Ticks on local boundaries from the minute to the month, labels by level in en-GB with a 24-hour clock - `15:00`, `17 Mar`, `Mar 2026` - and the date on the first tick and on the first of a new day (`17 Mar 00:00`); a day tick there carries the year. The tooltip's x value carries the seconds where the readings lie less than a minute apart. Another language is a `tickFormat`, which is handed the instant in milliseconds. `calendar` implies it.<br>Shown in: [Gestures and keys](#zoom-and-pan), [Limit the zoom](#zoom-and-pan), [Fit the y axis to what is visible](#zoom-and-pan) and 36 more |
@@ -3573,9 +3590,9 @@ The keys of [Chart](#chart-1) apply here.
 | `zoomable` | `boolean` | `false` | Zoom and pan: Ctrl or ⌘ with the wheel - and a pinch - zoom around the pointer, a drag, a horizontal wheel or Shift with the wheel pan, a double click goes back to `domain`; with the focus on the chart, + and − zoom, Shift with ← or → pans and 0 goes back. The span shown is part of the chart's view, by this axis' `id` (`useChart`'s `initialView`, `onViewChange`, `setView`, `setDomain`). The plain wheel always scrolls the page.<br>Shown in: [Gestures and keys](#zoom-and-pan), [Limit the zoom](#zoom-and-pan), [Fit the y axis to what is visible](#zoom-and-pan) and 6 more |
 | `zoomLimits` | `ZoomLimits` | at most the data's extent or this axis' own `domain`, whichever is wider, at least three data steps | The narrowest and the widest span zoom may reach, in the axis' units - milliseconds on a time axis.<br>Shown in: [Limit the zoom](#zoom-and-pan) |
 | `id` | `string` | `"x"` | Axis id, through which series bind themselves.<br>Shown in: [Add axes for other magnitudes (Axis)](#axis), [Align a second axis to the grid (Axis)](#axis), [Bind every kind of series to a second axis (Axis)](#axis) and 7 more |
-| `label` | `string` | — | Axis title.<br>Shown in: [Gestures and keys](#zoom-and-pan), [Limit the zoom](#zoom-and-pan), [Fit the y axis to what is visible](#zoom-and-pan) and 66 more |
+| `label` | `string` | — | Axis title.<br>Shown in: [Gestures and keys](#zoom-and-pan), [Limit the zoom](#zoom-and-pan), [Fit the y axis to what is visible](#zoom-and-pan) and 67 more |
 | `tickCount` | `number` | — | Target value; the 1-2-5 algorithm may deviate.<br>Shown in: [Keep charts in step](#zoom-and-pan), [Fix the domain and name the ticks (Axis)](#axis), [Leave out the hours nobody works (Axis)](#axis) and 8 more |
-| `tickFormat` | `(v: number) => string` | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity.<br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Leave out the hours nobody works (Axis)](#axis), [Bind every kind of series to a second axis (Axis)](#axis) and 21 more |
+| `tickFormat` | `ValueFormat` | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity. Or `NumberOptions`: Intl's options in the wording's locale, compared by value; the step's places stay unless the options set digits.<br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Leave out the hours nobody works (Axis)](#axis), [Bind every kind of series to a second axis (Axis)](#axis) and 21 more |
 | `grid` | `boolean` | only on the first axis of its orientation | Grid lines.<br>Shown in: [One vehicle through the day (StateBand)](#stateband), [Give each one a lane (StateBand)](#stateband), [See where the vans stand idle (Scenarios)](#see-where-the-vans-stand-idle) |
 | `ticks` | `readonly number[]` | — | Fixed tick values instead of the 1-2-5 algorithm, on a numeric axis: an hour axis' named hours, a lane grid. An axis that reads categories needs none - every category has its tick.<br>Shown in: [Bind every kind of series to a second axis (Axis)](#axis), [Mark bands, limits and cells (Chart)](#chart-1), [Compare progress with a plan (Line)](#line) and 7 more |
 | `categories` | `readonly string[]` | — | The categories of the axis, in their order. Without it they stand in the order the rows first bring them. With it the list is the order and the extent: a category no row carries keeps its empty place, and a row whose category is not listed is not drawn - DEV names it. It makes the axis a category axis whatever the rows hold ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)).<br>Shown in: [Fix the order and keep an empty place (Axis)](#axis) |
@@ -3592,7 +3609,7 @@ The keys of [Chart](#chart-1) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `onViewChange` | `(view: `[`ChartView`](#view)`) => void` | — | Every change the reader makes, once, always the whole view - the one to keep, or to hand another chart's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the chart starts with, nor for one `setView` applies.<br>Shown in: [Keep charts in step](#zoom-and-pan), [Read it by keyboard and screen reader (Chart)](#chart-1) |
-| `onSelect` | `(hit: ``TooltipHit``<Z>) => void` | — | The reader chose a point: a click on a hit (a tap too), or Enter on the Active point - the same hit the tooltip's `render` receives. Once per click; the end of a drag does not report, and the second click of a double click does not either. The chart holds no selection and draws none: what is chosen is the application's state. Needs a `<Tooltip>`, which makes the hits; the hit does not travel over `syncId`.<br>Shown in: [Choose a hit (Tooltip)](#tooltip) |
+| `onSelect` | `(hit: ``TooltipHit``<Z>) => void` | — | The reader chose a point: a click on a hit (a tap too), or Enter on the Active point - the same hit the tooltip's `render` receives. Once per click; the end of a drag does not report, and the second click of a double click does not either. The chart holds no selection and draws none: what is chosen is the application's state. Needs a `<Tooltip>`, which makes the hits; the hit does not travel over `syncId`.<br>Shown in: [Choose a hit (Tooltip)](#tooltip), [Drill down from a year to its days (Tooltip)](#tooltip) |
 
 ##### Types on this page
 
@@ -3643,6 +3660,15 @@ schedule's shape.
 | `min` *required* | `number` | — | <br>Shown in: [Limit the zoom](#zoom-and-pan) |
 | `max` *required* | `number` | — | <br>Shown in: [Limit the zoom](#zoom-and-pan) |
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
 ###### `TooltipHit<T = unknown>`
 
 What the pointer hit: the x value under it and one point per series there.
@@ -3651,10 +3677,21 @@ A custom tooltip's `render` receives it.
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `xValue` *required* | `number` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) |
-| `points` *required* | `readonly ``TooltipPoint``<T>[]` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) |
+| `points` *required* | `readonly ``TooltipPoint``<T>[]` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) and 1 more |
 | `xPx` *required* | `number` | — | Pixel position of the crosshair (snapped to the data point). |
 | `yPx` *required* | `number` | — | Pixel position of the primary hit. |
 
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 ###### `TooltipPoint<T = unknown>`
 
 One hit per series in the tooltip.
@@ -3665,7 +3702,7 @@ One hit per series in the tooltip.
 | `color` *required* | `string` | — |  |
 | `xValue` *required* | `number` | — | The point's x value on its own x axis - with several x axes it can differ from the hit's. |
 | `yValue` *required* | `number` | — | The point's y value; in a stack its own value, not its top - in a normalised stack its share in percent.<br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Choose a hit (Tooltip)](#tooltip) |
-| `datum` *required* | `T` | — | <br>Shown in: [Write the tooltip yourself (Tooltip)](#tooltip) |
+| `datum` *required* | `T` | — | <br>Shown in: [Write the tooltip yourself (Tooltip)](#tooltip), [Drill down from a year to its days (Tooltip)](#tooltip) |
 | `index` *required* | `number` | — |  |
 | `level` | `number` | — | Only for the matrix: its level, out of the level channel. It stands here and not in yValue, because yValue is the position on the y axis - for a matrix therefore the row. Putting both into one field would be exactly the overloading [ADR-0011](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0011-named-channels-never-overloaded.md) is written against. |
 | `segment` | `{ from: number; to: number; label: string }` | — | Only for state series: the section being pointed at. A duration does not stand here - it is the difference of two numbers the entry already carries, and formatting it would presuppose knowing what the x axis means. The caller knows that, not this library. |
@@ -3697,7 +3734,7 @@ The optional numbers of a box by name.
 
 - No zoom along y, no rectangle zoom and no navigator: the x span is the one zoom there is.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### View
 
@@ -3836,7 +3873,7 @@ export default function KeepAndRestore() {
   const { Chart, XAxis, YAxis, Line, view, setView } = useChart(SERIES[0]!.data);
   return (
     <>
-      <Chart height={260} ariaLabel="Latency of three services today">
+      <Chart height={260} aria-label="Latency of three services today">
         <XAxis value="t" time zoomable />
         <YAxis label="ms" domain="visible" />
         {SERIES.map((one) => (
@@ -3893,7 +3930,7 @@ The keys of [Chart](#chart-1) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `onViewChange` | `(view: ``ChartView``) => void` | — | Every change the reader makes, once, always the whole view - the one to keep, or to hand another chart's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the chart starts with, nor for one `setView` applies.<br>Shown in: [Keep charts in step (Zoom and pan)](#zoom-and-pan), [Read it by keyboard and screen reader (Chart)](#chart-1) |
-| `onSelect` | `(hit: ``TooltipHit``<Z>) => void` | — | The reader chose a point: a click on a hit (a tap too), or Enter on the Active point - the same hit the tooltip's `render` receives. Once per click; the end of a drag does not report, and the second click of a double click does not either. The chart holds no selection and draws none: what is chosen is the application's state. Needs a `<Tooltip>`, which makes the hits; the hit does not travel over `syncId`.<br>Shown in: [Choose a hit (Tooltip)](#tooltip) |
+| `onSelect` | `(hit: ``TooltipHit``<Z>) => void` | — | The reader chose a point: a click on a hit (a tap too), or Enter on the Active point - the same hit the tooltip's `render` receives. Once per click; the end of a drag does not report, and the second click of a double click does not either. The chart holds no selection and draws none: what is chosen is the application's state. Needs a `<Tooltip>`, which makes the hits; the hit does not travel over `syncId`.<br>Shown in: [Choose a hit (Tooltip)](#tooltip), [Drill down from a year to its days (Tooltip)](#tooltip) |
 
 ##### `ChartView`
 
@@ -3912,7 +3949,7 @@ A custom tooltip's `render` receives it.
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `xValue` *required* | `number` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) |
-| `points` *required* | `readonly ``TooltipPoint``<T>[]` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) |
+| `points` *required* | `readonly ``TooltipPoint``<T>[]` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) and 1 more |
 | `xPx` *required* | `number` | — | Pixel position of the crosshair (snapped to the data point). |
 | `yPx` *required* | `number` | — | Pixel position of the primary hit. |
 
@@ -3934,7 +3971,7 @@ One hit per series in the tooltip.
 | `color` *required* | `string` | — |  |
 | `xValue` *required* | `number` | — | The point's x value on its own x axis - with several x axes it can differ from the hit's. |
 | `yValue` *required* | `number` | — | The point's y value; in a stack its own value, not its top - in a normalised stack its share in percent.<br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Choose a hit (Tooltip)](#tooltip) |
-| `datum` *required* | `T` | — | <br>Shown in: [Write the tooltip yourself (Tooltip)](#tooltip) |
+| `datum` *required* | `T` | — | <br>Shown in: [Write the tooltip yourself (Tooltip)](#tooltip), [Drill down from a year to its days (Tooltip)](#tooltip) |
 | `index` *required* | `number` | — |  |
 | `level` | `number` | — | Only for the matrix: its level, out of the level channel. It stands here and not in yValue, because yValue is the position on the y axis - for a matrix therefore the row. Putting both into one field would be exactly the overloading [ADR-0011](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0011-named-channels-never-overloaded.md) is written against. |
 | `segment` | `{ from: number; to: number; label: string }` | — | Only for state series: the section being pointed at. A duration does not stand here - it is the difference of two numbers the entry already carries, and formatting it would presuppose knowing what the x axis means. The caller knows that, not this library. |
@@ -3966,7 +4003,7 @@ The optional numbers of a box by name.
 
 - The active point and the open data table are not part of the view: they are where the reader is, not how the chart is looked at.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Series
 
@@ -4077,7 +4114,7 @@ const CHECKOUT = metrics("checkout");
 export default function OneSeries() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={280} ariaLabel="Checkout's 95th percentile latency today">
+    <Chart height={280} aria-label="Checkout's 95th percentile latency today">
       <XAxis value="t" time />
       <YAxis label="ms" />
       <Line value="p95" name="Checkout p95" />
@@ -4190,7 +4227,7 @@ const IMAGES = metrics("images").map((d) => {
 export default function MultiSeries() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={300} ariaLabel="95th percentile latency of four services today">
+    <Chart height={300} aria-label="95th percentile latency of four services today">
       <XAxis value="t" time />
       <YAxis label="ms" />
       <Line value="p95" name="Checkout" />
@@ -4317,7 +4354,7 @@ const CHECKOUT = metrics("checkout");
 export default function StepLine() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={260} ariaLabel="Checkout's requests and the instances serving them today">
+    <Chart height={260} aria-label="Checkout's requests and the instances serving them today">
       <XAxis value="t" time />
       <YAxis label="Requests/min" />
       <YAxis id="instances" position="right" domain={[0, 15]} label="Instances" />
@@ -4405,7 +4442,7 @@ const day = (v: number) => new Date(v).toLocaleDateString("en-GB", { weekday: "s
 export default function BurnDown() {
   const { Chart, XAxis, YAxis, Line } = useChart(BURNDOWN);
   return (
-    <Chart height={260} ariaLabel="Sprint 14: hours left against the ideal">
+    <Chart height={260} aria-label="Sprint 14: hours left against the ideal">
       <XAxis value="t" ticks={BURNDOWN.map((d) => d.t)} tickFormat={day} />
       <YAxis label="Hours left" />
       <Line value="ideal" name="Ideal" color="var(--uc-color-text)" dash={[4, 4]} />
@@ -4437,7 +4474,7 @@ The keys of [Chart](#chart-1) apply here.
 | `yAxisId` | `string` | `"y"` | Binding to a y axis.<br>Shown in: [Hold a value until it changes](#line), [Add axes for other magnitudes (Axis)](#axis), [Align a second axis to the grid (Axis)](#axis) and 4 more |
 | `data` | `readonly T[]` | — | Series-own data; overrides the container data.<br>Shown in: [Several series and a gap](#line), [Hold a value until it changes](#line), [Tell series apart without colour (Chart)](#chart-1) and 6 more |
 | `name` | `string` | "Series n", after its place in the chart | The name in legend and tooltip. Without one a warning stands in DEV - an unnamed series is a colour nobody can look up.<br>Shown in: [One series](#line), [Several series and a gap](#line), [Hold a value until it changes](#line) and 47 more |
-| `format` | `(value: number) => string` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it.<br>Shown in: [Write each value in its unit (Tooltip)](#tooltip), [Show the values as a table (Tooltip)](#tooltip), [Table a long series (Tooltip)](#tooltip) and 1 more |
+| `format` | `ValueFormat` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it, as a function or `NumberOptions`.<br>Shown in: [Write each value in its unit (Tooltip)](#tooltip), [Show the values as a table (Tooltip)](#tooltip), [Table a long series (Tooltip)](#tooltip) and 1 more |
 | `color` | `string` | the palette's `--uc-series-N` | Any CSS colour value.<br>Shown in: [Compare progress with a plan](#line), [Fix the domain and name the ticks (Axis)](#axis), [Watch latency against its objective (Scenarios)](#watch-latency-against-its-objective) and 1 more |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value; the theme resolves it.<br>Shown in: [Compare the budget with the forecast (Scenarios)](#compare-the-budget-with-the-forecast) |
 | `strokeWidth` | `number` | `1.5` | Line width in CSS pixels.<br>Shown in: [Hold a value until it changes](#line), [Compare progress with a plan](#line), [Mix series kinds (Chart)](#chart-1) and 9 more |
@@ -4456,6 +4493,15 @@ by its name, or a function, compared by its source text (`ValueFunction`).
 type Value<T> = NumberField<T> | ValueFunction<T>;
 ```
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
 ###### `NumberField<T>`
 
 The fields of a row whose value is a number, or absent.
@@ -4480,11 +4526,22 @@ data reference then. A native or bound function is compared by identity.
 type ValueFunction<T> = (d: T, index: number) => number | null | undefined;
 ```
 
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 #### Known limits
 
-- No smoothing: a curve between two readings would invent values nobody measured ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md)).
+- No smoothing: a curve between two readings would invent values nobody measured ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Area
 
@@ -4593,7 +4650,7 @@ const CHECKOUT = metrics("checkout");
 export default function Filled() {
   const { Chart, XAxis, YAxis, Area } = useChart(CHECKOUT);
   return (
-    <Chart height={260} ariaLabel="Checkout's requests per minute today">
+    <Chart height={260} aria-label="Checkout's requests per minute today">
       <XAxis value="t" time />
       <YAxis label="Requests/min" />
       <Area value="requests" name="Requests" fillOpacity={0.35} strokeWidth={2} />
@@ -4725,7 +4782,7 @@ const EXPECTED = expected("checkout");
 export default function Corridor() {
   const { Chart, XAxis, YAxis, Area, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={280} ariaLabel="Checkout's requests inside the range they are expected in">
+    <Chart height={280} aria-label="Checkout's requests inside the range they are expected in">
       <XAxis value="t" time />
       <YAxis label="Requests/min" />
       {/* The outline runs along the upper edge; dashed, it reads as expected, not measured. */}
@@ -4797,7 +4854,7 @@ export default function StackedAreas() {
   const { Chart, XAxis, YAxis, Area } = useChart(PARCELS_PER_HOUR);
 
   return (
-    <Chart height={280} ariaLabel="Parcels loaded per hour at three depots, stacked">
+    <Chart height={280} aria-label="Parcels loaded per hour at three depots, stacked">
       <XAxis value="t" time domain="data" />
       <YAxis label="Parcels per hour" />
       <Area value="north" name="North" stack="depots" fillOpacity={0.5} strokeWidth={1} />
@@ -4861,7 +4918,7 @@ const tonnes = (v: number) => `${v.toFixed(1)} t`;
 export default function Shares() {
   const { Chart, XAxis, YAxis, Area } = useChart(TONNES_PER_HOUR);
   return (
-    <Chart height={280} ariaLabel="Each depot's share of the freight loaded per hour">
+    <Chart height={280} aria-label="Each depot's share of the freight loaded per hour">
       <XAxis value="t" time domain="data" />
       <YAxis label="Share of the hour" />
       <Area value="north" name="North" stack="depots" normalize format={tonnes} fillOpacity={0.5} strokeWidth={1} />
@@ -4894,7 +4951,7 @@ The keys of [Chart](#chart-1) apply here.
 | `yAxisId` | `string` | `"y"` | Binding to a y axis.<br>Shown in: [Bind every kind of series to a second axis (Axis)](#axis) |
 | `data` | `readonly T[]` | — | Series-own data; overrides the container data.<br>Shown in: [Fill a range between two edges](#area), [Bind every kind of series to a second axis (Axis)](#axis) |
 | `name` | `string` | "Series n", after its place in the chart | The name in legend and tooltip. Without one a warning stands in DEV - an unnamed series is a colour nobody can look up.<br>Shown in: [Fill down to zero](#area), [Fill a range between two edges](#area), [Stack areas](#area) and 5 more |
-| `format` | `(value: number) => string` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it.<br>Shown in: [Show shares of the whole over time](#area) |
+| `format` | `ValueFormat` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it, as a function or `NumberOptions`.<br>Shown in: [Show shares of the whole over time](#area) |
 | `color` | `string` | the palette's `--uc-series-N` | Any CSS colour value. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value; the theme resolves it. `color` beats it. |
 | `stack` | `string` | — | The stack this series stands in: every Bar and Area with the same id on the same x and y axis stands on the ones registered before it. A gap stacks as zero; negative values stack downward from zero. The tooltip names each series' own value and the stack's total.<br>Shown in: [Stack areas](#area), [Show shares of the whole over time](#area) |
@@ -4914,6 +4971,15 @@ by its name, or a function, compared by its source text (`ValueFunction`).
 type Value<T> = NumberField<T> | ValueFunction<T>;
 ```
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
 ###### `NumberField<T>`
 
 The fields of a row whose value is a number, or absent.
@@ -4938,6 +5004,17 @@ data reference then. A native or bound function is compared by identity.
 type ValueFunction<T> = (d: T, index: number) => number | null | undefined;
 ```
 
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 ### Bar
 
 Bars along the x axis (a bar or column chart): one per category, grouped side by side, stacked, or as shares of a whole.
@@ -4973,7 +5050,7 @@ const SPEND = [
 export default function PerCategory() {
   const { Chart, XAxis, YAxis, Bar } = useChart(SPEND);
   return (
-    <Chart height={260} ariaLabel="Actual spend per cost centre in February">
+    <Chart height={260} aria-label="Actual spend per cost centre in February">
       <XAxis value="costCentre" />
       <YAxis label="€" />
       <Bar value="actual" name="Actual" />
@@ -5006,7 +5083,7 @@ const FEBRUARY = [
 export default function Grouped() {
   const { Chart, XAxis, YAxis, Bar } = useChart(FEBRUARY);
   return (
-    <Chart height={280} ariaLabel="Budget and actual per cost centre in February">
+    <Chart height={280} aria-label="Budget and actual per cost centre in February">
       <XAxis value="costCentre" />
       <YAxis label="€" />
       {/* A token, so that it follows the colour scheme. */}
@@ -5045,7 +5122,7 @@ const signed = (v: number) => (v > 0 ? `+${(v / 1000).toFixed(0)}k` : `${(v / 10
 export default function Deviation() {
   const { Chart, XAxis, YAxis, Bar } = useChart(DEVIATION);
   return (
-    <Chart height={280} ariaLabel="Forecast against budget for the year, per cost centre">
+    <Chart height={280} aria-label="Forecast against budget for the year, per cost centre">
       <XAxis value="costCentre" />
       <YAxis tickFormat={signed} label="€" />
       <Bar value="euros" name="Over budget" />
@@ -5082,7 +5159,7 @@ export default function Stacked() {
   const { Chart, XAxis, YAxis, Bar } = useChart(DELAYS);
 
   return (
-    <Chart height={280} ariaLabel="Minutes late per working day, by cause">
+    <Chart height={280} aria-label="Minutes late per working day, by cause">
       <XAxis value="day" />
       <YAxis label="Minutes late" />
       <Bar value="traffic" name="Traffic" stack="delay" />
@@ -5123,7 +5200,7 @@ const minutes = (v: number) => `${v} min`;
 export default function Percent() {
   const { Chart, XAxis, YAxis, Bar } = useChart(DELAYS);
   return (
-    <Chart height={280} ariaLabel="Share of each cause in the minutes late per working day">
+    <Chart height={280} aria-label="Share of each cause in the minutes late per working day">
       <XAxis value="day" />
       <YAxis />
       <Bar value="traffic" name="Traffic" stack="delay" normalize format={minutes} />
@@ -5154,7 +5231,7 @@ export default function Histogram() {
   const bins = useMemo(() => bin(MINUTES_TO_ANSWER, { width: 20 }), []);
   const { Chart, XAxis, YAxis, Bar } = useChart(bins);
   return (
-    <Chart height={260} ariaLabel="Minutes to answer 40 support tickets, counted in bins of 20 minutes">
+    <Chart height={260} aria-label="Minutes to answer 40 support tickets, counted in bins of 20 minutes">
       <XAxis value="x" label="minutes to answer" />
       <YAxis label="tickets" />
       <Bar value="count" name="Tickets" barWidth={0.94} />
@@ -5178,12 +5255,12 @@ The keys of [Chart](#chart-1) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `value` *required* | `Value``<T>` | — | Height - a number field of the row or a function of it; null/undefined/NaN/±Infinity means a gap.<br>Shown in: [One bar per category](#bar), [Group bars side by side](#bar), [Show bars above and below zero](#bar) and 13 more |
+| `value` *required* | `Value``<T>` | — | Height - a number field of the row or a function of it; null/undefined/NaN/±Infinity means a gap.<br>Shown in: [One bar per category](#bar), [Group bars side by side](#bar), [Show bars above and below zero](#bar) and 14 more |
 | `xAxisId` | `string` | `"x"` | Binding to an x axis.<br>Shown in: [Bind every kind of series to a second axis (Axis)](#axis) |
 | `yAxisId` | `string` | `"y"` | Binding to a y axis.<br>Shown in: [Bind every kind of series to a second axis (Axis)](#axis) |
 | `data` | `readonly T[]` | — | Series-own data; overrides the container data.<br>Shown in: [Bind every kind of series to a second axis (Axis)](#axis) |
-| `name` | `string` | "Series n", after its place in the chart | The name in legend and tooltip. Without one a warning stands in DEV - an unnamed series is a colour nobody can look up.<br>Shown in: [One bar per category](#bar), [Group bars side by side](#bar), [Show bars above and below zero](#bar) and 13 more |
-| `format` | `(value: number) => string` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it.<br>Shown in: [Show shares of a whole](#bar), [Compare the budget with the forecast (Scenarios)](#compare-the-budget-with-the-forecast) |
+| `name` | `string` | "Series n", after its place in the chart | The name in legend and tooltip. Without one a warning stands in DEV - an unnamed series is a colour nobody can look up.<br>Shown in: [One bar per category](#bar), [Group bars side by side](#bar), [Show bars above and below zero](#bar) and 14 more |
+| `format` | `ValueFormat` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it, as a function or `NumberOptions`.<br>Shown in: [Show shares of a whole](#bar), [Compare the budget with the forecast (Scenarios)](#compare-the-budget-with-the-forecast) |
 | `color` | `string` | the palette's `--uc-series-N` | Any CSS colour value.<br>Shown in: [Group bars side by side](#bar), [See where the vans stand idle (Scenarios)](#see-where-the-vans-stand-idle), [Compare the budget with the forecast (Scenarios)](#compare-the-budget-with-the-forecast) |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value; the theme resolves it. `color` beats it.<br>Shown in: [Compare the budget with the forecast (Scenarios)](#compare-the-budget-with-the-forecast) |
 | `stack` | `string` | — | The stack this series stands in: every Bar and Area with the same id on the same x and y axis stands on the ones registered before it. A gap stacks as zero; negative values stack downward from zero. The tooltip names each series' own value and the stack's total.<br>Shown in: [Stack bars](#bar), [Show shares of a whole](#bar), [Read a stack's total in the table (Tooltip)](#tooltip) and 1 more |
@@ -5201,6 +5278,15 @@ by its name, or a function, compared by its source text (`ValueFunction`).
 type Value<T> = NumberField<T> | ValueFunction<T>;
 ```
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
 ###### `NumberField<T>`
 
 The fields of a row whose value is a number, or absent.
@@ -5225,11 +5311,22 @@ data reference then. A native or bound function is compared by identity.
 type ValueFunction<T> = (d: T, index: number) => number | null | undefined;
 ```
 
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 #### Known limits
 
 - Horizontal bars are the next kind to come ([ADR-0059](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0059-the-set-of-chart-kinds-is-open.md)); until then a `Matrix` or a `Table` ranks by name.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Scatter
 
@@ -5384,7 +5481,7 @@ const ARRIVALS: Arrival[] = TOURS.flatMap((tour) =>
 export default function Arrivals() {
   const { Chart, XAxis, YAxis, Scatter } = useChart(ARRIVALS);
   return (
-    <Chart height={260} ariaLabel="Every stop of today's tours: minutes after its window closed">
+    <Chart height={260} aria-label="Every stop of today's tours: minutes after its window closed">
       <XAxis value="t" time label="Arrival" />
       <YAxis label="Minutes late" />
       <Scatter value="late" name="Stop" radius={4} />
@@ -5465,7 +5562,7 @@ const OBJECTIVE = SERVICES.find((one) => one.id === "checkout")!.latencySlo;
 export default function AgainstATarget() {
   const { Chart, XAxis, YAxis, Scatter } = useChart(TRACES);
   return (
-    <Chart height={300} ariaLabel="Traced Checkout requests against the latency objective">
+    <Chart height={300} aria-label="Traced Checkout requests against the latency objective">
       <XAxis value="t" time />
       <YAxis label="ms" />
       <LimitLine value={OBJECTIVE} severity="warning" label="Objective" />
@@ -5494,7 +5591,7 @@ The keys of [Chart](#chart-1) apply here.
 | `yAxisId` | `string` | `"y"` | Binding to a y axis.<br>Shown in: [Bind every kind of series to a second axis (Axis)](#axis) |
 | `data` | `readonly T[]` | — | Series-own data; overrides the container data.<br>Shown in: [Bind every kind of series to a second axis (Axis)](#axis) |
 | `name` | `string` | "Series n", after its place in the chart | The name in legend and tooltip. Without one a warning stands in DEV - an unnamed series is a colour nobody can look up.<br>Shown in: [Plot single measurements](#scatter), [Mark samples that miss a target](#scatter), [Mix series kinds (Chart)](#chart-1) and 3 more |
-| `format` | `(value: number) => string` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it. |
+| `format` | `ValueFormat` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it, as a function or `NumberOptions`. |
 | `color` | `string` | the palette's `--uc-series-N` | Any CSS colour value. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value; the theme resolves it.<br>Shown in: [Mark samples that miss a target](#scatter) |
 | `radius` | `number` | `3` | Point radius in CSS pixels.<br>Shown in: [Plot single measurements](#scatter), [Mark samples that miss a target](#scatter) |
@@ -5510,6 +5607,15 @@ by its name, or a function, compared by its source text (`ValueFunction`).
 type Value<T> = NumberField<T> | ValueFunction<T>;
 ```
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
 ###### `NumberField<T>`
 
 The fields of a row whose value is a number, or absent.
@@ -5534,6 +5640,17 @@ data reference then. A native or bound function is compared by identity.
 type ValueFunction<T> = (d: T, index: number) => number | null | undefined;
 ```
 
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 ### BoxPlot
 
 A distribution per position (a box plot, box-and-whisker): quartiles, median and whiskers, per service, per group or per hour. Reach for it to compare spreads, not single values.
@@ -5574,7 +5691,7 @@ const RESPONSE_TIMES: ResponseTime[] = [
 export default function Minimal() {
   const { Chart, XAxis, YAxis, BoxPlot } = useChart(RESPONSE_TIMES);
   return (
-    <Chart height={260} ariaLabel="Response time per service over the last hour">
+    <Chart height={260} aria-label="Response time per service over the last hour">
       <XAxis value="service" />
       <YAxis tickFormat={(v) => `${v} ms`} />
       <BoxPlot
@@ -5720,7 +5837,7 @@ const BOXES = hourBoxes();
 export default function OverTime() {
   const { Chart, XAxis, YAxis, BoxPlot } = useChart(BOXES);
   return (
-    <Chart height={280} ariaLabel="Checkout median latency per hour today">
+    <Chart height={280} aria-label="Checkout median latency per hour today">
       <XAxis value="hour" time />
       <YAxis tickFormat={(v) => `${v} ms`} />
       <BoxPlot
@@ -5766,7 +5883,7 @@ const RESPONSE_TIMES: ResponseTime[] = [
 export default function WithOutliers() {
   const { Chart, XAxis, YAxis, BoxPlot } = useChart(RESPONSE_TIMES);
   return (
-    <Chart height={300} ariaLabel="Response time per service over the last hour, with outliers">
+    <Chart height={300} aria-label="Response time per service over the last hour, with outliers">
       <XAxis value="service" />
       <YAxis tickFormat={(v) => `${v} ms`} />
       <BoxPlot
@@ -5814,7 +5931,7 @@ const notch = (d: Batch) => (1.57 * (d.q3 - d.q1)) / Math.sqrt(d.n);
 export default function MeanAndNotches() {
   const { Chart, XAxis, YAxis, BoxPlot } = useChart(BATCHES);
   return (
-    <Chart height={300} ariaLabel="Breaking strength per clay supplier, with mean and notches">
+    <Chart height={300} aria-label="Breaking strength per clay supplier, with mean and notches">
       <XAxis value="supplier" />
       <YAxis tickFormat={(v) => `${v} N`} />
       <BoxPlot
@@ -5872,7 +5989,7 @@ const AFTER: Spread[] = [
 export default function Grouped() {
   const { Chart, XAxis, YAxis, BoxPlot } = useChart(BEFORE);
   return (
-    <Chart height={280} ariaLabel="Response time per service before and after the release">
+    <Chart height={280} aria-label="Response time per service before and after the release">
       <XAxis value="service" />
       <YAxis tickFormat={(v) => `${v} ms`} />
       {[
@@ -5928,7 +6045,7 @@ const THIS_WEEK: Spread[] = [
 export default function AgainstTheObjective() {
   const { Chart, XAxis, YAxis, BoxPlot } = useChart(LAST_WEEK);
   return (
-    <Chart height={280} ariaLabel="Checkout 95th percentile per region and week against its objective">
+    <Chart height={280} aria-label="Checkout 95th percentile per region and week against its objective">
       <XAxis value="region" />
       <YAxis tickFormat={(v) => `${v} ms`} />
       <BoxPlot
@@ -5981,7 +6098,7 @@ const mm = (v: number) => `${v.toFixed(2)} mm`;
 export default function Detailed() {
   const { Chart, XAxis, YAxis, BoxPlot, Line } = useChart(BOXES);
   return (
-    <Chart height={320} ariaLabel="Tile length per shift, with the medians as a line">
+    <Chart height={320} aria-label="Tile length per shift, with the medians as a line">
       <XAxis value="shift" label="Shift" />
       <YAxis tickFormat={mm} />
       <BoxPlot
@@ -6026,7 +6143,7 @@ The keys of [Chart](#chart-1) apply here.
 | `yAxisId` | `string` | `"y"` | Binding to a y axis. |
 | `data` | `readonly T[]` | — | Series-own data; overrides the container data.<br>Shown in: [Before and after, side by side](#boxplot), [Against the objective](#boxplot) |
 | `name` | `string` | "Series n", after its place in the chart | The name in legend and tooltip. Without one a warning stands in DEV.<br>Shown in: [One box per service](#boxplot), [A box per hour on a time axis](#boxplot), [With outliers](#boxplot) and 4 more |
-| `format` | `(value: number) => string` | the y axis' `tickFormat`, else the built-in number format | Every number of the box as the tooltip and the table write it.<br>Shown in: [Mean and notches: do two medians differ?](#boxplot) |
+| `format` | `ValueFormat` | the y axis' `tickFormat`, else the built-in number format | Every number of the box as the tooltip and the table write it, as a function or `NumberOptions`.<br>Shown in: [Mean and notches: do two medians differ?](#boxplot) |
 | `color` | `string` | the palette's `--uc-series-N` | Any CSS colour value. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value; the theme resolves it. `color` beats it. Set by the caller: a box out of its specification is the caller's judgement, not the library's.<br>Shown in: [Against the objective](#boxplot) |
 | `boxWidth` | `number` | `0.8` | Width as a fraction of the step, as a bar's: boxes and bars on one x axis share this fraction and stand side by side.<br>Shown in: [Mean and notches: do two medians differ?](#boxplot), [A box per shift, its medians as a line](#boxplot) |
@@ -6050,6 +6167,15 @@ A list read from the row: the name of a list field or a function.
 type ListValue<T> = ListField<T> | ListFunction<T>;
 ```
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
 ###### `NumberField<T>`
 
 The fields of a row whose value is a number, or absent.
@@ -6096,11 +6222,22 @@ empty array is none; a value that is not finite is left out.
 type ListFunction<T> = (d: T, index: number) => readonly number[] | null | undefined;
 ```
 
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 #### Known limits
 
 - No horizontal boxes, no violin or jittered points, no box width by count: a density is smoothing, a jitter a picture that does not repeat.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.42.0/docs/adr/0032-what-umriss-is-not.md).
+What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/charts-v0.43.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### StateBand
 
@@ -6282,7 +6419,7 @@ const DAY = vehicleDay("v1");
 export default function OneVehicle() {
   const { Chart, XAxis, YAxis, StateBand } = useChart(DAY);
   return (
-    <Chart height={150} ariaLabel="States of van FP 214 K through the day">
+    <Chart height={150} aria-label="States of van FP 214 K through the day">
       <XAxis value="t" time label="Time" />
       {/* Without a lane the band fills its y axis; one tick names it. */}
       <YAxis domain={[0, 1]} ticks={[0.5]} tickFormat={() => "FP 214 K"} grid={false} />
@@ -6480,7 +6617,7 @@ const STATES = vehicleDay("v2");
 export default function UnderACourse() {
   const { Chart, XAxis, YAxis, StateBand, Line } = useChart(BATTERY);
   return (
-    <Chart height={320} ariaLabel="An e-van's charge above what it was doing">
+    <Chart height={320} aria-label="An e-van's charge above what it was doing">
       <XAxis value="t" time label="Time" />
       <YAxis domain={[-40, 100]} ticks={[0, 25, 50, 75, 100]} label="Charge %" />
       {/* The lane: the bottom unit of five, the rest is room for the course. */}
@@ -6660,7 +6797,7 @@ const FLEET = VEHICLES.map((vehicle) => ({ vehicle, day: vehicleDay(vehicle.id)
 export default function OneLaneEach() {
   const { Chart, XAxis, YAxis, StateBand } = useChart(FLEET[0]!.day);
   return (
-    <Chart height={300} ariaLabel="The states of all eight vehicles through the day">
+    <Chart height={300} aria-label="The states of all eight vehicles through the day">
       <XAxis value="t" time label="Time" />
       <YAxis grid={false} />
       {FLEET.map(({ vehicle, day }) => (
@@ -6822,7 +6959,7 @@ const SUCCESS_BY_HOUR: readonly SuccessCell[] = (() => {
 export default function ByLimits() {
   const { Chart, XAxis, YAxis, Matrix } = useChart(SUCCESS_BY_HOUR);
   return (
-    <Chart height={280} ariaLabel="Successful requests per service and hour yesterday, by limits">
+    <Chart height={280} aria-label="Successful requests per service and hour yesterday, by limits">
       <XAxis value="hour" ticks={[0, 6, 12, 18]} tickFormat={(v) => `${v}:00`} label="Hour" />
       <YAxis />
       <Matrix
@@ -6915,7 +7052,7 @@ const SUCCESS_BY_HOUR: readonly SuccessCell[] = (() => {
 export default function Gradient() {
   const { Chart, XAxis, YAxis, Matrix } = useChart(SUCCESS_BY_HOUR);
   return (
-    <Chart height={280} ariaLabel="Successful requests per service and hour yesterday, as a gradient">
+    <Chart height={280} aria-label="Successful requests per service and hour yesterday, as a gradient">
       <XAxis value="hour" ticks={[0, 6, 12, 18]} tickFormat={(v) => `${v}:00`} label="Hour" />
       <YAxis />
       <Matrix value="service" level="success" name="Success rate" />
@@ -6942,7 +7079,7 @@ The keys of [Chart](#chart-1) apply here.
 | `yAxisId` | `string` | `"y"` | Binding to a y axis. |
 | `data` | `readonly T[]` | — | Series-own data; overrides the container data. |
 | `name` | `string` | "Series n", after its place in the chart | The name in legend and tooltip. Without one a warning stands in DEV - an unnamed series is a colour nobody can look up.<br>Shown in: [Colour cells by their limits](#matrix), [Colour cells along a gradient](#matrix), [Mark bands, limits and cells (Chart)](#chart-1) and 1 more |
-| `format` | `(value: number) => string` | the built-in number format | The level as the tooltip writes it. The y axis' `tickFormat` writes the row, not the level.<br>Shown in: [Colour cells by their limits](#matrix) |
+| `format` | `ValueFormat` | the built-in number format | The level as the tooltip writes it, as a function or `NumberOptions`. The y axis' `tickFormat` writes the row, not the level.<br>Shown in: [Colour cells by their limits](#matrix) |
 
 ##### Types on this page
 
@@ -6991,6 +7128,15 @@ type MatrixColoring =
     };
 ```
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
 ###### `AxisValue`
 
 What an axis reads from a row ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)): a number - a position, or an
@@ -7042,6 +7188,17 @@ target.
 | `limits` | `readonly ``Limit``[]` | — | In any order; none, one or several.<br>Shown in: [Colour cells by their limits](#matrix), [Mark bands, limits and cells (Chart)](#chart-1) |
 | `target` | `number` | — |  |
 
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 ###### `Limit`
 
 A bound: a value, a side and a severity. No more - a tolerance band is
@@ -7184,7 +7341,7 @@ const OBJECTIVE = SERVICES.find((one) => one.id === "checkout")!.latencySlo;
 export default function Objective() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={260} ariaLabel="Checkout's latency against its objective">
+    <Chart height={260} aria-label="Checkout's latency against its objective">
       <XAxis value="t" time />
       <YAxis label="ms" />
       <LimitLine value={OBJECTIVE} severity="alarm" label="Objective" />
@@ -7288,7 +7445,7 @@ const CHECKOUT = metrics("checkout");
 export default function Band() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={260} ariaLabel="Checkout's error rate against its warning band and alarm limit">
+    <Chart height={260} aria-label="Checkout's error rate against its warning band and alarm limit">
       <XAxis value="t" time />
       <YAxis label="Errors %" />
       <LimitBand from={1} to={2} severity="warning" label="Watch" />
@@ -7491,7 +7648,7 @@ const LANES = NORTH.map((vehicle) => ({ vehicle, day: vehicleDay(vehicle.id) }))
 export default function LimitsAndState() {
   const { Chart, XAxis, YAxis, StateBand, Line } = useChart(BATTERY);
   return (
-    <Chart height={340} ariaLabel="An e-van's charge against its limits, above the states of the North depot's vehicles">
+    <Chart height={340} aria-label="An e-van's charge against its limits, above the states of the North depot's vehicles">
       <XAxis value="t" time label="Time" />
       <YAxis domain={[-100, 100]} ticks={[0, 20, 40, 60, 80, 100]} label="Charge %" />
       {/* The lanes take the lower places; the domain leaves the rest as room for the course. */}
@@ -7656,7 +7813,7 @@ const SHIFT_START = new Date(2026, 2, 17, 6).getTime();
 export default function KilnZone() {
   const { Chart, XAxis, YAxis, Line } = useChart(SHIFT.readings);
   return (
-    <Chart height={280} ariaLabel="Kiln K1 zone 3 against its tolerance and alarm limit over the early shift">
+    <Chart height={280} aria-label="Kiln K1 zone 3 against its tolerance and alarm limit over the early shift">
       <XAxis value={(d) => SHIFT_START + d.minute * 60_000} time />
       <YAxis label="°C" />
       <LimitBand from={KILN.tolerance[0]} to={KILN.tolerance[1]} severity="warning" label="Tolerance" />
@@ -7762,7 +7919,7 @@ const CHECKOUT = metrics("checkout");
 export default function AlongTime() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={260} ariaLabel="Checkout's latency across a maintenance window and the start of a release freeze">
+    <Chart height={260} aria-label="Checkout's latency across a maintenance window and the start of a release freeze">
       <XAxis value="t" time />
       <YAxis label="ms" />
       <LimitBand orientation="x" from={new Date(2026, 2, 17, 2)} to={new Date(2026, 2, 17, 3)} color="#5b7c99" label="Maintenance" />
@@ -7926,7 +8083,7 @@ const LIMITS = controlLimits(
 export default function SpecificationAndControl() {
   const { Chart, XAxis, YAxis, Line } = useChart(SAMPLES);
   return (
-    <Chart height={300} ariaLabel="The tile length against its specification and its control limits">
+    <Chart height={300} aria-label="The tile length against its specification and its control limits">
       <XAxis value="minute" label="Minute of the shift" />
       <YAxis label="mm" />
       <LimitBand from={597.5} to={602.5} severity="warning" label="Specification" />
@@ -8177,7 +8334,7 @@ const REFERENCE_WINDOW = { kind: "referenceWindow", from: 0, to: 15 } as const;
 export default function ControlChartExample() {
   const { Chart, XAxis, YAxis } = useChart(SAMPLES);
   return (
-    <Chart height={300} ariaLabel="Control chart of the tile length after firing">
+    <Chart height={300} aria-label="Control chart of the tile length after firing">
       <XAxis value="minute" label="Minute of the shift" />
       <YAxis label="mm" />
       {/* Specification limits are chosen, control limits are computed. */}
@@ -8362,7 +8519,7 @@ export default function ListTheViolations() {
   return (
     <div className="side-by-side">
       <div style={{ flex: "1 1 320px" }}>
-        <Chart height={240} ariaLabel="Control chart of the tile length, its violations listed beside it">
+        <Chart height={240} aria-label="Control chart of the tile length, its violations listed beside it">
           <XAxis value="minute" label="Minute of the shift" />
           <YAxis label="mm" />
           <ControlChart value="length" data={SAMPLES} origin={REFERENCE_WINDOW} name="Tile length" onViolations={setFound} />
@@ -8553,7 +8710,7 @@ export default function ChooseTheRules() {
   return (
     <div className="side-by-side">
       <div style={{ flex: "1 1 320px" }}>
-        <Chart height={240} ariaLabel="Control chart of the tile length under three of the four rules">
+        <Chart height={240} aria-label="Control chart of the tile length under three of the four rules">
           <XAxis value="minute" label="Minute of the shift" />
           <YAxis label="mm" />
           <ControlChart
@@ -8604,7 +8761,7 @@ The keys of [Chart](#chart-1) apply here.
 | `xAxisId` | `string` | `"x"` | Binding to an x axis. |
 | `yAxisId` | `string` | `"y"` | Binding to a y axis. |
 | `name` | `string` | "Series n", after its place in the chart | The name in legend and tooltip. Without one a warning stands in DEV - an unnamed series is a colour nobody can look up.<br>Shown in: [Chart a process against its control limits](#controlchart), [List the rule violations](#controlchart), [Choose the rules](#controlchart) and 1 more |
-| `format` | `(value: number) => string` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it - on the line and on the violations. |
+| `format` | `ValueFormat` | the y axis' `tickFormat`, else the built-in number format | The value as the tooltip writes it - on the line and on the violations., as a function or `NumberOptions`. |
 | `color` | `string` | the palette's `--uc-series-N` | Any CSS colour value. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value for the line; the theme resolves it. The violations are always "alarm". |
 | `rules` | `Partial<``RuleOptions``>` | — | Switchable one by one; run lengths are parameters.<br>Shown in: [Choose the rules](#controlchart) |
@@ -8643,6 +8800,15 @@ type ControlLimitOrigin =
   | { readonly kind: "referenceWindow"; readonly from: number; readonly to: number };
 ```
 
+###### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
 ###### `RuleOptions`
 
 Which rules run, and with which run lengths.
@@ -8689,6 +8855,17 @@ data reference then. A native or bound function is compared by identity.
 type ValueFunction<T> = (d: T, index: number) => number | null | undefined;
 ```
 
+###### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 ###### `RuleName`
 
 Name of a rule, the way it is switched on and off in `violations`.
@@ -8735,7 +8912,7 @@ export default function ParetoExample() {
   const { entries } = useMemo(() => pareto(FAILED_DELIVERIES, { collectRank: 6, remainderName: "Other" }), []);
   const { Chart, XAxis, YAxis, Bar, Line } = useChart(entries);
   return (
-    <Chart height={300} ariaLabel="Failed deliveries by cause, sorted, with the cumulative share">
+    <Chart height={300} aria-label="Failed deliveries by cause, sorted, with the cumulative share">
       <XAxis value="name" />
       <YAxis label="Failed deliveries" />
       <YAxis
@@ -8768,12 +8945,6 @@ From `ChartProps` — the full table stands on [Chart](#chart-1).
 | [`height`](#chart-1) | `number` | fills the frame, at least 300 px | Height in CSS pixels, fixed. Left out, the chart fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 300 px, which is also its height in a frame without one. A different floor goes through `style`'s `minHeight` ([ADR-0050](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0050-a-chart-fills-its-frame-never-below-its-floor.md)). |
 | [`children`](#chart-1) | `ReactNode` | — | The axes, series and companions of this chart. They draw nothing themselves: each registers its configuration and the scene draws it, and the order in the JSX is the drawing order. |
 
-###### Accessibility
-
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| [`ariaLabel`](#chart-1) | `string` | — | Required in DEV through a warning. |
-
 From `XAxisProps` — the full table stands on [Axis](#axis).
 
 | Prop | Type | Default | Description |
@@ -8781,7 +8952,7 @@ From `XAxisProps` — the full table stands on [Axis](#axis).
 | [`value`](#axis) *required* | [`AxisField`](#axis)`<T> \| ((d: T, index: number) => `[`AxisValue`](#axis)`)` | — | Where a row lies on this axis: a field of the row, compared by its name, or a function of it, compared by its source text as a series' is (`ValueFunction`) - with the same closure limit. A number is a position, a `Date` an instant, a string a category: every distinct one gets a place of its own, in the order the rows bring them, a tick and its name as the label ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)). The type decides, never the content - `"2024"` is a category, `2024` a number - and a row without a value has no place. The axis reads the rows of every series bound to it; where those bring their own `data`, name their row: `<XAxis<HourCount> value="hour" />`. |
 | [`id`](#axis) | `string` | `"x"` | Axis id, through which series bind themselves. |
 | [`label`](#axis) | `string` | — | Axis title. |
-| [`tickFormat`](#axis) | `(v: number) => string` | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity. |
+| [`tickFormat`](#axis) | [`ValueFormat`](#axis) | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity. Or `NumberOptions`: Intl's options in the wording's locale, compared by value; the step's places stay unless the options set digits. |
 
 From `YAxisProps` — the full table stands on [Axis](#axis).
 
@@ -8791,7 +8962,7 @@ From `YAxisProps` — the full table stands on [Axis](#axis).
 | [`position`](#axis) | `"left" \| "right"` | `"left"` | Which edge the axis stands at. Several y axes per side are stacked outwards, so that extents of clearly different magnitude stay readable. |
 | [`id`](#axis) | `string` | `"y"` | Axis id, through which series bind themselves. |
 | [`label`](#axis) | `string` | — | Axis title. |
-| [`tickFormat`](#axis) | `(v: number) => string` | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity. |
+| [`tickFormat`](#axis) | [`ValueFormat`](#axis) | — | Label of a tick. Compared by its source text: one that reads a changed closure variable under the same text does not relabel the axis - give it a new text or remount. A bound `Intl.NumberFormat#format` is compared by identity. Or `NumberOptions`: Intl's options in the wording's locale, compared by value; the step's places stay unless the options set digits. |
 
 From `LineProps` — the full table stands on [Line](#line).
 
@@ -8954,7 +9125,7 @@ const SIGN_IN = metrics("sign-in");
 function Latencies({ mode }: { mode: "x" | "nearest" }) {
   const { Chart, XAxis, YAxis, Line } = useChart(SEARCH);
   return (
-    <Chart height={220} ariaLabel={`Search and sign-in latency, tooltip mode ${mode}`}>
+    <Chart height={220} aria-label={`Search and sign-in latency, tooltip mode ${mode}`}>
       <XAxis value="t" time tickCount={4} />
       <YAxis label="ms" />
       <Line value="p95" name="Search" />
@@ -9095,7 +9266,7 @@ function AgainstObjective({ hit }: { hit: TooltipHit<MetricPoint> }) {
 export default function OwnContent() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={280} ariaLabel="Checkout and billing latency, the tooltip against their objectives">
+    <Chart height={280} aria-label="Checkout and billing latency, the tooltip against their objectives">
       <XAxis value="t" time />
       <YAxis label="ms" />
       <Line value="p95" name="Checkout" />
@@ -9109,7 +9280,7 @@ export default function OwnContent() {
 
 ##### Write each value in its unit
 
-`format` on a series writes its value in the tooltip; without it the y axis' `tickFormat` does, and without that a bare number.
+`format` on a series writes its value in the tooltip; without it the y axis' `tickFormat` does, and without that a bare number. Either is a function or Intl's options, written in the chart's wording's locale - the same object a table column takes.
 
 ```tsx
 import { Legend, Tooltip, useChart } from "@umriss-ui/charts";
@@ -9198,12 +9369,12 @@ function metrics(serviceId: string): MetricPoint[] {
 const CHECKOUT = metrics("checkout");
 
 const milliseconds = (v: number) => `${v.toFixed(0)} ms`;
-const percent = (v: number) => `${v.toFixed(2)} %`;
+const percent = { decimals: 2, style: "unit", unit: "percent" } as const;
 
 export default function ValueFormat() {
   const { Chart, XAxis, YAxis, Line } = useChart(CHECKOUT);
   return (
-    <Chart height={260} ariaLabel="Checkout's latency and error rate with their units">
+    <Chart height={260} aria-label="Checkout's latency and error rate with their units">
       <XAxis value="t" time />
       <YAxis label="ms" />
       <YAxis id="errors" position="right" label="Errors %" />
@@ -9292,7 +9463,7 @@ const hours = (v: number) => `${v.toFixed(0)} h`;
 export default function ValuesAsTable() {
   const { Chart, XAxis, YAxis, Line } = useChart(BURNDOWN);
   return (
-    <Chart height={260} ariaLabel="Sprint 14: hours left against the ideal">
+    <Chart height={260} aria-label="Sprint 14: hours left against the ideal">
       <XAxis value="t" ticks={BURNDOWN.map((d) => d.t)} tickFormat={day} />
       <YAxis label="Hours left" />
       <Line value="ideal" name="Ideal" format={hours} />
@@ -9413,7 +9584,7 @@ const milliseconds = (v: number) => `${v.toFixed(0)} ms`;
 export default function WeekAsTable() {
   const { Chart, XAxis, YAxis, Line } = useChart(SEARCH_WEEK);
   return (
-    <Chart height={240} ariaLabel="Search latency over last week, a reading a minute">
+    <Chart height={240} aria-label="Search latency over last week, a reading a minute">
       <XAxis value="t" time domain="data" zoomable label="Time" />
       <YAxis label="ms" />
       <Line value="p95" name="p95" format={milliseconds} />
@@ -9443,7 +9614,7 @@ const LATENCY = [
 export default function Limits() {
   const { Chart, XAxis, YAxis, Line } = useChart(LATENCY);
   return (
-    <Chart height={260} ariaLabel="Checkout's latency against its objective and its warning band">
+    <Chart height={260} aria-label="Checkout's latency against its objective and its warning band">
       <XAxis value="x" tickFormat={(v) => LATENCY[Math.round(v)]?.time ?? ""} />
       <YAxis label="ms" tickFormat={(v) => `${v} ms`} />
       <LimitBand from={250} to={300} severity="warning" label="Warning band" />
@@ -9477,7 +9648,7 @@ export default function ChooseAHit() {
   const { Chart, XAxis, YAxis, Line } = useChart(ORDERS, { onSelect: setChosen });
   return (
     <>
-      <Chart height={260} ariaLabel="Orders per hour, by channel">
+      <Chart height={260} aria-label="Orders per hour, by channel">
         <XAxis value="hour" tickFormat={(v) => `${v}:00`} />
         <YAxis label="orders" />
         <Line value="web" name="Web" />
@@ -9501,6 +9672,114 @@ export default function ChooseAHit() {
 }
 ```
 
+##### Drill down from a year to its days
+
+`onSelect` on a bar drills in: a year opens its months, a month its days. The chart keeps no level and draws none - the stack of levels is this example's state, and the rows and the categories follow it ([ADR-0056](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0056-a-chart-reports-a-chosen-hit-and-holds-no-selection.md)).
+
+```tsx
+import { useState } from "react";
+import { Tooltip, useChart } from "@umriss-ui/charts";
+
+/* Orders per day for 2024 and 2025, written out here so the example runs on its own: each day's
+   count follows from its date, and a month and a year are the sums of the days in them. */
+const YEARS = [2024, 2025];
+const MONTHS = ["Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec"];
+const DAYS = YEARS.flatMap((year) =>
+  MONTHS.flatMap((_, month) => {
+    const length = new Date(year, month + 1, 0).getDate();
+    return Array.from({ length }, (_, index) => {
+      const day = index + 1;
+      const weekend = [0, 6].includes(new Date(year, month, day).getDay());
+      return { year, month, day, orders: ((year * 31 + month * 7 + day * 13) % 40) + (weekend ? 30 : 70) };
+    });
+  }),
+);
+
+interface Level {
+  year: number;
+  month?: number;
+}
+
+interface Row {
+  level: "year" | "month" | "day";
+  year: number;
+  month: number;
+  label: string;
+  orders: number;
+}
+
+function sum(days: readonly { orders: number }[]): number {
+  return days.reduce((total, one) => total + one.orders, 0);
+}
+
+/* The rows of the level the stack stands on: the years, the months of one year, or the days of one month. */
+function rowsAt(stack: readonly Level[]): Row[] {
+  const top = stack.at(-1);
+  if (top === undefined) {
+    return YEARS.map((year) => ({
+      level: "year",
+      year,
+      month: 0,
+      label: String(year),
+      orders: sum(DAYS.filter((d) => d.year === year)),
+    }));
+  }
+  if (top.month === undefined) {
+    return MONTHS.map((name, month) => ({
+      level: "month",
+      year: top.year,
+      month,
+      label: name,
+      orders: sum(DAYS.filter((d) => d.year === top.year && d.month === month)),
+    }));
+  }
+  return DAYS.filter((d) => d.year === top.year && d.month === top.month).map((d) => ({
+    level: "day",
+    year: d.year,
+    month: d.month,
+    label: String(d.day),
+    orders: d.orders,
+  }));
+}
+
+export default function DrillDown() {
+  const [stack, setStack] = useState<Level[]>([]);
+  const rows = rowsAt(stack);
+  const top = stack.at(-1);
+  const where = top === undefined ? "all years" : top.month === undefined ? String(top.year) : `${MONTHS[top.month]} ${top.year}`;
+  /* The level the back button returns to: the months of a year are named by the year, the years by "all years". */
+  const above = stack.length <= 1 ? "all years" : String(stack[0]!.year);
+  const { Chart, XAxis, YAxis, Bar } = useChart(rows, {
+    onSelect: (hit) => {
+      const row = hit.points[0]?.datum;
+      if (row === undefined || row.level === "day") return;
+      setStack((current) => [...current, row.level === "year" ? { year: row.year } : { year: row.year, month: row.month }]);
+    },
+  });
+  return (
+    <>
+      <dl className="metrics">
+        <div>
+          <dt>Showing</dt>
+          <dd>{where}</dd>
+        </div>
+      </dl>
+      {top !== undefined && (
+        <button type="button" onClick={() => setStack((current) => current.slice(0, -1))}>
+          Back to {above}
+        </button>
+      )}
+      <Chart height={260} aria-label={`Orders, ${where}`}>
+        <XAxis value="label" />
+        <YAxis label="orders" />
+        <Bar value="orders" name="Orders" />
+        <Tooltip mode="x" />
+      </Chart>
+    </>
+  );
+}
+```
+
 ##### Read a stack's total in the table
 
 The table of a stacked chart ends the stack's members with a Total column - the sum the tooltip shows at the same place, so nobody adds the row up by hand.
@@ -9520,7 +9799,7 @@ const TICKETS = [
 export default function TotalOfAStack() {
   const { Chart, XAxis, YAxis, Bar } = useChart(TICKETS);
   return (
-    <Chart height={260} ariaLabel="Tickets opened per working day, by channel">
+    <Chart height={260} aria-label="Tickets opened per working day, by channel">
       <XAxis value="day" />
       <YAxis label="Tickets" />
       <Bar value="mail" name="Mail" stack="tickets" />
@@ -9544,7 +9823,7 @@ The keys of [Chart](#chart-1) apply here.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `mode` | `"x" \| "nearest"` | `"x"` | "x": every series at the x position; "nearest": only the nearest point.<br>Shown in: [Report every series or the nearest](#tooltip), [Write the tooltip yourself](#tooltip), [Write each value in its unit](#tooltip) and 61 more |
+| `mode` | `"x" \| "nearest"` | `"x"` | "x": every series at the x position; "nearest": only the nearest point.<br>Shown in: [Report every series or the nearest](#tooltip), [Write the tooltip yourself](#tooltip), [Write each value in its unit](#tooltip) and 62 more |
 | `limits` | `boolean` | `false` | Adds a row for every labelled `LimitLine` and `LimitBand` on the hit's y axis - its label and value in that axis' format - to the built-in tooltip, and the same to what a key reads out. Limits are not series and stay out of the tooltip unless asked for.<br>Shown in: [Read the limits at the hit](#tooltip) |
 | `render` | `(hit: ``TooltipHit``<T>) => ReactNode` | the built-in tooltip | Render prop for content of one's own. Compared by its source text, like `tickFormat` - with the same closure limit.<br>Shown in: [Write the tooltip yourself](#tooltip), [Fix the domain and name the ticks (Axis)](#axis) |
 
@@ -9559,7 +9838,7 @@ The keys of [Chart](#chart-1) apply here.
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `onViewChange` | `(view: `[`ChartView`](#view)`) => void` | — | Every change the reader makes, once, always the whole view - the one to keep, or to hand another chart's `setView`. A pan or zoom is reported at most once per frame. Not called for the view the chart starts with, nor for one `setView` applies.<br>Shown in: [Keep charts in step (Zoom and pan)](#zoom-and-pan), [Read it by keyboard and screen reader (Chart)](#chart-1) |
-| `onSelect` | `(hit: ``TooltipHit``<Z>) => void` | — | The reader chose a point: a click on a hit (a tap too), or Enter on the Active point - the same hit the tooltip's `render` receives. Once per click; the end of a drag does not report, and the second click of a double click does not either. The chart holds no selection and draws none: what is chosen is the application's state. Needs a `<Tooltip>`, which makes the hits; the hit does not travel over `syncId`.<br>Shown in: [Choose a hit](#tooltip) |
+| `onSelect` | `(hit: ``TooltipHit``<Z>) => void` | — | The reader chose a point: a click on a hit (a tap too), or Enter on the Active point - the same hit the tooltip's `render` receives. Once per click; the end of a drag does not report, and the second click of a double click does not either. The chart holds no selection and draws none: what is chosen is the application's state. Needs a `<Tooltip>`, which makes the hits; the hit does not travel over `syncId`.<br>Shown in: [Choose a hit](#tooltip), [Drill down from a year to its days](#tooltip) |
 
 ##### Types on this page
 
@@ -9571,7 +9850,7 @@ A custom tooltip's `render` receives it.
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `xValue` *required* | `number` | — | <br>Shown in: [Write the tooltip yourself](#tooltip), [Choose a hit](#tooltip), [Fix the domain and name the ticks (Axis)](#axis) |
-| `points` *required* | `readonly ``TooltipPoint``<T>[]` | — | <br>Shown in: [Write the tooltip yourself](#tooltip), [Choose a hit](#tooltip), [Fix the domain and name the ticks (Axis)](#axis) |
+| `points` *required* | `readonly ``TooltipPoint``<T>[]` | — | <br>Shown in: [Write the tooltip yourself](#tooltip), [Choose a hit](#tooltip), [Drill down from a year to its days](#tooltip) and 1 more |
 | `xPx` *required* | `number` | — | Pixel position of the crosshair (snapped to the data point). |
 | `yPx` *required* | `number` | — | Pixel position of the primary hit. |
 
@@ -9585,7 +9864,7 @@ One hit per series in the tooltip.
 | `color` *required* | `string` | — |  |
 | `xValue` *required* | `number` | — | The point's x value on its own x axis - with several x axes it can differ from the hit's. |
 | `yValue` *required* | `number` | — | The point's y value; in a stack its own value, not its top - in a normalised stack its share in percent.<br>Shown in: [Choose a hit](#tooltip), [Fix the domain and name the ticks (Axis)](#axis) |
-| `datum` *required* | `T` | — | <br>Shown in: [Write the tooltip yourself](#tooltip) |
+| `datum` *required* | `T` | — | <br>Shown in: [Write the tooltip yourself](#tooltip), [Drill down from a year to its days](#tooltip) |
 | `index` *required* | `number` | — |  |
 | `level` | `number` | — | Only for the matrix: its level, out of the level channel. It stands here and not in yValue, because yValue is the position on the y axis - for a matrix therefore the row. Putting both into one field would be exactly the overloading [ADR-0011](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0011-named-channels-never-overloaded.md) is written against. |
 | `segment` | `{ from: number; to: number; label: string }` | — | Only for state series: the section being pointed at. A duration does not stand here - it is the difference of two numbers the entry already carries, and formatting it would presuppose knowing what the x axis means. The caller knows that, not this library. |
@@ -9740,7 +10019,7 @@ export default function HideASeries() {
           Show all
         </button>
       </div>
-      <Chart height={260} ariaLabel="Latency of three services">
+      <Chart height={260} aria-label="Latency of three services">
         <XAxis value="t" time />
         <YAxis label="ms" />
         {SERIES.map((one) => (
@@ -9832,7 +10111,7 @@ const monthName = (month: string) => MONTH_NAMES[Number(month.slice(5)) - 1] ??
 function Marketing({ placement }: { placement?: "bottom" }) {
   const { Chart, XAxis, YAxis, Line } = useChart(MARKETING);
   return (
-    <Chart height={220} ariaLabel={`Marketing's budget and forecast, legend ${placement ?? "above"}`}>
+    <Chart height={220} aria-label={`Marketing's budget and forecast, legend ${placement ?? "above"}`}>
       <XAxis value="month" categoryLabel={monthName} />
       <YAxis label="€" />
       <Line value="budget" name="Budget" />
@@ -10118,7 +10397,7 @@ export default function Benchmark() {
       >
         <Chart
           height={320}
-          ariaLabel="Benchmark with three series"
+          aria-label="Benchmark with three series"
           onPerf={onPerf}
         >
           <XAxis value={matrix ? "c" : "t"} label="Index" domain="data" zoomable />
@@ -10265,7 +10544,7 @@ export default function WeekOfSeconds() {
           <dd>{drawMs.toFixed(1)} ms</dd>
         </div>
       </dl>
-      <Chart height={300} ariaLabel="Search latency and requests over last week, a reading a second" onPerf={onPerf}>
+      <Chart height={300} aria-label="Search latency and requests over last week, a reading a second" onPerf={onPerf}>
         <XAxis value="t" time domain="data" zoomable />
         <YAxis label="ms" domain="visible" />
         <YAxis id="requests" position="right" label="Requests/min" domain="visible" />
@@ -10298,12 +10577,6 @@ From `ChartProps` — the full table stands on [Chart](#chart-1).
 |---|---|---|---|
 | [`onPerf`](#chart-1) | `(perf: `[`ChartPerf`](#chart-1)`) => void` | — | Instrumentation for the benchmark page; not needed otherwise. |
 
-###### Accessibility
-
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| [`ariaLabel`](#chart-1) | `string` | — | Required in DEV through a warning. |
-
 From `XAxisProps` — the full table stands on [Axis](#axis).
 
 | Prop | Type | Default | Description |
@@ -10825,7 +11098,7 @@ An `Area` as the chart holds it once registered.
 | `xAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `yAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `name` | `string` | — |  From `SeriesBase`. |
-| `format` | `(value: number) => string` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. From `SeriesBase`. |
+| `format` | `ValueFormat` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. Or `NumberOptions`: Intl's options in the wording's locale, compared by value. From `SeriesBase`. |
 | `color` | `string` | — |  From `SeriesBase`. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value: the theme resolves it, in both themes. For series that mean something rather than just being the next one - the violating points of a control chart, say. `color` beats it. From `SeriesBase`. |
 | `stack` | `string` | — | The stack this series stands in: series with the same id, on the same x and y axis, stack in registration order. From `Stackable`. |
@@ -10854,7 +11127,7 @@ An `XAxis` or `YAxis` as the chart holds it once registered.
 | `accessor` | `(d: T, index: number) => ``AxisValue` | — | Where a row lies along the axis; an x axis' only - along y the series place their rows. A number is a position or an instant, a string a category, a `Date` an instant ([ADR-0052](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0052-a-chart-reads-its-rows-as-they-come.md)). |
 | `label` | `string` | — |  |
 | `tickCount` | `number` | — |  |
-| `tickFormat` | `(v: number) => string` | — |  |
+| `tickFormat` | `ValueFormat` | — |  |
 | `domain` *required* | `"nice" \| "data" \| "visible" \| readonly [number, number]` | — | "visible" is a y axis' only: the extent of what its series show inside their x axis' domain. |
 | `grid` | `boolean` | only the first registered axis per orientation | Whether the axis draws its grid lines. |
 | `ticks` | `readonly number[]` | — | Fixed tick values instead of the 1-2-5 algorithm, on a numeric axis: an hour axis' named hours, a lane grid. |
@@ -10935,7 +11208,7 @@ A `Bar` as the chart holds it once registered.
 | `xAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `yAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `name` | `string` | — |  From `SeriesBase`. |
-| `format` | `(value: number) => string` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. From `SeriesBase`. |
+| `format` | `ValueFormat` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. Or `NumberOptions`: Intl's options in the wording's locale, compared by value. From `SeriesBase`. |
 | `color` | `string` | — |  From `SeriesBase`. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value: the theme resolves it, in both themes. For series that mean something rather than just being the next one - the violating points of a control chart, say. `color` beats it. From `SeriesBase`. |
 | `stack` | `string` | — | The stack this series stands in: series with the same id, on the same x and y axis, stack in registration order. From `Stackable`. |
@@ -11030,7 +11303,7 @@ chose - the library draws them and computes none.
 | `xAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `yAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `name` | `string` | — |  From `SeriesBase`. |
-| `format` | `(value: number) => string` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. From `SeriesBase`. |
+| `format` | `ValueFormat` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. Or `NumberOptions`: Intl's options in the wording's locale, compared by value. From `SeriesBase`. |
 | `color` | `string` | — |  From `SeriesBase`. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value: the theme resolves it, in both themes. For series that mean something rather than just being the next one - the violating points of a control chart, say. `color` beats it. From `SeriesBase`. |
 
@@ -11055,12 +11328,12 @@ is typed by that `data` instead.
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `Chart` *required* | `(props: `[`ChartProps`](#chart-1)`) => ReactNode` | — | The chart over the hook's rows. One per `useChart`: it holds the view, and a second chart is a second call.<br>Shown in: [Draw a first chart (Installation)](#installation), [Size a chart by its container (Installation)](#installation), [Mix series kinds (Chart)](#chart-1) and 74 more |
-| `XAxis` *required* | `<T = Z>(props: `[`XAxisProps`](#axis)`<T>) => null` | — | An x axis reads the rows of every series bound to it: the hook's, or with `<XAxis<Row>>` those the series bring as their own `data`.<br>Shown in: [Draw a first chart (Installation)](#installation), [Size a chart by its container (Installation)](#installation), [Mix series kinds (Chart)](#chart-1) and 74 more |
-| `YAxis` *required* | `(props: `[`YAxisProps`](#axis)`) => null` | — | <br>Shown in: [Draw a first chart (Installation)](#installation), [Size a chart by its container (Installation)](#installation), [Mix series kinds (Chart)](#chart-1) and 74 more |
+| `Chart` *required* | `(props: `[`ChartProps`](#chart-1)`) => ReactNode` | — | The chart over the hook's rows. One per `useChart`: it holds the view, and a second chart is a second call.<br>Shown in: [Draw a first chart (Installation)](#installation), [Size a chart by its container (Installation)](#installation), [Mix series kinds (Chart)](#chart-1) and 75 more |
+| `XAxis` *required* | `<T = Z>(props: `[`XAxisProps`](#axis)`<T>) => null` | — | An x axis reads the rows of every series bound to it: the hook's, or with `<XAxis<Row>>` those the series bring as their own `data`.<br>Shown in: [Draw a first chart (Installation)](#installation), [Size a chart by its container (Installation)](#installation), [Mix series kinds (Chart)](#chart-1) and 75 more |
+| `YAxis` *required* | `(props: `[`YAxisProps`](#axis)`) => null` | — | <br>Shown in: [Draw a first chart (Installation)](#installation), [Size a chart by its container (Installation)](#installation), [Mix series kinds (Chart)](#chart-1) and 75 more |
 | `Line` *required* | `<T = Z>(props: `[`LineProps`](#line)`<T>) => null` | — | <br>Shown in: [Draw a first chart (Installation)](#installation), [Size a chart by its container (Installation)](#installation), [Mix series kinds (Chart)](#chart-1) and 47 more |
 | `Area` *required* | `<T = Z>(props: `[`AreaProps`](#area)`<T>) => null` | — | <br>Shown in: [Mix series kinds (Chart)](#chart-1), [Mark every kind (Chart)](#chart-1), [Bind every kind of series to a second axis (Axis)](#axis) and 5 more |
-| `Bar` *required* | `<T = Z>(props: `[`BarProps`](#bar)`<T>) => null` | — | <br>Shown in: [Mix series kinds (Chart)](#chart-1), [Mark every kind (Chart)](#chart-1), [Bind every kind of series to a second axis (Axis)](#axis) and 13 more |
+| `Bar` *required* | `<T = Z>(props: `[`BarProps`](#bar)`<T>) => null` | — | <br>Shown in: [Mix series kinds (Chart)](#chart-1), [Mark every kind (Chart)](#chart-1), [Bind every kind of series to a second axis (Axis)](#axis) and 14 more |
 | `Scatter` *required* | `<T = Z>(props: `[`ScatterProps`](#scatter)`<T>) => null` | — | <br>Shown in: [Mix series kinds (Chart)](#chart-1), [Mark every kind (Chart)](#chart-1), [Bind every kind of series to a second axis (Axis)](#axis) and 3 more |
 | `StateBand` *required* | `<T = Z>(props: `[`StateBandProps`](#stateband)`<T> & ``OneLane``) => null` | — | <br>Shown in: [Mark bands, limits and cells (Chart)](#chart-1), [One vehicle through the day (StateBand)](#stateband), [Lay a state under a course (StateBand)](#stateband) and 4 more |
 | `Matrix` *required* | `<T = Z>(props: `[`MatrixProps`](#matrix)`<T>) => null` | — | <br>Shown in: [Mark bands, limits and cells (Chart)](#chart-1), [Colour cells by their limits (Matrix)](#matrix), [Colour cells along a gradient (Matrix)](#matrix) and 1 more |
@@ -11311,7 +11584,7 @@ A `Line` as the chart holds it once registered.
 | `xAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `yAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `name` | `string` | — |  From `SeriesBase`. |
-| `format` | `(value: number) => string` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. From `SeriesBase`. |
+| `format` | `ValueFormat` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. Or `NumberOptions`: Intl's options in the wording's locale, compared by value. From `SeriesBase`. |
 | `color` | `string` | — |  From `SeriesBase`. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value: the theme resolves it, in both themes. For series that mean something rather than just being the next one - the violating points of a control chart, say. `color` beats it. From `SeriesBase`. |
 
@@ -11402,7 +11675,7 @@ series kind whose base accessor reads more than a number.
 | `xAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `yAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `name` | `string` | — |  From `SeriesBase`. |
-| `format` | `(value: number) => string` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. From `SeriesBase`. |
+| `format` | `ValueFormat` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. Or `NumberOptions`: Intl's options in the wording's locale, compared by value. From `SeriesBase`. |
 | `color` | `string` | — |  From `SeriesBase`. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value: the theme resolves it, in both themes. For series that mean something rather than just being the next one - the violating points of a control chart, say. `color` beats it. From `SeriesBase`. |
 
@@ -11418,6 +11691,17 @@ type NumberField<T> = NoInfer<
 >;
 ```
 
+##### `NumberOptions`
+
+The options of `Intl.NumberFormat`, plus `decimals` for a fixed number of
+places (minimum and maximum alike; an Intl digit option given beside it
+wins). The same shape as core's, declared here because the charts import
+nothing.
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| `decimals` | `number` | — |  |
+
 ##### `OneLane`
 
 A lane is named or given by its edges: the compiler refuses both at once.
@@ -11598,7 +11882,7 @@ A `Scatter` as the chart holds it once registered.
 | `xAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `yAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `name` | `string` | — |  From `SeriesBase`. |
-| `format` | `(value: number) => string` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. From `SeriesBase`. |
+| `format` | `ValueFormat` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. Or `NumberOptions`: Intl's options in the wording's locale, compared by value. From `SeriesBase`. |
 | `color` | `string` | — |  From `SeriesBase`. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value: the theme resolves it, in both themes. For series that mean something rather than just being the next one - the violating points of a control chart, say. `color` beats it. From `SeriesBase`. |
 
@@ -11614,7 +11898,7 @@ which axes it stands on, and how it is named and coloured.
 | `xAxisId` *required* | `string` | — |  |
 | `yAxisId` *required* | `string` | — |  |
 | `name` | `string` | — |  |
-| `format` | `(value: number) => string` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. |
+| `format` | `ValueFormat` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. Or `NumberOptions`: Intl's options in the wording's locale, compared by value. |
 | `color` | `string` | — |  |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value: the theme resolves it, in both themes. For series that mean something rather than just being the next one - the violating points of a control chart, say. `color` beats it. |
 
@@ -11691,7 +11975,7 @@ an index into `states`.
 | `xAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `yAxisId` *required* | `string` | — |  From `SeriesBase`. |
 | `name` | `string` | — |  From `SeriesBase`. |
-| `format` | `(value: number) => string` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. From `SeriesBase`. |
+| `format` | `ValueFormat` | — | The value in the tooltip; before the y axis' `tickFormat`. Compared by its source text, as an accessor is. Or `NumberOptions`: Intl's options in the wording's locale, compared by value. From `SeriesBase`. |
 | `color` | `string` | — |  From `SeriesBase`. |
 | `tone` | `"ok" \| "warning" \| "alarm"` | — | A role instead of a colour value: the theme resolves it, in both themes. For series that mean something rather than just being the next one - the violating points of a control chart, say. `color` beats it. From `SeriesBase`. |
 
@@ -11713,7 +11997,7 @@ A custom tooltip's `render` receives it.
 | Prop | Type | Default | Description |
 |---|---|---|---|
 | `xValue` *required* | `number` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) |
-| `points` *required* | `readonly ``TooltipPoint``<T>[]` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) |
+| `points` *required* | `readonly ``TooltipPoint``<T>[]` | — | <br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Write the tooltip yourself (Tooltip)](#tooltip), [Choose a hit (Tooltip)](#tooltip) and 1 more |
 | `xPx` *required* | `number` | — | Pixel position of the crosshair (snapped to the data point). |
 | `yPx` *required* | `number` | — | Pixel position of the primary hit. |
 
@@ -11729,7 +12013,7 @@ One hit per series in the tooltip.
 | `color` *required* | `string` | — |  |
 | `xValue` *required* | `number` | — | The point's x value on its own x axis - with several x axes it can differ from the hit's. |
 | `yValue` *required* | `number` | — | The point's y value; in a stack its own value, not its top - in a normalised stack its share in percent.<br>Shown in: [Fix the domain and name the ticks (Axis)](#axis), [Choose a hit (Tooltip)](#tooltip) |
-| `datum` *required* | `T` | — | <br>Shown in: [Write the tooltip yourself (Tooltip)](#tooltip) |
+| `datum` *required* | `T` | — | <br>Shown in: [Write the tooltip yourself (Tooltip)](#tooltip), [Drill down from a year to its days (Tooltip)](#tooltip) |
 | `index` *required* | `number` | — |  |
 | `level` | `number` | — | Only for the matrix: its level, out of the level channel. It stands here and not in yValue, because yValue is the position on the y axis - for a matrix therefore the row. Putting both into one field would be exactly the overloading [ADR-0011](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0011-named-channels-never-overloaded.md) is written against. |
 | `segment` | `{ from: number; to: number; label: string }` | — | Only for state series: the section being pointed at. A duration does not stand here - it is the difference of two numbers the entry already carries, and formatting it would presuppose knowing what the x axis means. The caller knows that, not this library. |
@@ -11748,6 +12032,17 @@ by its name, or a function, compared by its source text (`ValueFunction`).
 type Value<T> = NumberField<T> | ValueFunction<T>;
 ```
 
+##### `ValueFormat`
+
+A value format: a function, or Intl's options written in the chart's
+wording's locale.
+
+```ts
+type ValueFormat = ((value: number) => string) | NumberOptions;
+```
+
+Used on [Tooltip](#tooltip).
+
 ##### `ValueFunction<T>`
 
 A **value** computed from the row - the function form of `Value`.