@ids-group-ltd/ids-design-system 0.12.2 → 0.13.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (139) hide show
  1. package/CHANGELOG.md +751 -6
  2. package/components.md +87 -2
  3. package/docs/agent/INDEX.md +11 -1
  4. package/docs/agent/charts/chart-colour-which-palette-a-chart-takes.md +9 -0
  5. package/docs/agent/charts/chart-frame-the-box-a-chart-draws-around-itself.md +12 -0
  6. package/docs/agent/charts/ds-bar-chart.md +15 -0
  7. package/docs/agent/charts/ds-column-chart.md +14 -0
  8. package/docs/agent/charts/ds-donut-chart.md +17 -0
  9. package/docs/agent/charts/ds-funnel-chart.md +16 -0
  10. package/docs/agent/charts/ds-line-chart.md +15 -0
  11. package/docs/agent/forms/ds-button.md +6 -2
  12. package/docs/agent/forms/ds-number-stepper.md +1 -0
  13. package/docs/agent/navigation/ds-sidenav-item.md +1 -0
  14. package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs +2 -2
  15. package/fesm2022/ids-group-ltd-ids-design-system-components-accordion.mjs.map +1 -1
  16. package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs +16 -14
  17. package/fesm2022/ids-group-ltd-ids-design-system-components-autocomplete.mjs.map +1 -1
  18. package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs +2 -2
  19. package/fesm2022/ids-group-ltd-ids-design-system-components-badge.mjs.map +1 -1
  20. package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.mjs +161 -0
  21. package/fesm2022/ids-group-ltd-ids-design-system-components-bar-chart.mjs.map +1 -0
  22. package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs +20 -21
  23. package/fesm2022/ids-group-ltd-ids-design-system-components-breadcrumbs.mjs.map +1 -1
  24. package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs +107 -40
  25. package/fesm2022/ids-group-ltd-ids-design-system-components-button.mjs.map +1 -1
  26. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs +43 -0
  27. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-legend.mjs.map +1 -0
  28. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs +197 -0
  29. package/fesm2022/ids-group-ltd-ids-design-system-components-chart-tooltip.mjs.map +1 -0
  30. package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs +10 -4
  31. package/fesm2022/ids-group-ltd-ids-design-system-components-checkbox.mjs.map +1 -1
  32. package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs +3 -2
  33. package/fesm2022/ids-group-ltd-ids-design-system-components-color-picker.mjs.map +1 -1
  34. package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs +173 -0
  35. package/fesm2022/ids-group-ltd-ids-design-system-components-column-chart.mjs.map +1 -0
  36. package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs +9 -6
  37. package/fesm2022/ids-group-ltd-ids-design-system-components-date-picker.mjs.map +1 -1
  38. package/fesm2022/ids-group-ltd-ids-design-system-components-donut-chart.mjs +299 -0
  39. package/fesm2022/ids-group-ltd-ids-design-system-components-donut-chart.mjs.map +1 -0
  40. package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs +2 -2
  41. package/fesm2022/ids-group-ltd-ids-design-system-components-dropzone.mjs.map +1 -1
  42. package/fesm2022/ids-group-ltd-ids-design-system-components-empty-state.mjs +2 -2
  43. package/fesm2022/ids-group-ltd-ids-design-system-components-empty-state.mjs.map +1 -1
  44. package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs +69 -17
  45. package/fesm2022/ids-group-ltd-ids-design-system-components-field-group.mjs.map +1 -1
  46. package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs +2 -2
  47. package/fesm2022/ids-group-ltd-ids-design-system-components-filter-bar.mjs.map +1 -1
  48. package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs +366 -0
  49. package/fesm2022/ids-group-ltd-ids-design-system-components-funnel-chart.mjs.map +1 -0
  50. package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs +12 -16
  51. package/fesm2022/ids-group-ltd-ids-design-system-components-input.mjs.map +1 -1
  52. package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs +631 -0
  53. package/fesm2022/ids-group-ltd-ids-design-system-components-line-chart.mjs.map +1 -0
  54. package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs +2 -2
  55. package/fesm2022/ids-group-ltd-ids-design-system-components-list.mjs.map +1 -1
  56. package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs +1 -1
  57. package/fesm2022/ids-group-ltd-ids-design-system-components-modal.mjs.map +1 -1
  58. package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs +3 -2
  59. package/fesm2022/ids-group-ltd-ids-design-system-components-multi-select.mjs.map +1 -1
  60. package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs +2 -2
  61. package/fesm2022/ids-group-ltd-ids-design-system-components-number-stepper.mjs.map +1 -1
  62. package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs +3 -2
  63. package/fesm2022/ids-group-ltd-ids-design-system-components-otp-input.mjs.map +1 -1
  64. package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs +2 -2
  65. package/fesm2022/ids-group-ltd-ids-design-system-components-pagination.mjs.map +1 -1
  66. package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs +14 -22
  67. package/fesm2022/ids-group-ltd-ids-design-system-components-radio-group.mjs.map +1 -1
  68. package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs +1 -0
  69. package/fesm2022/ids-group-ltd-ids-design-system-components-segmented.mjs.map +1 -1
  70. package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs +9 -6
  71. package/fesm2022/ids-group-ltd-ids-design-system-components-select.mjs.map +1 -1
  72. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs +2 -2
  73. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav-footer.mjs.map +1 -1
  74. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs +18 -7
  75. package/fesm2022/ids-group-ltd-ids-design-system-components-sidenav.mjs.map +1 -1
  76. package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs +1 -0
  77. package/fesm2022/ids-group-ltd-ids-design-system-components-slider.mjs.map +1 -1
  78. package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs +4 -3
  79. package/fesm2022/ids-group-ltd-ids-design-system-components-stat.mjs.map +1 -1
  80. package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs +10 -4
  81. package/fesm2022/ids-group-ltd-ids-design-system-components-switch.mjs.map +1 -1
  82. package/fesm2022/ids-group-ltd-ids-design-system-components-table-export.mjs +1 -1
  83. package/fesm2022/ids-group-ltd-ids-design-system-components-table-export.mjs.map +1 -1
  84. package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs +30 -71
  85. package/fesm2022/ids-group-ltd-ids-design-system-components-table.mjs.map +1 -1
  86. package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs +2 -2
  87. package/fesm2022/ids-group-ltd-ids-design-system-components-tag.mjs.map +1 -1
  88. package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs +3 -2
  89. package/fesm2022/ids-group-ltd-ids-design-system-components-textarea.mjs.map +1 -1
  90. package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs +3 -2
  91. package/fesm2022/ids-group-ltd-ids-design-system-components-time-picker.mjs.map +1 -1
  92. package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs +31 -9
  93. package/fesm2022/ids-group-ltd-ids-design-system-components-tooltip.mjs.map +1 -1
  94. package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs +2 -2
  95. package/fesm2022/ids-group-ltd-ids-design-system-components-tree.mjs.map +1 -1
  96. package/fesm2022/ids-group-ltd-ids-design-system-components.mjs +409 -5
  97. package/fesm2022/ids-group-ltd-ids-design-system-components.mjs.map +1 -1
  98. package/fesm2022/ids-group-ltd-ids-design-system-core.mjs +17 -1
  99. package/fesm2022/ids-group-ltd-ids-design-system-core.mjs.map +1 -1
  100. package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs +3 -0
  101. package/fesm2022/ids-group-ltd-ids-design-system-icons.mjs.map +1 -1
  102. package/fesm2022/ids-group-ltd-ids-design-system.mjs +10 -1
  103. package/fesm2022/ids-group-ltd-ids-design-system.mjs.map +1 -1
  104. package/migrations/0.12.3.json +83 -0
  105. package/migrations/0.13.0.json +530 -0
  106. package/package.json +57 -1
  107. package/styles/_chart-data-table.scss +95 -0
  108. package/styles/_chart-frame.scss +53 -0
  109. package/styles/_chart-interactive.scss +40 -0
  110. package/styles/_chart-motion.scss +45 -0
  111. package/styles/_control-line.scss +45 -0
  112. package/styles/_field-state.scss +14 -15
  113. package/styles/_focus.scss +31 -60
  114. package/styles/_tokens-charts.scss +149 -39
  115. package/styles/_tokens.scss +35 -31
  116. package/themes/dark/_theme.scss +37 -29
  117. package/types/ids-group-ltd-ids-design-system-components-autocomplete.d.ts +11 -9
  118. package/types/ids-group-ltd-ids-design-system-components-bar-chart.d.ts +104 -0
  119. package/types/ids-group-ltd-ids-design-system-components-breadcrumbs.d.ts +8 -17
  120. package/types/ids-group-ltd-ids-design-system-components-button.d.ts +60 -30
  121. package/types/ids-group-ltd-ids-design-system-components-chart-legend.d.ts +34 -0
  122. package/types/ids-group-ltd-ids-design-system-components-chart-tooltip.d.ts +78 -0
  123. package/types/ids-group-ltd-ids-design-system-components-checkbox.d.ts +6 -1
  124. package/types/ids-group-ltd-ids-design-system-components-column-chart.d.ts +105 -0
  125. package/types/ids-group-ltd-ids-design-system-components-date-picker.d.ts +4 -1
  126. package/types/ids-group-ltd-ids-design-system-components-donut-chart.d.ts +113 -0
  127. package/types/ids-group-ltd-ids-design-system-components-field-group.d.ts +52 -11
  128. package/types/ids-group-ltd-ids-design-system-components-funnel-chart.d.ts +109 -0
  129. package/types/ids-group-ltd-ids-design-system-components-input.d.ts +5 -7
  130. package/types/ids-group-ltd-ids-design-system-components-line-chart.d.ts +241 -0
  131. package/types/ids-group-ltd-ids-design-system-components-radio-group.d.ts +10 -10
  132. package/types/ids-group-ltd-ids-design-system-components-select.d.ts +5 -2
  133. package/types/ids-group-ltd-ids-design-system-components-sidenav.d.ts +16 -4
  134. package/types/ids-group-ltd-ids-design-system-components-switch.d.ts +6 -1
  135. package/types/ids-group-ltd-ids-design-system-components-table.d.ts +13 -28
  136. package/types/ids-group-ltd-ids-design-system-components-tooltip.d.ts +11 -1
  137. package/types/ids-group-ltd-ids-design-system-components.d.ts +163 -3
  138. package/types/ids-group-ltd-ids-design-system-core.d.ts +12 -1
  139. package/types/ids-group-ltd-ids-design-system.d.ts +9 -2
