@umriss-ui/schedule 0.43.0 → 0.44.0

package/docs/llms-full.md

@@ -1,4 +1,4 @@
-# @umriss-ui/schedule 0.43.0
+# @umriss-ui/schedule 0.44.0
 
 > React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.
 
@@ -967,6 +967,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 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)). The width is the host's. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -1426,7 +1432,7 @@ Under forced colours the plot paints itself in the system colours: the work in t
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `ref` | `Ref<HTMLDivElement> \| RefObject<``ScheduleHandle`` \| null> \| undefined` | — | Receives the root element. A ref to the deprecated `ScheduleHandle` still works for one more minor release: the element carries its three functions. |
+| `ref` | `Ref<HTMLDivElement> \| undefined` | — | Receives the root element. |
 | `height` | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 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)). The width is the host's.<br>Shown in: [A day of tours](#first-schedule), [Start from an empty plan](#first-schedule), [Plan a day in the machine shop](#first-schedule) and 80 more |
 | `laneHeight` | `number` | `44` | Height of one lane in pixels at the default font size of 16 px; the schedule multiplies it by the root font size over 16 px when that ratio is above 1, so lane names keep their room in a reader's larger font.<br>Shown in: [Scroll more lanes than fit (Lanes)](#lanes), [Measure a plan (Benchmark)](#benchmark) |
 | `headerWidth` | `number` | `160` | Width of the lane headers in pixels - at most 40 % of the schedule, so that on a phone the plot keeps the larger part.<br>Shown in: [What a lane header says (Lanes)](#lanes), [Scroll more lanes than fit (Lanes)](#lanes), [Group lanes under a head (Lane groups)](#lane-groups) and 1 more |
@@ -1454,20 +1460,15 @@ Under forced colours the plot paints itself in the system colours: the work in t
 | `onIntent` | `(intent: ``Intent``) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it.<br>Shown in: [Read a folded group (Lane groups)](#lane-groups), [Cut the nights out of the axis (Time axis and calendar)](#time-axis-and-calendar), [Plan work around someone's leave (Blocked time)](#blocked-time) and 18 more |
 | `onInteraction` | `(interaction: `[`ScheduleInteraction`](#interactions)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu.<br>Shown in: [Report what the pointer is on (Interactions)](#interactions), [Open a context menu (Interactions)](#interactions), [Show a detail panel instead (Tooltip)](#tooltip) and 3 more |
 
-Also takes every attribute of `<div>` – without `aria-label`, `children`.
-
-##### Types on this page
-
-###### `ScheduleHandle`
-
-What a schedule offers a caller imperatively: the arithmetic between a
-point on the screen and a time on a lane. Everything else is props.
+###### Accessibility
 
 | Prop | Type | Default | Description |
 |---|---|---|---|
-| `positionAt` *required* | `(clientX: number, clientY: number) => { time: number; lane: string \| null } \| null` | — | The time and the lane at a client point, or null outside the plot. |
-| `clientPointOf` *required* | `(time: number, lane?: string) => { x: number; y: number } \| null` | — | The client point of a time - on the middle of a lane where one is named - or null while the schedule is not on screen. |
-| `visibleDomain` *required* | `() => readonly [number, number]` | — | The visible span, as two wall-clock instants. |
+| `aria-label` *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38".<br>Shown in: [A day of tours](#first-schedule), [Start from an empty plan](#first-schedule), [Plan a day in the machine shop](#first-schedule) and 82 more |
+
+Also takes every attribute of `<div>` – without `aria-label`, `children`.
+
+##### Types on this page
 
 ###### `CalendarInput`
 
@@ -1665,11 +1666,11 @@ no subtask yet; the caller creates one, with its own identity, from
 
 #### Known limits
 
-- No dependency types, critical path or auto-scheduling: the application decides where work goes, the schedule shows the result and its findings ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.43.0/docs/adr/0032-what-umriss-is-not.md)).
+- No dependency types, critical path or auto-scheduling: the application decides where work goes, the schedule shows the result and its findings ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md)).
 - No milestones yet: a point in time on a lane has no mark of its own.
 - A dependency joins two subtasks of one task; dependencies across tasks are not yet possible.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Plan
 
@@ -2111,7 +2112,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 - A folded group shows no summary - no utilisation band, no bar spanning its work: a computed claim would look like a drawn fact ([ADR-0025](https://github.com/romanhaendler/umriss-ui/blob/main/docs/adr/0025-a-lane-group-is-structure-over-lanes-never-a-lane.md)).
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Subtasks
 
@@ -2425,6 +2426,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`label`](#first-schedule) | `(subtask: `[`Subtask`](#subtasks)`) => string` | — | What stands written in a bar: a function from a subtask to a line of text, or nothing for bars without text. The text is cut off with an ellipsis where the bar is too narrow for it and left out where even that would say nothing; a bar that began before the view keeps its text at the view's edge. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -2730,6 +2737,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`label`](#first-schedule) | `(subtask: `[`Subtask`](#subtasks)`) => string` | — | What stands written in a bar: a function from a subtask to a line of text, or nothing for bars without text. The text is cut off with an ellipsis where the bar is too narrow for it and left out where even that would say nothing; a bar that began before the view keeps its text at the view's edge. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -2907,6 +2920,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 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)). The width is the host's. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -2957,7 +2976,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - No stacked layout on request yet: an overlap is always drawn offset, as the finding it is.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Dependencies
 
@@ -3327,9 +3346,9 @@ type DependencyEnds = "dot" | "none";
 
 #### Known limits
 
-- Only finish-to-start within one task; no dependency types and no critical path ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.43.0/docs/adr/0032-what-umriss-is-not.md)).
+- Only finish-to-start within one task; no dependency types and no critical path ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.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/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Routes
 
@@ -3517,6 +3536,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`attach`](#first-schedule) | [`DependencyAttachment`](#first-schedule)<br>`"centre" \| "nearest"` | `"centre"` | Where a dependency's ends sit on their bars: the `"centre"` of both, or the `"nearest"` edge - which is the shortest line between two stops. Within one lane both mean the middle. A dependency may say otherwise for itself. It changes the picture and never a finding: whether a dependency is violated follows from its `leaves` and `arrives` alone. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -3851,6 +3876,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -4598,6 +4629,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`now`](#first-schedule) | `boolean \| number` | `false` | A line marking the present across the lanes: `true` follows the clock by the minute, an instant fixes it there. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -4725,6 +4762,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`zoomLimits`](#first-schedule) | [`ZoomLimits`](#first-schedule) | one hour to 28 days | The narrowest and widest time span zoom may reach, in milliseconds. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -4937,6 +4980,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`onSelectedTaskChange`](#first-schedule) | `(task: string \| null, subtask: string \| null) => void` | — | Called when a click selects a task or clears the selection, with the subtask that was clicked - null where the click was on a dependency or on nothing. It is called again when another subtask of the same task is clicked. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -5002,7 +5051,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - One task at a time: there is no multiple selection.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Interactions
 
@@ -6021,6 +6070,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 | [`height`](#first-schedule) | `number` | fills the frame, at least 400 px | Height in CSS pixels, both bands included, fixed. Left out, the schedule fills its frame - a stretched grid cell, a card the grid stretches, a container of definite height - and never goes below 400 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)). The width is the host's. |
 | [`children`](#first-schedule) | `ReactNode` | — | `Lane`, `Dependencies` and `Subtasks`, in the order they are to stand and be drawn. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -6078,7 +6133,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - Only the view is shared - the span and the folded groups, not the selection, the hover or the vertical scroll.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Functions on the hook
 
@@ -6263,6 +6318,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onInteraction`](#first-schedule) | `(interaction: `[`ScheduleInteraction`](#interactions)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -6530,7 +6591,7 @@ The keys of [First schedule](#first-schedule) apply here.
 
 - Overlapping work is marked, not packed into sub-lanes; stacked overlap is not built yet.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Editing
 
@@ -6827,6 +6888,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -6899,10 +6966,10 @@ From `Overlap` — the full table stands on [Findings as data](#findings-as-data
 
 #### Known limits
 
-- No undo: your application owns the data, and with it the history ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.43.0/docs/adr/0032-what-umriss-is-not.md)).
+- No undo: your application owns the data, and with it the history ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md)).
 - The keys move work in time only; a lane change needs the pointer.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Stretch, lead-in, lead-out
 
