@fusion.dev/helix 0.159.0 → 0.160.0

package/types/vue.d.ts

@@ -206,6 +206,7 @@ import type {
   HelixSelectedEvent,
   HelixSortEvent,
   HelixSortedEvent,
+  HelixClearEvent,
   HelixRejectEvent,
   HelixFacetEvent,
   HelixBeforeActivateEvent,
@@ -217,7 +218,6 @@ import type {
   HelixGraphSignalEvent,
   HelixGraphZoomEvent,
   HelixResizeEvent,
-  HelixClearEvent,
   HelixShortcutEvent,
   HelixActionEvent,
   HelixMapPartChangeEvent,
@@ -5924,6 +5924,9 @@ export type HelixDateInputHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixDateInputHelixBeforeOpenElementEvent =
   HelixDateInputElementEvent<HelixBeforeOpenEvent>;
+/** `helix-clear` event type */
+export type HelixDateInputHelixClearElementEvent =
+  HelixDateInputElementEvent<HelixClearEvent>;
 
 export type HelixDateInputVueProps = {
   /** What a row of segments reports when the field is required and every
@@ -5948,6 +5951,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   incompleteMessage?: (HelixDateInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "range-end-label"?: (HelixDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  rangeEndLabel?: (HelixDateInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "range-start-label"?: (HelixDateInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  rangeStartLabel?: (HelixDateInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -6112,32 +6127,48 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   valueMissingMessage?: (HelixDateInput["valueMissingMessage"]) | undefined;
-  /** What the browser may autofill here, as one of the platform's own tokens.
+  /** What the browser may autofill here, as one of the platform's own tokens,
+such as `bday`.
 
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all: hardcoding `off` here means a birthday or a
-postal code can never be filled in for a reader. */
+postal code can never be filled in for a reader. With `segmented`, a
+hidden native date input carries it, since no browser fills the segments. */
   autocomplete?: (HelixDateInput["autocomplete"]) | undefined;
-  /** The calendar the written date and the calendar's days are in: `gregory`,
-`buddhist`, `japanese`, `roc`, or `iso8601`.
-
-Absent is the locale's own where it is one of the five, and `gregory` for
-every other, as Date Picker's `calendar` is. The value is `YYYY-MM-DD` in
-every calendar, and a focused field is ISO in every calendar. In
-`segmented`, the segments are the Gregorian day, month, and year, in the
-order the locale writes them, or ISO order for `iso8601`. */
+  /** The calendar the written date, the segments, and the calendar's days are
+in: `gregory`, `buddhist`, `japanese`, `roc`, or `iso8601`, or a calendar
+with months of its own that Date Picker's `calendar` names, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`.
+
+Absent is the locale's own where its months are the Gregorian months, and
+`gregory` for every other, as Date Picker's `calendar` is. The value is
+`YYYY-MM-DD` in every calendar, and a focused text field is ISO in every
+calendar. In `segmented`, the segments are the day, month, and year as
+the calendar counts them, in the order the locale writes them: Mehr 14,
+1405 is month 7 and day 14 of 1405 under `persian`. Under the five with
+Gregorian months they are the Gregorian day, month, and year, or ISO order
+for `iso8601`. */
   calendar?: (HelixDateInput["calendar"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   "calendar-label"?: (HelixDateInput["calendarLabel"]) | undefined;
   /** The name of the calendar's grid of days, read by screen readers. */
   calendarLabel?: (HelixDateInput["calendarLabel"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  clearable?: (HelixDateInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "clear-label"?: (HelixDateInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  clearLabel?: (HelixDateInput["clearLabel"]) | undefined;
   /** How a date is written in the field: `short` through `full`, or ISO.
 
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -6159,8 +6190,9 @@ submits and what `min` and `max` compare against. */
 **The field renders when it is idle and holds the value when it is being
 edited.** A written date is a rendering, and a document being edited must
 not be a rendering of something else: `Intl.DateTimeFormat` formats and does
-not parse, so `4 August 2026` cannot be typed back, and writing a parser per
-locale is how a field ends up rejecting what it just displayed.
+not parse, so a rendering such as `Tuesday, August 4, 2026` is no text to
+edit. The field does read a date typed in the locale's order and digits as
+you leave it, which covers what a reader types.
 
 The way out is not to choose between the two but to separate them in time.
 Idle, the field shows `4 August 2026`, which is what a date is for reading.
@@ -6298,6 +6330,14 @@ the date.
 **The name goes in**, so a row of them is heard as which one each
 removes rather than as "Remove" said once per date. */
   removeLabel?: (HelixDateInput["removeLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  "selection-label"?: (HelixDateInput["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the dates chosen in the calendar, with
+`{kind}`, `{start}`, `{end}` and `{count}` filled in as Date Picker's
+`selection-label` says. */
+  selectionLabel?: (HelixDateInput["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, handed to the calendar this renders
@@ -6309,6 +6349,14 @@ platform's base. */
   "step-mismatch-message"?: (HelixDateInput["stepMismatchMessage"]) | undefined;
   /** The message shown when a date is not on `step`. */
   stepMismatchMessage?: (HelixDateInput["stepMismatchMessage"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  "time-zone"?: (HelixDateInput["timeZone"]) | undefined;
+  /** The time zone today is read in, such as `America/New_York`, handed to the
+calendar: the day marked today, and the month an empty field opens on.
+Empty is the reader's own. Dates are plain `YYYY-MM-DD` and carry no zone. */
+  timeZone?: (HelixDateInput["timeZone"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
   "trigger-label"?: (HelixDateInput["triggerLabel"]) | undefined;
   /** The name of the button that opens the calendar, read by screen readers. */
@@ -6317,6 +6365,12 @@ platform's base. */
   "unavailable-message"?: (HelixDateInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-dates` or `disable-days` bars a date. */
   unavailableMessage?: (HelixDateInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  "unreadable-message"?: (HelixDateInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no date, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`. */
+  unreadableMessage?: (HelixDateInput["unreadableMessage"]) | undefined;
   /** The name of the calendar's heading where it shows a page of years, with
 `{heading}` filled in. */
   "year-view-label"?: (HelixDateInput["yearViewLabel"]) | undefined;
@@ -6384,6 +6438,8 @@ export type HelixDateInputVueEvents = {
   "helix-before-close": HelixDateInputHelixBeforeCloseElementEvent;
   /** Fired before the calendar opens. Cancelable: call `preventDefault()` to keep it closed. */
   "helix-before-open": HelixDateInputHelixBeforeOpenElementEvent;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "helix-clear": HelixDateInputHelixClearElementEvent;
   /** Fired after the value changes. */
   input: HelixDateInputElementEvent;
 };
@@ -6453,14 +6509,16 @@ it is one of the five, such as `buddhist` for `th-TH` or `japanese` for
 `ja-JP-u-ca-japanese`, and `gregory` for every other, such as `persian`
 for `fa-IR`.
 
-`persian`, `hebrew`, `islamic-umalqura`, `islamic-civil`, `ethiopic`,
-`coptic`, and `indian` draw a calendar with months of its own, as React
-Aria's calendars do: each grid is one of that calendar's months, the
-Hebrew leap month and Ethiopia's five-day thirteenth month included, and
-Previous, Next and the page keys move by those months. `month` and
+`persian`, `hebrew`, `islamic`, `islamic-umalqura`, `islamic-civil`,
+`islamic-tbla`, `islamic-rgsa`, `ethiopic`, `ethioaa`, `coptic`,
+`indian`, `chinese`, and `dangi` draw a calendar with months of its own,
+as React Aria's calendars do: each grid is one of that calendar's months,
+the Hebrew and Chinese leap months and Ethiopia's five-day thirteenth
+month included, and Previous, Next and the page keys move by those
+months. With `max-view`, the months view shows that calendar's year, of
+twelve or thirteen months, and the years view its years. `month` and
 `helix-navigate` then name a month by its first day, `YYYY-MM-DD`. The
-heading stays text, as the months and years views are drawn in Gregorian
-months only. The value is `YYYY-MM-DD` in every calendar. */
+value is `YYYY-MM-DD` in every calendar. */
   calendar?: (HelixDatePicker["calendar"]) | undefined;
   /** The month to open on when `month` is not set. */
   "default-month"?: (HelixDatePicker["defaultMonth"]) | undefined;
@@ -6607,6 +6665,18 @@ else set needs. */
   readOnly?: (HelixDatePicker["readOnly"]) | undefined;
   /** Stops the form from submitting while no date is chosen. */
   required?: (HelixDatePicker["required"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  "selection-label"?: (HelixDatePicker["selectionLabel"]) | undefined;
+  /** What a screen reader hears about the chosen dates: the grid's
+description, said again whenever the dates change. `{kind}` is `date`,
+`start` while a range holds one end, `range`, or `dates` for `multiple`.
+`{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+many dates are chosen. */
+  selectionLabel?: (HelixDatePicker["selectionLabel"]) | undefined;
   /** How far apart the selectable dates are, in days.
 
 `<input type="date" step>`'s own unit, counted from `min` where there is
@@ -8178,12 +8248,14 @@ export type HelixFlexVueEvents = {};
 
 export type HelixFormatDateVueProps = {
   /** The calendar a date is written in: `gregory`, `buddhist`, `japanese`,
-`roc`, or `iso8601`, the calendars Date Picker and Date Input draw.
-
-Absent is the locale's own where it is one of the five, such as
-`buddhist` for `th-TH`, and `gregory` for every other, such as `persian`
-for `fa-IR`, so a date written here reads as the same date a Date Picker
-beside it shows. */
+`roc`, or `iso8601`, or a calendar with months of its own, such as
+`persian`, `hebrew`, `islamic-umalqura`, `ethiopic`, or `chinese`: every
+calendar Date Picker and Date Input draw.
+
+Absent is the locale's own where its months are the Gregorian months,
+such as `buddhist` for `th-TH`, and `gregory` for every other, such as
+`persian` for `fa-IR`, so a date written here reads as the same date a
+Date Picker beside it shows. Write `calendar="persian"` for Mehr 14, 1405. */
   calendar?: (HelixFormatDate["calendar"]) | undefined;
   /** The timestamp, in any format `Date` can parse.
 
@@ -8209,6 +8281,14 @@ browser may use either. */
   dateStyle?: (HelixFormatDate["dateStyle"]) | undefined;
   /** How the day of the month is written, where a date is shown. */
   day?: (HelixFormatDate["day"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  "day-period"?: (HelixFormatDate["dayPeriod"]) | undefined;
+  /** Writes the part of the day in words, such as "in the morning" or "at
+night", in its `long`, `short`, or `narrow` form, where `hour` is on a
+twelve-hour clock. */
+  dayPeriod?: (HelixFormatDate["dayPeriod"]) | undefined;
   /** Shows how long ago the timestamp was, in a compact form such as "3h", in
 place of the date.
 
@@ -8226,6 +8306,12 @@ Off by default, which draws the date as one run of text, as Shoelace and
 Web Awesome do. An `elapsed` or `relative` reading is one phrase either
 way. */
   fields?: (HelixFormatDate["fields"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  "fractional-second-digits"?: (HelixFormatDate["fractionalSecondDigits"]) | undefined;
+  /** How many digits of a fraction of a second to write after `second`: 1, 2,
+or 3, as in 09:41:07.250. */
+  fractionalSecondDigits?: (HelixFormatDate["fractionalSecondDigits"]) | undefined;
   /** Draws an `elapsed` or `relative` reading once and leaves it, where it
 would otherwise move on as it goes stale.
 
@@ -8288,9 +8374,13 @@ Empty is the runtime's own. */
 
 Empty is the runtime's own. */
   timeZone?: (HelixFormatDate["timeZone"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   "time-zone-name"?: (HelixFormatDate["timeZoneName"]) | undefined;
-  /** Shows the name of the time zone, in its `long` or `short` form. */
+  /** Shows the name of the time zone: `long` or `short`, as Pacific Daylight
+Time or PDT, `longOffset` or `shortOffset`, as GMT-07:00 or GMT-7, or
+`longGeneric` or `shortGeneric`, as Pacific Time or PT. */
   timeZoneName?: (HelixFormatDate["timeZoneName"]) | undefined;
   /** How the weekday is written, where one is shown. */
   weekday?: (HelixFormatDate["weekday"]) | undefined;
@@ -15693,6 +15783,14 @@ rather than a thumb sitting on nothing. */
 middle of the track, or `end` at `max`. Absent is `start`. A range fills
 between its thumbs and ignores it. */
   origin?: (HelixSlider["origin"]) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  "page-step"?: (HelixSlider["pageStep"] | `${number}`) | undefined;
+  /** How far Page Up and Page Down move a thumb, in the slider's own units, as
+React Aria's `pageSize` and Zag's `largeStep` do. Absent leaves the keys
+to the platform, which moves a tenth of the track. */
+  pageStep?: (HelixSlider["pageStep"]) | undefined;
   /** Adds a second thumb, so the value is a pair.
 
 The pair is one string, `"10,50"`, which is what `value` and
@@ -17757,6 +17855,9 @@ export type HelixTimeInputHelixBeforeCloseElementEvent =
 /** `helix-before-open` event type */
 export type HelixTimeInputHelixBeforeOpenElementEvent =
   HelixTimeInputElementEvent<HelixBeforeOpenEvent>;
+/** `helix-clear` event type */
+export type HelixTimeInputHelixClearElementEvent =
+  HelixTimeInputElementEvent<HelixClearEvent>;
 
 export type HelixTimeInputVueProps = {
   /** What a row of segments reports when the field is required and every
@@ -17781,6 +17882,18 @@ are not, where `bad-input-message` is not set. `{kind}` is `date` or
 are not, where `bad-input-message` is not set. `{kind}` is `date` or
 `time`. */
   incompleteMessage?: (HelixTimeInput["incompleteMessage"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  "range-end-label"?: (HelixTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's second date
+or time, after each segment's own name. */
+  rangeEndLabel?: (HelixTimeInput["rangeEndLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  "range-start-label"?: (HelixTimeInput["rangeStartLabel"]) | undefined;
+  /** What a screen reader hears before the segments of a range's first date
+or time, after each segment's own name: "month, Start, Stay". */
+  rangeStartLabel?: (HelixTimeInput["rangeStartLabel"]) | undefined;
   /** Whether the field is a row of segments, one for each part of the date or
 time, in place of a line of text.
 
@@ -17950,6 +18063,14 @@ the field and does not reach that one. */
 Empty leaves the attribute off, which is the browser's default and is what
 lets autofill work at all. */
   autocomplete?: (HelixTimeInput["autocomplete"]) | undefined;
+  /** Whether the field shows a button that empties it, as Input's `clearable`
+does. Shown only while the field holds something to clear and is neither
+disabled nor read-only. */
+  clearable?: (HelixTimeInput["clearable"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  "clear-label"?: (HelixTimeInput["clearLabel"]) | undefined;
+  /** The accessible name of the clear button, which shows only an icon. */
+  clearLabel?: (HelixTimeInput["clearLabel"]) | undefined;
   /** Times that cannot be chosen, as `HH:mm`, separated by commas or spaces.
 
 Handed to the list, which offers them as unavailable, and checked against
@@ -18053,6 +18174,12 @@ never something this element would refuse to read back. */
   "unavailable-message"?: (HelixTimeInput["unavailableMessage"]) | undefined;
   /** The message shown when `disable-times` bars a time. */
   unavailableMessage?: (HelixTimeInput["unavailableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  "unreadable-message"?: (HelixTimeInput["unreadableMessage"]) | undefined;
+  /** The message for text that is no time, where `bad-input-message` is not
+set. `{mode}` is `single`, `range`, or `multiple`, and `{shape}` is `HH:mm`, or `HH:mm:ss` with `seconds`. */
+  unreadableMessage?: (HelixTimeInput["unreadableMessage"]) | undefined;
   /** Whether the panel shows one list of times or a column for each part of the
 time.
 
@@ -18118,6 +18245,8 @@ export type HelixTimeInputVueEvents = {
   "helix-before-close": HelixTimeInputHelixBeforeCloseElementEvent;
   /** Fired before the list opens. Cancelable: canceling it keeps the list closed and leaves the decision to you. */
   "helix-before-open": HelixTimeInputHelixBeforeOpenElementEvent;
+  /** Fired after the clear button has emptied the field, after `input` and `change`. */
+  "helix-clear": HelixTimeInputHelixClearElementEvent;
   /** Fired after the value changes. */
   input: HelixTimeInputElementEvent;
 };
@@ -18726,6 +18855,18 @@ and this one was the English a form in another language still spoke in
 the bubble it raises on submit: `feedback` replaces the message under
 the field and does not reach that one. */
   valueMissingMessage?: (HelixToggleGroup["valueMissingMessage"]) | undefined;
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  "allow-empty-selection"?: (HelixToggleGroup["allowEmptySelection"]) | undefined;
+  /** Whether a press on the chosen item, or Space or Enter on it, takes it
+back so nothing is chosen, as React Aria's `ToggleButtonGroup` and
+Radix's `ToggleGroup` do in a single group. Absent, a single group always
+keeps its choice once it has one, as a radio group does. A multiple group
+releases a pressed item either way. */
+  allowEmptySelection?: (HelixToggleGroup["allowEmptySelection"]) | undefined;
   /** Where the group's label sits. `start` puts it on the track's line.
 
 Absent is above, which is what a field looks like and what almost every
@@ -21089,6 +21230,8 @@ export type CustomCssProperties = {
   "--date-picker-period-size"?: (string) | undefined;
   /** Band behind the days in a range. */
   "--date-picker-range-color"?: (string) | undefined;
+  /** Band behind the days a waiting range is drawn to, before its second end is chosen. */
+  "--date-picker-range-preview-color"?: (string) | undefined;
   /** Height of a week row. */
   "--date-picker-row-size"?: (string) | undefined;
   /** Fill behind a selected day. */

package/types/words.d.ts

@@ -65,8 +65,7 @@ declare module '@fusion.dev/helix-core' {
        */
       canceledLabel: Message
       /**
-       * The name of the clear button, read by screen readers. The button shows only
-       * an icon.
+       * The accessible name of the clear button, which shows only an icon.
        *
        * English: `Clear`
        */
@@ -552,6 +551,13 @@ declare module '@fusion.dev/helix-core' {
        * English: `Earlier years`
        */
       previousYearsLabel: Message
+      /**
+       * What a screen reader hears before the segments of a range's second date
+       * or time, after each segment's own name.
+       *
+       * English: `End`
+       */
+      rangeEndLabel: Message
       /**
        * The message shown when a range holds more than two dates.
        *
@@ -565,6 +571,13 @@ declare module '@fusion.dev/helix-core' {
        * English: `Choose a date on or before {max}.`
        */
       rangeOverflowMessage: Message
+      /**
+       * What a screen reader hears before the segments of a range's first date
+       * or time, after each segment's own name: "month, Start, Stay".
+       *
+       * English: `Start`
+       */
+      rangeStartLabel: Message
       /**
        * The message shown when a date is before `min`. `{min}` is replaced with
        * `min`, written the way the field writes dates.
@@ -810,6 +823,13 @@ declare module '@fusion.dev/helix-core' {
        * English: `Choose a date that is available.`
        */
       unavailableMessage: Message
+      /**
+       * The message for text that is no date, where `bad-input-message` is not
+       * set. `{mode}` is `single`, `range`, or `multiple`.
+       *
+       * English: `{mode, select, single {Enter a date as YYYY-MM-DD.} other {Enter dates as YYYY-MM-DD, separated by commas.}}`
+       */
+      unreadableMessage: Message
       /**
        * What a screen reader hears before an unread notification's text.
        *
@@ -1368,6 +1388,16 @@ declare module '@fusion.dev/helix-core' {
        * English: `Choose a date on or after {min}.`
        */
       rangeUnderflowMessage: Message
+      /**
+       * What a screen reader hears about the chosen dates: the grid's
+       * description, said again whenever the dates change. `{kind}` is `date`,
+       * `start` while a range holds one end, `range`, or `dates` for `multiple`.
+       * `{start}` and `{end}` are dates written in `locale`, and `{count}` is how
+       * many dates are chosen.
+       *
+       * English: `{kind, select, date {Selected date: {start}} start {Range starts {start}. Choose the day it ends.} range {Selected range: {start} to {end}} other {{count, plural, one {# date selected} other {# dates selected}}}}`
+       */
+      selectionLabel: Message
       /**
        * The validation message for a date that `step` skips.
        *