package/CHANGELOG.md CHANGED
@@ -1,12 +1,757 @@
1
- # Changelog
1
+ ## Unreleased
2
2
 
3
- All notable changes to `@ids-group-ltd/ids-design-system` are documented here.
3
+ ## 0.13.0 — 2026-09-14
4
4
 
5
- Versioning follows [SemVer](https://semver.org). Mapping from commit types:
6
- `fix` → patch, `feat` → minor, breaking change (API or visual) → major.
7
- While the package is on `0.x`, minor releases may contain breaking changes.
5
+ ### Breaking
8
6
 
9
- ## Unreleased
7
+ - **`ds-field-group` renders its chrome on an inner row, not on the host.** The border, radius,
8
+ focus ring and the divider between segments moved from `:host` to `.row`, because the group now
9
+ carries a message of its own and that line has to sit OUTSIDE the bordered box. A stylesheet that
10
+ reached `ds-field-group` to change its border, radius or padding now targets a box that no longer
11
+ has them.
12
+
13
+ ```scss
14
+ /* before */ /* after — or better, use the tokens */
15
+ ds-field-group { border: 0; } ds-field-group .row { border: 0; }
16
+ ```
17
+
18
+ Every `--ds-field-group-*` token is unchanged and still declared on the host, so an override
19
+ written through the tokens needs nothing. The host's own box is unchanged too while the group has
20
+ no message: measured in the docs app, the row stays 40px and the host stays 40px — it grows to
21
+ 57px only once `error` or `hint` is bound.
22
+
23
+ - **`--ds-button-border` is `--ds-button-border-color`, and `--ds-button-border-disabled` is
24
+ `--ds-button-border-color-disabled`.** Both name a COLOUR, and since the width moved out to
25
+ `--ds-button-border-width` beside them the old names read like a `border` shorthand — set
26
+ `2px solid red` on one and nothing happens. The values and defaults are unchanged; only the
27
+ names moved.
28
+
29
+ ```scss
30
+ /* before */ /* after */
31
+ ds-button { ds-button {
32
+ --ds-button-border: var(--brand); --ds-button-border-color: var(--brand);
33
+ } }
34
+ ```
35
+
36
+ - **A `ds-button`, `ds-sidenav-item` or `ds-sidenav-group` link no longer claims to be a page it
37
+ is only inside of.** `aria-current` was derived from `routerLinkActive`, which matches by
38
+ PREFIX — so a "back to the section" link on `/case-studies/retail` announced
39
+ `aria-current="page"` for `/case-studies`, a page the reader was leaving rather than on. It now
40
+ says what ARIA means: an exact match announces `page`, a prefix match announces `true`, anything
41
+ else announces nothing. The `active` CLASS still matches by prefix, so nothing changes visually.
42
+
43
+ Only a screen reader hears the difference, which is why it went unnoticed for so long — on
44
+ `ds-button` the `active` class is painted by nothing at all. If a test asserted
45
+ `aria-current="page"` on a section link, it now reads `true`.
46
+
47
+ - **Thirty-one chart palette tokens are renamed, and an override written against an old name
48
+ stops applying in silence.** A custom property that no longer resolves is invalid at
49
+ computed-value time, so the whole declaration around it is dropped: `background:
50
+ var(--chart-cat-3)` paints nothing, a `:root` override of `--chart-cat-3` simply never reaches
51
+ the chart, and neither reports an error. Five groups:
52
+
53
+ - Categorical series — `--chart-cat-1` … `--chart-cat-8` become `--chart-categorical-1` …
54
+ `--chart-categorical-8`.
55
+ - Sequential ramp — `--chart-seq-1` … `--chart-seq-6` become `--chart-sequential-1` …
56
+ `--chart-sequential-6`.
57
+ - Divergent ramp — `--chart-div--3` … `--chart-div-3` become `--chart-divergent--3` …
58
+ `--chart-divergent-3`, signed suffix and all.
59
+ - Colours taking the `-color` the rest of the library carries — `--chart-axis-line`,
60
+ `--chart-axis-label`, `--chart-grid-line`, `--chart-cursor-line` and `--chart-tooltip-border`.
61
+ - Abbreviations spelled out — `--chart-axis-fs` becomes `--chart-axis-font-size`,
62
+ `--chart-line-w` becomes `--chart-line-width`, `--chart-line-w-bold` becomes
63
+ `--chart-line-width-bold`, `--chart-dot-r` becomes `--chart-dot-radius`, and
64
+ `--chart-dot-r-active` becomes `--chart-dot-radius-active`.
65
+
66
+ Three more are REMOVED rather than renamed, because no chart draws what they named and the
67
+ `--ds-chart-*` token each fed reached no rule: `--chart-axis-title`, `--chart-grid-line-strong`
68
+ and `--chart-tick-size`. Handle `--chart-grid-line-strong` before `--chart-grid-line`: the short
69
+ name is a prefix of the long one, and a prefix-blind sweep renames this one instead of deleting
70
+ it.
71
+
72
+ The sequential and divergent VALUES are unchanged in both themes; the eight categorical values are
73
+ not — they are retuned in this same release, so a rename there lands a different colour rather than
74
+ the same one under a new name. `--chart-bar-gap`, `--chart-hover-bg-color`, `--chart-tooltip-bg-color` and
75
+ `--chart-tooltip-text-color` keep their names. Recolouring a series
76
+ is better done through the `--ds-chart-` layer below than through the palette.
77
+
78
+ - **`DsFieldGroupContext` carries two more members, and a class that IMPLEMENTS it no longer
79
+ compiles.** The interface behind `DS_FIELD_GROUP` had one member, `sizeResolved`; it now also
80
+ declares `invalidResolved: () => boolean` and `messageId: () => string | null`, because a segment
81
+ has to read the group's RESOLVED error state — an `error` string counts, not only the `invalid`
82
+ flag — and has to add the group's one message to its own `aria-describedby`. Anyone who provides
83
+ `DS_FIELD_GROUP` from their own wrapper so that DS fields behave as segments inside it gets
84
+ TS2420 until both are supplied: a compile error, not a silent change.
85
+
86
+ ```ts
87
+ providers: [{ provide: DS_FIELD_GROUP, useValue: {
88
+ sizeResolved: () => 'md',
89
+ invalidResolved: () => this.invalid(),
90
+ messageId: () => this.messageId(),
91
+ } satisfies DsFieldGroupContext }]
92
+ ```
93
+
94
+ `() => false` and `() => null` reproduce the old behaviour exactly. Only a consumer who PROVIDES
95
+ the token is affected; injecting it to read the context is unchanged and gains two members.
96
+
97
+ - **`TableRowAction.label` is `string | ((row: T) => string)`, which breaks code that READS it.**
98
+ Writing an action is unaffected — a plain string still compiles. But `rowActionSelected` hands
99
+ back the action, and `event.action.label` is now a union: assigning it to a `string`, or calling
100
+ a string method on it, is a compile error rather than a silent wrong value.
101
+
102
+ ```ts
103
+ const label = typeof event.action.label === 'string'
104
+ ? event.action.label
105
+ : event.action.label(event.row);
106
+ ```
107
+
108
+ Branch on `event.action.id` instead wherever the label was only standing in for the identity —
109
+ that is what `id` is for, and it stayed a `string`.
110
+
111
+ - **A `ds-stat` label clips to one line.** It wrapped freely before, so a two-word label took two
112
+ lines and made its tile taller than the ones beside it; it now truncates with an ellipsis and
113
+ discloses the full text in a tooltip on hover. There is no hook to put the wrapping back — the
114
+ value's `--ds-stat-value-white-space`, `--ds-stat-value-lines` and `--ds-stat-value-wrap` govern
115
+ the value alone. A label that was relying on two lines needs shortening, or a wider tile.
116
+
117
+ ### Added
118
+
119
+ - **`LineChartPoint` is exported.** `(pointClicked)` on `ds-line-chart` has always emitted it, and
120
+ the type was reachable from nowhere — a consumer typing the handler had to restate the shape by
121
+ hand.
122
+
123
+ - **The focus ring on a chart mark is two tones, and it is drawn rather than outlined.** A white
124
+ stroke with a dark halo around it, because one tone is not enough: an accent ring disappears on a
125
+ mark of its own hue family, and a chart's marks are exactly the surfaces a ring has to survive.
126
+ Measured in Chrome on 2026-09-14, WCAG contrast against each of the eight categorical colours:
127
+ the white stroke runs 3.01 – 9.45 and the halo 1.83 – 5.75, so every series colour clears 3:1
128
+ against at least one tone, and the halo clears 17.32 against the chart's own surface.
129
+ `--ds-chart-focus-ring-color` and `--ds-chart-focus-halo-color` are the hooks.
130
+
131
+ `outline` is not the mechanism because on an SVG element it paints the BOUNDING BOX rather than
132
+ the silhouette — a donut slice would ring as a rectangle.
133
+
134
+ **Forced colours are handled explicitly.** `fill` and `stroke` are not remapped by Windows High
135
+ Contrast, so a chart keeps every series colour, they all resolve to the same one against the
136
+ forced background, and nothing reports a problem. Axes, gridlines and labels now take `CanvasText`
137
+ and the focus ring takes `Highlight` under `(forced-colors: active)`.
138
+
139
+ - **`ds-line-chart` takes `patterns`, a second encoding channel.** Each series gets a dash of its
140
+ own from a fixed list, in the same order as the palette slots, so the lines are told apart by
141
+ shape as well as by colour — WCAG technique G111. Slot 1 stays solid, so a single-series chart is
142
+ unchanged by turning it on. Off by default: the shipped palette clears the colour-blind
143
+ separation threshold on its own, and this is for monochrome print, a retuned palette, or a reader
144
+ who asks for it.
145
+
146
+ ```html
147
+ <ds-line-chart patterns [series]="series" [categories]="months" />
148
+ ```
149
+
150
+ The other four charts print a label beside every mark already — a bar's row, a column's category,
151
+ a donut's legend row, a funnel's stage — so colour is not what identifies a mark there.
152
+
153
+ - **A tap answers the way a hover does, and stays put.** Tapping a mark opens its tooltip and
154
+ LATCHES it: a touch fires `pointerleave` the instant the finger lifts, so without this the panel
155
+ would flash and vanish. The next tap outside the mark releases it. On `ds-line-chart` a tap
156
+ anywhere in the plot picks the category under the finger, the same as a pointer moving over it.
157
+
158
+ `ds-line-chart`'s markers carry a hit area rather than relying on the dot: a transparent
159
+ `non-scaling-stroke` of 24px on a fine pointer and 44px under `(pointer: coarse)`. Measured in
160
+ Chrome at a 390px viewport: the marker hit-tests 21px from its centre and misses at 25px, so the
161
+ touch target is 44px across whatever width the plot is scaled to — a stroke in viewBox units
162
+ would have been a different size on a narrow card than on a wide one. It is narrower on a fine
163
+ pointer because a 44px target on a dense chart swallows the neighbouring readings.
164
+
165
+ - **A mark that arrives and a mark that leaves are now two staged phases.** Removals run first, at
166
+ `--ds-motion-chart-mark-exit-duration`; additions wait that long and then run at
167
+ `--ds-motion-chart-mark-enter-duration`, so a vanishing mark and an arriving one are never on
168
+ screen together. The update phase — a mark changing size — is unchanged and still runs on
169
+ `--ds-motion-chart-mark-duration`.
170
+
171
+ `staggerMs` spaces the arrivals out on all five charts. `0` is the default and means no stagger;
172
+ `40` is the documented step, and the total delay is capped at 300ms so a hundred-mark series does
173
+ not take three seconds to appear. Measured on the docs card at `staggerMs="40"`: five columns
174
+ resolve to 0, 40, 80, 120 and 160ms.
175
+
176
+ ```html
177
+ <ds-column-chart staggerMs="40" [data]="points" />
178
+ ```
179
+
180
+ Every transition retargets rather than queues: a data change mid-animation continues from where
181
+ the mark actually is. Measured on the column chart's docs card — a bar caught at 163.4px when the
182
+ second change landed carried on to 169.6px, with no jump back to the first target.
183
+
184
+ `prefers-reduced-motion` needs nothing from the charts. The durations are tokens, the library's
185
+ global rule already zeroes them, and each mark then lands straight on its final size — measured
186
+ with the tokens zeroed: `animation-duration: 0s`, `animation-delay: 0s`, `opacity: 1`,
187
+ `transform: none`.
188
+
189
+ - **`ds-line-chart`'s legend can switch a series off.** `legendFilters` turns each entry into a
190
+ real `<input type="checkbox">` — keyboard-operable and correctly announced without inventing a
191
+ role — and `hiddenSeries` is a two-way `model`, so a page can drive the filter from a URL
192
+ parameter and read back what the reader chose. Hovering or focusing an entry dims every other
193
+ series to `--ds-chart-dim-opacity`.
194
+
195
+ ```html
196
+ <ds-line-chart
197
+ legendFilters
198
+ [(hiddenSeries)]="hidden"
199
+ [series]="series"
200
+ [categories]="months" />
201
+ ```
202
+
203
+ **The value axis does not move when a series is hidden.** `rescaleOnHide` opts into the other
204
+ behaviour, and it is off by default because a silent rescale turns a period-over-period
205
+ comparison into a different claim — measured on the docs card, hiding one series with the
206
+ default leaves the axis at `0 … 5K`, and with `rescaleOnHide` it becomes `0 … 1.6K`.
207
+
208
+ Switching every series off replaces the plot with `noVisibleSeriesText` — "All series are
209
+ hidden" by default — carried on a `role="status"` line, with the legend still rendered so the
210
+ reader can switch one back on. Without it the reader is left looking at an empty grid.
211
+
212
+ A legend without a filter is unchanged: `ds-line-chart` still draws one whenever there is more
213
+ than one series, and it is now `ds-chart-legend` rather than markup of its own.
214
+
215
+ - **Every chart answers a hover, a tap and a keyboard focus with a tooltip.** `ds-bar-chart`,
216
+ `ds-column-chart`, `ds-donut-chart` and `ds-funnel-chart` default to `tooltip="item"` — the mark
217
+ under the pointer, or the one holding focus. `ds-line-chart` defaults to `tooltip="axis"`: a
218
+ pointer names every series at the category under it, while tabbing to a marker names that series
219
+ alone, because focus is already on one reading. `tooltip="none"` turns it off.
220
+
221
+ The panel is portaled out of the chart's box, so a chart inside a small dashboard card is not
222
+ what clips it — with no room above the mark it flips below, then to either side, and is pushed
223
+ back on screen rather than cut. On a coarse pointer it clears the tap point by 48px instead of
224
+ 12, so the panel is not under the finger.
225
+
226
+ ```html
227
+ <ds-line-chart [series]="series" [categories]="months" tooltip="axis" />
228
+ <ds-donut-chart [data]="slices" tooltip="none" />
229
+ ```
230
+
231
+ The content is a projected template, never a formatter string, so a tooltip can hold components
232
+ and markup rather than escaped text:
233
+
234
+ ```html
235
+ <ds-column-chart [data]="points">
236
+ <ng-template #dsChartTooltip let-tip>
237
+ <strong>{{ tip.category }}</strong>
238
+ @for (entry of tip.entries; track entry.label) {
239
+ <p>{{ entry.label }}: {{ entry.formatted }}</p>
240
+ }
241
+ </ng-template>
242
+ </ds-column-chart>
243
+ ```
244
+
245
+ Three tokens paint it — `--ds-chart-tooltip-bg-color`, `--ds-chart-tooltip-text-color` and
246
+ `--ds-chart-tooltip-border-color`. They were declared before this and reached no rule; they reach
247
+ one now. The panel carries `aria-hidden`, because every interactive mark already puts the same
248
+ label and value in its own accessible name and a screen reader would otherwise read each reading
249
+ twice.
250
+
251
+ - **Hovering or focusing one mark dims the others.** With `interactive` set on `ds-bar-chart`,
252
+ `ds-column-chart`, `ds-donut-chart` or `ds-funnel-chart`, the mark under the pointer or under
253
+ focus keeps its colour and every other mark drops to `--ds-chart-dim-opacity`, default `0.3` —
254
+ the highlight is a fade of the rest rather than a change to the thing being pointed at, so the
255
+ colour a reader is matching against the legend stays the colour it was. Without `interactive`
256
+ nothing dims: a chart nobody can click has no mark to single out.
257
+
258
+ ```scss
259
+ /* a denser chart wants a deeper fade */
260
+ ds-donut-chart { --ds-chart-dim-opacity: 0.15; }
261
+ ```
262
+
263
+ The fade runs on `--ds-motion-chart-state-duration` and `--ds-motion-chart-state-easing`, so a
264
+ consumer who slows or flattens chart state changes does it in one place for all four. Reduced
265
+ motion needs nothing from the chart — the library's global rule already zeroes every duration.
266
+
267
+ - **`ds-number-stepper` takes `--ds-number-stepper-field-width`.** The number between the two step
268
+ buttons is sized from the control's own box height — 1.25× it — which is right for two or three
269
+ digits and clips a five-digit quantity. The hook is that width, and the default is the value the
270
+ three sizes carried before, so nothing moved.
271
+
272
+ ```scss
273
+ ds-number-stepper { --ds-number-stepper-field-width: 5ch; }
274
+ ```
275
+
276
+ - **`ds-line-chart` highlights the category under the pointer.** A line has no mark between two
277
+ readings, so the hover target is the whole category: a band paints behind the plot and every
278
+ series' reading at that category grows to the active dot radius. The band is what survives a
279
+ finger covering it on touch, and the grown markers are what the tooltip will anchor to.
280
+ `--ds-chart-hover-bg-color` paints the band, `--ds-chart-cursor-line-color` the rule down its
281
+ centre and `--ds-chart-dot-radius-active` sizes the grown reading; all three were declared and
282
+ reached no rule until now. `--ds-line-chart-hover-bg-color`, `--ds-line-chart-cursor-line-color`
283
+ and `--ds-line-chart-dot-radius-active` override any of them for this chart alone. The band is
284
+ what survives a finger covering it, which a 1px rule on its own does not.
285
+
286
+ - **Every chart takes `error` and `errorText`.** A failed fetch had to render as `emptyText`, which
287
+ says "No data" when the truth is "could not load". The branch renders ahead of `loading` and
288
+ carries `role="status"`, so the message is announced when it replaces a spinner.
289
+
290
+ ```html
291
+ <ds-bar-chart
292
+ [data]="rows"
293
+ [loading]="pending()"
294
+ [error]="failed()"
295
+ errorText="Could not reach the depot service" />
296
+ ```
297
+
298
+ - **`BarChartRow` and `ColumnChartPoint` take an optional `id`.** Supplying it makes a reorder move
299
+ the DOM nodes instead of rewriting them; left out, the row keeps its position as its key, which is
300
+ what both charts did before. `DonutChartSlice` and `FunnelChartStage` already required one.
301
+
302
+ - **`ds-line-chart` takes `interactive` and emits `pointClicked`.** Every reading becomes a focusable
303
+ button carrying its series, its category and its value, so a click and a keyboard activation reach
304
+ the consumer the same way they already do on `ds-bar-chart`. A series drawn with
305
+ `showMarkers="false"` grows invisible markers when `interactive` is set, so there is something to
306
+ land on; they appear on hover and on focus.
307
+
308
+ ```html
309
+ <ds-line-chart
310
+ interactive
311
+ [series]="series"
312
+ [categories]="months"
313
+ (pointClicked)="openMonth($event)" />
314
+ ```
315
+
316
+ - **A `TableRowAction` can name itself per row, and can open a divider.** `label` takes
317
+ `(row) => string` as well as a string, so one action reads Pause on a live row and Resume on a
318
+ paused one under the SAME `id` — `rowActionSelected` still fires once with that id, instead of the
319
+ consumer declaring two actions whose `hidden` predicates have to be kept exact opposites by hand.
320
+ `divider: true` draws a line above an item, for the destructive tail that colour alone was
321
+ separating.
322
+
323
+ ```ts
324
+ rowActions: TableRowAction<Run>[] = [
325
+ { id: 'suspend', label: (row) => (row.active ? 'Pause' : 'Resume'), icon: 'refresh' },
326
+ { id: 'delete', label: 'Delete', icon: 'trash', error: true, divider: true },
327
+ ];
328
+ ```
329
+
330
+ A divider on the FIRST item is ignored: a line at the top of a menu has nothing on one side of it.
331
+ Measured in the docs app across four rows — the label reads Pause on the active row and Resume on
332
+ the other three, and every menu renders exactly one divider, in document order between the last
333
+ ordinary item and Delete.
334
+
335
+ These are the last two of the four pieces asked for on 2026-08-18; `hidden` and `disabledReason`
336
+ shipped on 2026-08-21.
337
+
338
+
339
+ - **`ds-field-group` takes `error`, `hint` and `warning`, so the error it shows has words.** The
340
+ group suppresses its segments' own labels and message rows — they would break the glued line — and
341
+ until now it had nowhere for the text to go, which left colour as the only channel and 1.4.1
342
+ failing. It carries the same pair every field carries: `error` is a string that turns the state on
343
+ AND says what is wrong, `invalid` stays the flag for when the text lives in a form-level summary.
344
+
345
+ ```html
346
+ <ds-field-group error="Введите сумму больше нуля">
347
+ <ds-select [options]="currencies" />
348
+ <ds-input grow [(value)]="amount" />
349
+ </ds-field-group>
350
+ ```
351
+
352
+ It takes the rest of that base too: `reserveMessage` holds the message row's height while the
353
+ group is clean, so binding an error later does not push the form below it down, and
354
+ `messageIcon` overrides the glyph the state resolves to, or removes it with `false`.
355
+
356
+ **Every segment announces it, not just the first.** Each carries `aria-invalid` while the group is
357
+ in error and points at the one message through `aria-describedby`, so a reader who tabs straight to
358
+ the second segment hears it too — the group's border is not something a screen reader can see.
359
+ Measured in the docs app: both segments of an `error` group report `aria-invalid="true"` and the
360
+ same `aria-describedby`, and a `hint` group links the message without claiming an error.
361
+
362
+ The `invalid` input on every field already described this arrangement in its own documentation —
363
+ *"for when the text lives elsewhere, such as a form-level error summary or one message covering a
364
+ whole field group"*. The group was the half that had never been built.
365
+
366
+ - **`ds-button` forwards everything else a link can carry: `fragment`, `queryParams`,
367
+ `queryParamsHandling`, `target` and `rel`.** Each is a pass-through to the anchor the component
368
+ already renders, so a call-to-action with a destination modifier stays a `ds-button` instead of
369
+ falling back to a hand-written class.
370
+
371
+ ```html
372
+ <ds-button [routerLink]="['/ai-solutions', slug]" fragment="enquiry">Talk to us</ds-button>
373
+ <ds-button [href]="demoUrl" target="_blank" rel="noopener">Open the demo</ds-button>
374
+ ```
375
+
376
+ `fragment`, `queryParams` and `queryParamsHandling` belong to a `routerLink` destination and
377
+ dev-warn on any other; `target` and `rel` work on both link destinations and dev-warn on a plain
378
+ button.
379
+
380
+ - **`routerLink` accepts a `UrlTree`** on `ds-button`, `ds-sidenav-item` and `ds-sidenav-group`, so
381
+ the `UrlCreationOptions` with no input of their own — `relativeTo`, `preserveFragment` — are
382
+ reachable without waiting for one.
383
+
384
+ ```ts
385
+ protected readonly enquiry = this.router.createUrlTree(['/ai-solutions', slug], {
386
+ fragment: 'enquiry',
387
+ });
388
+ ```
389
+
390
+ - **`ariaCurrent` on `ds-button`, `ds-sidenav-item` and `ds-sidenav-group`, and
391
+ `routerLinkActiveOptions` on `ds-button`.** `ariaCurrent` overrides what the link announces,
392
+ including `null` for "announce nothing" and `'step'` or `'location'` where the link is not a
393
+ page. Left alone, the announcement follows the exact/prefix rule above and needs nothing from
394
+ the consumer.
395
+
396
+ `routerLinkActiveOptions` moves what the `active` CLASS matches — and, because the announcement
397
+ is written by the same directive, it also bounds the announcement: narrow it to
398
+ `{ exact: true }` and a prefix match is no longer active, so the link announces nothing at all
399
+ rather than `true`. Set it to change the highlight, and pass `ariaCurrent` alongside it if the
400
+ ancestor announcement still matters.
401
+
402
+ - **Ten classes grew their member surface, which breaks a subclass that declares the same name.**
403
+ Subclassing a DS component is unsupported (`design-system.md` § Components), so this reaches only
404
+ a consumer who does it — and there it is a build error, not a silent change. `ButtonComponent`
405
+ gained `fragment`, `queryParams`, `queryParamsHandling`, `target`, `rel`,
406
+ `routerLinkActiveOptions`, `ariaCurrent`, `linkModifiers` and `ariaCurrentResolved`;
407
+ `SidenavItemComponent` and `SidenavGroupComponent` each gained `ariaCurrent`, `noModifiers` and
408
+ `ariaCurrentResolved`; `TooltipDirective` gained `dsTooltipWhenClipped` and `tipText`;
409
+ `TableComponent` gained `actionLabel` and LOST `cellPopoverText`, `cellTextPopover`, `isClipped`,
410
+ `onCellClipClick` and `onHeaderEnter`, so a subclass that overrode one of the five now overrides
411
+ nothing. `FieldGroupComponent` gained `error`, `hint`,
412
+ `warning`, `messageIcon`, `reserveMessage`, `reserveMessageResolved`, `invalidResolved`,
413
+ `messageId`, `message`, `fieldMessage` and `uid` — it shares the fields' message base now;
414
+ `InputComponent` gained `groupMessage`, and `SelectComponent`, `AutocompleteComponent` and
415
+ `DatePickerComponent` gained `groupMessage` and `describedByIds`. Being public API or not is no protection:
416
+ `private` and `protected` collide with TS2415 exactly as a public name does.
417
+
418
+ `routerLink` also widened on the three navigating components — `string | readonly unknown[] |
419
+ null` became `DsRouterLink`, which adds `UrlTree`. Writing it is unaffected; code that READS the
420
+ value back, or overrides the input, has a new union member to handle.
421
+ - **`ds-stat` takes `--ds-stat-value-lines` and `--ds-stat-value-wrap`, which compose with the
422
+ `white-space` hook.** The three cover the shapes a KPI value actually needs: clip to one line
423
+ (the default), wrap freely, wrap and put the ellipsis on the line you name, or break a word wider
424
+ than the tile.
425
+
426
+ ```scss
427
+ ds-stat { --ds-stat-value-white-space: normal; } /* wraps */
428
+ ds-stat { --ds-stat-value-white-space: normal; --ds-stat-value-lines: 2; } /* … then clips */
429
+ ds-stat { --ds-stat-value-white-space: normal; --ds-stat-value-wrap: anywhere; }
430
+ ```
431
+
432
+ `--ds-stat-value-lines` only bites once the value wraps: a clamp on a `nowrap` box has nothing to
433
+ clamp. And wrapping alone does not keep a long value inside the card — a single word wider than
434
+ the tile still paints past the edge, which is what `--ds-stat-value-wrap: anywhere` is for.
435
+
436
+ Whatever is clipped is still readable: the label and the value each disclose their full text in a
437
+ tooltip on hover, and only when they are actually clipped, so a tile that fits shows no tip.
438
+
439
+ - **`dsTooltipWhenClipped`, so any host can disclose only what it is actually hiding.** With it the
440
+ tip opens only while the host shows less text than it holds, re-tested on every open — so it
441
+ appears and stops appearing as a column, panel or window is resized, with no observer to run. Left
442
+ with no `dsTooltip` text it discloses the host's own text, which is what makes it usable on
443
+ projected content.
444
+
445
+ ```html
446
+ <span class="cell" dsTooltipWhenClipped [dsTooltip]="row.name">{{ row.name }}</span>
447
+ ```
448
+
449
+ `isTextClipped(element)` is exported from `/core` behind it: true when the element, or anything it
450
+ renders, is showing less than it holds. Horizontal only — a clamped block hides whole lines and
451
+ its `scrollWidth` matches its `clientWidth`.
452
+
453
+
454
+ - **Five charts: `ds-bar-chart`, `ds-column-chart`, `ds-donut-chart`, `ds-funnel-chart` and
455
+ `ds-line-chart`.** Each takes a `caption`, a `summary` for the accessible name, a `loading`
456
+ skeleton sized to the real data so the chart does not resize when the numbers land, an `emptyText`
457
+ and a `valueFormat` — and each offers its numbers again as a table under a
458
+ `dataTable: 'toggle' | 'visible' | 'none'` disclosure, because a chart that only draws is a chart
459
+ a screen reader cannot read.
460
+
461
+ ```html
462
+ <ds-bar-chart caption="Visitor funnel" [data]="rows" />
463
+ <ds-line-chart [categories]="months" [series]="series" yAxisMode="rounded" />
464
+ ```
465
+
466
+ The two that carry real geometry are worth knowing about. `ds-funnel-chart` has a `shape`, and it
467
+ defaults to `'area'` — the silhouette with the stage boundaries moved so each band's AREA is
468
+ proportional to its value, the honest encoding that still leaves a tail you can put a label on.
469
+ `'width'` reads every boundary off the values, which collapses the tail of a steep funnel below a
470
+ labellable width. `'taper'` encodes NOTHING: the silhouette is fixed whatever the data, so editing
471
+ the values moves the table under it and never the shape — reach for it only where the numbers are
472
+ read from that table. `ds-line-chart` has a `yAxisMode` that only matters once a series sets
473
+ `axis: 'secondary'`: `'rounded'` and `'exact'` share one set of gridlines and differ in whether the
474
+ second axis rounds its step up or ends on its largest reading, `'independent'` grids each axis on
475
+ its own, and `'stacked'` draws two plots sharing the category axis.
476
+
477
+ All five take `interactive`, and it is the keyboard switch rather than the click switch: the click
478
+ output — `rowClicked`, `pointClicked`, `sliceClicked`, `stageClicked` and `ds-line-chart`'s own
479
+ `pointClicked` — fires with or without the flag. With it set, every mark joins the tab order as a
480
+ `role="button"` answering Enter and Space, and the container announces itself as a `group` rather
481
+ than an `img`; that swap is load-bearing rather than cosmetic, because `role="img"` makes a
482
+ browser treat everything inside as presentational, and a focusable mark inside one is not
483
+ reachable at all.
484
+
485
+ `ds-donut-chart` is the exception, and deliberately: its arcs take the keyboard route only when
486
+ `legend="none"`. Where a legend is drawn, its rows already carry the route, and making both
487
+ focusable would give a four-slice chart eight tab stops for four things.
488
+
489
+ The focus ring on an SVG mark is a drawn stroke, not an `outline` — an outline on an SVG element
490
+ paints its BOUNDING BOX rather than its silhouette, so a funnel stage would ring as a flat bar
491
+ across its trapezoid. `--ds-funnel-chart-focus-color` and `--ds-funnel-chart-focus-width`,
492
+ `--ds-line-chart-focus-color` and `--ds-line-chart-focus-width`, and
493
+ `--ds-donut-chart-focus-color` and `--ds-donut-chart-focus-width` set it, each falling back to
494
+ `--focus-ring-color` and `--focus-ring-width`. Under forced colours the outline is kept instead,
495
+ where `stroke` is not remapped.
496
+
497
+ **Each chart draws its own frame** — border, radius, padding and an `--surface-default` background
498
+ — which is unusual in this library, where a component resists owning chrome. A chart earns the
499
+ exception because it is read as an object rather than as a block of text: a plot, its axes, a
500
+ legend and an annex table all run into the page without an edge. One already sitting in a card
501
+ drops it with `--ds-chart-frame-border-width: 0` and `--ds-chart-frame-padding: 0`.
502
+
503
+ `ds-donut-chart` also takes `maxSlices`, which caps the legend: past it the smallest slices are
504
+ summed into one named by `otherLabel`, on the neutral eighth palette colour. Off by default —
505
+ grouping changes what the chart says, so it is the consumer's call — and the tail is summed rather
506
+ than dropped, so the total never moves.
507
+
508
+ Two geometry rules are worth knowing because they are not preferences. `ds-donut-chart` holds its
509
+ centre content to the square that fits inside the hole, so a long `centerLabel` wraps instead of
510
+ running out over the ring, and the text carries a halo of the chart's own background — at
511
+ `thickness: 1` it sits on the slices, where no single text colour is readable against three
512
+ different hues. And `ds-bar-chart` keeps a label far closer to its own bar than to the next row,
513
+ because levelling the two makes the eye group a bar with the label BELOW it and read every row off
514
+ by one.
515
+
516
+
517
+ - **Chart colour is three families, and reaching for the wrong one is the usual chart bug.** The
518
+ eight `--ds-chart-series-N-color` hooks are CATEGORICAL — they separate marks that are DIFFERENT
519
+ THINGS, such as donut slices or line series. A bar chart's rows are not different things; they are
520
+ one series measured five times, and painting them from a categorical palette says five categories
521
+ where there is one. So a single series has hooks of its own, and ordered stages have a third set:
522
+
523
+ ```scss
524
+ /* different things */ --ds-chart-series-1-color … --ds-chart-series-8-color
525
+ /* one thing, measured often */ --ds-chart-series-default-color + --ds-chart-series-accent-color
526
+ /* ordered stages of one */ --ds-chart-ramp-1-color … --ds-chart-ramp-8-color
527
+ ```
528
+
529
+ `ds-bar-chart` takes the single-series pair: every row shares `--ds-chart-series-default-color`, and
530
+ setting `color` on one row marks the one the reader should land on — usually
531
+ `var(--ds-chart-series-accent-color)`. There is no accent flag, because the accent is a colour and a
532
+ boolean would only be a less flexible way of setting one. `ds-funnel-chart` takes the ramp, spread
533
+ across however many stages there are, with the last stage leaving it for the accent.
534
+ `ds-donut-chart`, `ds-line-chart` and `ds-column-chart` take the categorical set — a column often IS
535
+ a separate thing (revenue by region), and where a column chart is instead one quantity over time,
536
+ `color` puts every column on the single-series colour in one pass.
537
+
538
+ The categorical eight are retuned with this: led by coral and teal, each clearing 3:1 on white for
539
+ WCAG 1.4.11 and at least dE 15 from every other under normal, deuteranope and protanope vision. No
540
+ hue sits between 35 and 130 — a yellow or a lime is high-luminance by nature, and dragging one down
541
+ to clear the contrast floor turns it to mustard. Slot 8 is a neutral rather than a ninth hue: every
542
+ eighth HUE that clears the floor lands within dE 4 of one of the other seven under some colour-vision
543
+ deficiency, so the honest eighth is one that has no hue to collide with.
544
+
545
+ ### Changed
546
+
547
+ - **`--ds-chart-line-width-bold` now reaches a rule.** Highlighting one `ds-line-chart` series —
548
+ from the legend, or from a mark — thickens it to that width as well as dimming the others, so the
549
+ highlight survives a monochrome print and a reader who cannot tell the two hues apart.
550
+
551
+ - **A chart's generated description leads with what the chart says, not with how it is drawn.** The
552
+ order is now: what it is and its scale, the trend, the extremes, then where the numbers are —
553
+ `"Visits by month, 3 points, 1,620 to 2,410. Rising throughout. Highest in Nov at 2,410, lowest
554
+ in Sep at 1,620. Full values in the table below."` It used to recite first-to-last and then the
555
+ extremes, which is a recital of the encoding, and blind readers rank that lowest of the four
556
+ levels of chart description — the encoding is the one thing a screen-reader user cannot use.
557
+
558
+ The trend is named rather than implied: a series that only ever rises reads "Rising throughout",
559
+ one that dips on the way up reads "Rising overall", and one that returns to its starting value
560
+ reads "Ending where it started".
561
+
562
+ The closing pointer follows the table: a chart at `dataTable="none"` no longer promises a table
563
+ that is not rendered. `summary` still overrides the whole sentence.
564
+
565
+ - **An `interactive` chart is one tab stop, not one per mark.** Arrow keys walk the marks, Home and
566
+ End reach the extremes, and the ends wrap the way `ds-radio-group`'s do. `ds-line-chart` keeps one
567
+ stop PER SERIES, so a two-series plot is two stops and each line is a strand the arrows walk;
568
+ measured on the docs card, twelve markers now expose two tab stops instead of twelve.
569
+
570
+ WCAG 2.1.1's Understanding is explicit that not every mouse-operable control has to be separately
571
+ focusable, and that is the permission this rests on. Nothing in the API changed — a page that
572
+ bound `interactive` and an output needs no edit — but a test that counted `[tabindex="0"]` inside
573
+ a chart will now see one per series.
574
+
575
+
576
+ ### Fixed
577
+
578
+ - **A disabled field is no longer announced as invalid.** Every field bound `aria-invalid` from its
579
+ error state alone, so a control that was disabled AND carried an error told a screen reader
580
+ "invalid" about something the reader cannot act on. Nothing on screen changed — the error paint
581
+ already excluded disabled — which is why it went unseen.
582
+
583
+ The belief that a natively disabled control made the attribute inert is wrong, and that is what
584
+ kept the defect narrow in the record: measured in Chrome's accessibility tree, a disabled
585
+ `<input aria-invalid="true">` reports `invalid=true` and is NOT ignored. Disabling removes an
586
+ element from the tab order, not from the tree. So this reached all fifteen fields, not the two
587
+ first reported.
588
+
589
+ The rule lives in one place — the shared message resolver — rather than in fifteen templates: a
590
+ disabled control is neither submitted nor validated, the same reasoning `_field-state.scss`
591
+ already uses to keep the error paint off it. The message TEXT still shows: a refused field may
592
+ still need to say why.
593
+
594
+ ### What you can now DELETE
595
+
596
+ | your workaround | why it is unnecessary | replace with |
597
+ | --- | --- | --- |
598
+ | `class="btn` — a hand-written button class kept only for controls that need `fragment`, `queryParams`, `target` or `rel` | those reach `ds-button` now, so the control can move with the rest | `ds-button` with the matching input |
599
+ | `[routerLink]="'/path?a=1#b'"` — a query or hash folded into the link string | the string was percent-encoded into the path and never worked; the inputs carry them properly | `[queryParams]` and `fragment` |
600
+ | importing `RouterLink` in your own component to write `[queryParams]` on a `<ds-button>` | that put a second `RouterLink` on the host, disagreeing with the anchor's about the destination | the component's own inputs |
601
+ | `ds-stat { --ds-stat-value-white-space: normal; }` written only to stop a long value painting over the tile beside it | the value clips by default, so it no longer escapes its card | nothing — keep the hook only where you want the value wrapped and the tile taller |
602
+ | `ds-stat .value { overflow: hidden; text-overflow: ellipsis; }` — your own clip on the value | the component clips it, and with `overflow: clip` plus a clip margin, so descenders survive where `hidden` shaved them | nothing |
603
+ | `.cell-text-pop` — a rule sizing or colouring the table's full-value popover | the popover is gone; a clipped cell opens a tooltip instead | `--ds-tooltip-*`, if the panel needs changing at all |
604
+ | `--ds-chart-axis-title-color` | no chart draws an axis title, so the token reached no rule and setting it changed nothing | nothing |
605
+ | `--ds-chart-grid-line-strong-color` | no chart draws a strong gridline, so the token reached no rule | nothing |
606
+ | `--ds-chart-tick-size` | no chart draws tick marks on its axes, so the token reached no rule | nothing |
607
+
608
+ ## 0.12.3 — 2026-09-10
609
+
610
+ ### Breaking
611
+
612
+ - **`ds-button`'s `buttonRef` is `controlRef`, and it is typed `HTMLElement`.** The element the
613
+ component renders now follows its destination, so the old name described one of three cases and
614
+ the old type described the same one. Rename the reference; the property behind it is unchanged.
615
+ A read of `.nativeElement` that expects a `<button>` — `.disabled`, `.form`, `.type` — no longer
616
+ type-checks and needs a narrow of your own, because the element may be an `<a>`.
617
+
618
+ ```ts
619
+ // before
620
+ trigger.buttonRef().nativeElement.focus();
621
+ // after
622
+ trigger.controlRef().nativeElement.focus();
623
+ ```
624
+
625
+ ### Added
626
+
627
+ - **`ds-button` takes `routerLink` and `href`, so a call-to-action can stay a real link.** Three
628
+ elements, decided by destination: `routerLink` renders an `<a [routerLink]>` that also carries
629
+ `routerLinkActive`, `href` renders a plain `<a href>`, and neither renders the
630
+ `<button type="button">` it always did. Unset — the default — nothing changes.
631
+
632
+ The look is identical across all three, because the styling is class-based rather than keyed to
633
+ the tag. What you get back is what the element decides: middle-click, open-in-new-tab,
634
+ copy-link-address and the `link` role a screen reader announces.
635
+
636
+ ```html
637
+ <ds-button routerLink="/reports" icon="arrowRight">Go to reports</ds-button>
638
+ <ds-button href="https://example.com" variant="outline">Read the spec</ds-button>
639
+ ```
640
+
641
+ `routerLink` takes the shapes a router link takes anywhere, a string or a command array.
642
+ **`type` and `loading` are button-only** and are ignored on a link with a dev-mode warning: an
643
+ anchor has no form to submit, and a navigation cannot be in flight before it starts. `disabled`
644
+ works on all three, but an anchor has no native disabled state, so it takes `aria-disabled` plus
645
+ `tabindex="-1"` — and its click is swallowed, which is what stops an `href` from navigating
646
+ anyway. `disabledReason` reads the same on a link as on a button.
647
+
648
+ - **`ds-checkbox`, `ds-radio` and `ds-switch` take `ariaLabel`.** A control rendered with no
649
+ visible label — no `label`, nothing projected — had no accessible name and nothing a consumer
650
+ could set to give it one, while `ds-select` and `ds-number-stepper` had taken this input all
651
+ along. The row's `<label>` collapses when empty, so on a bare box the `aria-label` is the whole
652
+ name.
653
+
654
+ ```html
655
+ <ds-checkbox ariaLabel="Select all rows" />
656
+ ```
657
+
658
+ It applies only when there is no visible label; set it beside one and it overrides what the label
659
+ says, which is the ARIA rule rather than a choice this makes.
660
+
661
+ - **`--ds-field-group-focus-shadow-error` — the halo a `ds-field-group` draws while invalid and
662
+ focused.** Defaults to `--ds-field-focus-shadow-error`, the same halo a single error field uses,
663
+ so a focused invalid group reads as one state instead of a red border with a blue glow around it.
664
+
665
+ - **`BreadcrumbItem` takes `ariaLabel`, for the icon-only crumb.** A crumb with an `icon` and no
666
+ `label` — the usual home crumb — rendered as a link with no accessible name at all. Nothing is
667
+ derived from `icon`: `home` is a glyph id, not a word for the user, so a crumb in that shape now
668
+ dev-warns until it is given a name.
669
+
670
+ ```ts
671
+ items = [{ icon: 'home', href: '/', ariaLabel: 'Home' }, { label: 'Records' }];
672
+ ```
673
+
674
+ - **`--focus-ring-radius` — the radius a box takes when it exists only to carry a focus ring.**
675
+ Follows `--ds-radius-inner`, 4px, so retuning the inner radius moves these rings with it. There
676
+ is no `outline-radius` in CSS: an outline follows the
677
+ `border-radius` of the box it is painted on, so a ring host with no radius of its own draws a 90°
678
+ rectangle beside the rounded controls around it. Set this to reshape every such ring at once, or
679
+ give the host its own radius to override it locally.
680
+
681
+ ### Changed
682
+
683
+ - **A clickable `ds-table` row, a `ds-tree` row and a `ds-list` activator draw a rounded focus
684
+ ring.** All three ringed a square-cornered box while every control around them was rounded; they
685
+ now carry `--focus-ring-radius`. None of the three paints anything itself — the table row's tints
686
+ sit on its cells — so the radius shapes the ring and nothing else, and it sits on the resting rule
687
+ rather than inside `:focus-visible`, or the shape would appear only while focused. Reachable by
688
+ keyboard only.
689
+
690
+ - **`ds-checkbox`, `ds-radio` and `ds-switch` draw a rounded focus ring.** The ring goes on the row
691
+ that holds the glyph and its label, and that row had no radius, so it came out square while the
692
+ glyph inside it was rounded. The row now takes `--focus-ring-radius`. The row paints nothing else,
693
+ so this changes the ring and nothing besides it — no fill, no border, no layout. Reachable by
694
+ keyboard only; the resting state of all three is unchanged.
695
+
696
+ - **Four exported classes grew members — only matters if you SUBCLASS one.** `ButtonComponent`
697
+ gained `routerLink`, `href`, `controlRef` and `destination`, which decides which of the three
698
+ elements renders; `buttonRef` is gone from its surface, so a subclass that overrode it now
699
+ overrides nothing. `CheckboxComponent`, `RadioComponent` and `SwitchComponent` each gained
700
+ `ariaLabel` and `resolvedAriaLabel`. Being public API or not is no protection: `private` and
701
+ `protected` collide with TS2415 exactly as a public name does. Nothing changes for a consumer who
702
+ only uses the elements.
703
+
704
+ ### Fixed
705
+
706
+ - **`ds-field-group[invalid]` keeps its error border under the cursor and under focus.** Both
707
+ `:hover` and `:focus-within` carried one class more than `.invalid` did, so they out-ranked it —
708
+ and the border is the group's ONLY error affordance, because a segment's own label and message are
709
+ hidden to keep the glued row intact. The error vanished at exactly the moment the user reached the
710
+ control. Hover and focus now do not match an invalid group at all, and its focus halo takes the
711
+ error tint through the new `--ds-field-group-focus-shadow-error`. A valid group hovers and focuses
712
+ exactly as before.
713
+
714
+ `.invalid` also stops depending on line order to lose to `.disabled`: both sat at the same
715
+ specificity and only the order of the two rules decided it. Disabled takes no state paint, the
716
+ same rule the nine single fields now follow.
717
+
718
+ - **`ds-stat variant="error"` recolours the value.** `:host(.error) .value` and the later
719
+ `.stat .value` land on the same specificity once emulated encapsulation adds its attribute to
720
+ each, so the default colour won on source order and the error variant changed nothing at all.
721
+ Error now moves the `--_stat-value-color` resolver, which is how the size variants already work,
722
+ so a consumer's `--ds-stat-value-color` still overrides it.
723
+
724
+ - **`ds-sidenav-footer`'s collapse button has an accessible name.** Its only name was the
725
+ `Collapse` text beside the chevron, and the collapsed rail hides that text — so on the rail, which
726
+ is the state the button exists to leave, it announced as an unlabelled button. It now carries
727
+ `aria-label`, and both the label and the name say `Expand` while collapsed, because that is what
728
+ the button does from there. The placeholder search row rendered when there are no search items had
729
+ no name either and now matches its live twin.
730
+
731
+ - **An icon-only `ds-breadcrumbs` crumb has an accessible name.** The crumb rendered an `<a>` around
732
+ a decorative icon and nothing else, so a screen reader announced a link with no name and a
733
+ keyboard user tabbed onto an anonymous stop. Give it `ariaLabel` (above); in dev mode a crumb
734
+ still missing one says so.
735
+
736
+ - **A disabled field no longer paints its `data-field-state`.** An `error`, `warning` or `success`
737
+ state used to out-rank the disabled look in all nine field components — `ds-input`, `ds-textarea`,
738
+ `ds-select`, `ds-multi-select`, `ds-autocomplete`, `ds-date-picker`, `ds-time-picker`,
739
+ `ds-color-picker` and `ds-otp-input` — so a field left invalid and then disabled kept a red border
740
+ and fill while being unfocusable. It was pure specificity: the state selector carried one more
741
+ class than the disabled rule it landed on. A disabled control is not submitted and is not
742
+ validated, so the error promised a correction that could not be made; ARIA settles the same
743
+ conflict the same way, ignoring an ARIA state that a native attribute contradicts.
744
+
745
+ **A read-only field still paints it, deliberately.** `readonly` is submitted where `disabled` is
746
+ not, so a wrong value there does reach the server and is worth flagging. Both skip browser
747
+ validation; only one of them can still send something invalid.
748
+
749
+ - **A `ds-multi-select` panel's filter row draws a rounded focus ring.** It came out as a hard
750
+ rectangle the full width of the panel, inside a panel whose every other control is rounded,
751
+ because an `outline` has no radius of its own — it follows the box it is drawn on, and that row
752
+ had none. It now carries `--ds-radius-inner`, which is the radius the panel's option rows and
753
+ clear button already use. `ds-sidenav-footer`'s search box was always drawn this way and is
754
+ unchanged.
10
755
 
11
756
  ## 0.12.2 — 2026-09-09
12
757