@@ -7017,6 +7084,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -7068,7 +7141,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - A main time never becomes shorter than one raster step, or a minute without a raster.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Snapping
 
@@ -7245,6 +7318,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -7432,6 +7511,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -7845,6 +7930,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -7909,7 +8000,7 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 - A rule that changes while a drag runs is noticed at the drop, not before.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ### Ripple
 
@@ -8126,6 +8217,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onIntent`](#first-schedule) | `(intent: `[`Intent`](#first-schedule)`) => void` | — | Called once per intent when a drag ends. The data changes only if the caller changes it. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -8188,10 +8285,10 @@ From `ScheduleView` — the full table stands on [View](#view).
 
 #### Known limits
 
-- No dependency types, slack or critical path: the schedule is no project-planning engine ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.43.0/docs/adr/0032-what-umriss-is-not.md)).
+- No dependency types, slack or critical path: the schedule is no project-planning engine ([ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md)).
 - A dependency joins subtasks of one task, so work of other tasks is never pushed.
 
-What umriss deliberately does not build, and why: [ADR-0032](https://github.com/romanhaendler/umriss-ui/blob/schedule-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/schedule-v0.44.0/docs/adr/0032-what-umriss-is-not.md).
 
 ## Measuring
 
@@ -8533,6 +8630,12 @@ From `ScheduleProps` — the full table stands on [First schedule](#first-schedu
 |---|---|---|---|
 | [`onInteraction`](#first-schedule) | `(interaction: `[`ScheduleInteraction`](#interactions)`) => void` | — | Click, context menu and hover, with what the pointer is on and where. While it is set, a right-click opens no browser menu. |
 
+###### Accessibility
+
+| Prop | Type | Default | Description |
+|---|---|---|---|
+| [`aria-label`](#first-schedule) *required* | `string` | — | What the schedule shows, for a screen reader: "Plan of week 38". |
+
 From `LaneProps` — the full table stands on [Lanes](#lanes).
 
 | Prop | Type | Default | Description |
@@ -8986,19 +9089,6 @@ the channel each one owns stands beside it.
 | `muted` *required* | `boolean` | — | `muted`: the SATURATION - the task colour mixed half into the surface, opaque and at full height. Another team's, another crew's. |
 | `open` *required* | `boolean` | — | `open`: the FADE, where the bar passes the edge of the view. It goes on past what is drawn. |
 
-##### `ScheduleHandle`
-
-What a schedule offers a caller imperatively: the arithmetic between a
-point on the screen and a time on a lane. Everything else is props.
-
-| Prop | Type | Default | Description |
-|---|---|---|---|
-| `positionAt` *required* | `(clientX: number, clientY: number) => { time: number; lane: string \| null } \| null` | — | The time and the lane at a client point, or null outside the plot. |
-| `clientPointOf` *required* | `(time: number, lane?: string) => { x: number; y: number } \| null` | — | The client point of a time - on the middle of a lane where one is named - or null while the schedule is not on screen. |
-| `visibleDomain` *required* | `() => readonly [number, number]` | — | The visible span, as two wall-clock instants. |
-
-*Deprecated* since 0.43 - use the functions on [`useSchedule`](#api-index-1)'s return.
-
 ##### `ScheduleHit`
 
 What a pointer is on.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@umriss-ui/schedule",
-  "version": "0.43.0",
+  "version": "0.44.0",
   "description": "React Gantt-style schedule for data-dense applications - work on lanes over time, with dependencies, blocked time, findings and controlled editing.",
   "license": "MIT",
   "author": "Roman Händler",
@@ -59,8 +59,8 @@
     }
   },
   "peerDependencies": {
-    "@umriss-ui/charts": "^0.43.0",
-    "@umriss-ui/core": "^0.43.0",
+    "@umriss-ui/charts": "^0.44.0",
+    "@umriss-ui/core": "^0.44.0",
     "react": ">=19",
     "react-dom": ">=19"
   },
@@ -76,8 +76,8 @@
     "typescript": "^5.6.3",
     "vite": "^6.0.0",
     "vite-plugin-dts": "^4.3.0",
-    "@umriss-ui/charts": "0.43.0",
-    "@umriss-ui/core": "0.43.0",
+    "@umriss-ui/charts": "0.44.0",
+    "@umriss-ui/core": "0.44.0",
     "@umriss-ui/demo": "0.0.0"
   },
   "scripts": {