@deriv-com/dds-marketing 0.1.0 → 1.0.0

package/.llm/components/segmentedcontrolitem.md

@@ -0,0 +1,280 @@
+<!-- GENERATED from segmented-control-item.contract.json. Do not edit. -->
+
+# SegmentedControlItem
+
+One option in a segmented control, and nothing on its own — a segment says it is the chosen one of a set, and a set of one has nothing to be chosen from. It draws as a pill with a word in it and is announced as a radio, which is what tells a reader these exclude each other before they press anything.
+
+Which segment is current belongs to the group rather than to the segment: exactly one may be, and a segment cannot see its siblings. So `selected` arrives from SegmentedControl, as `size` does — a row at mixed heights is not a row. `disabled` is the consumer's, and it bars this one option while the rest still answer.
+
+## Use when
+
+- One option in a SegmentedControl — the thing a reader presses to change which of a few mutually exclusive values is in force
+- A choice worth showing beside its alternatives rather than hiding in a list, so the reader compares and picks in one glance
+
+## Do not use
+
+- The option names a slice of the page the reader moves to rather than a value they set → `Tab`
+- The choice is on or off rather than one of several → `Button`
+- The option leads somewhere → `Link`
+- A standalone control. Outside a SegmentedControl nothing injects `selected`, so the segment answers for itself and is a pill that never changes — and `role="radio"` outside a radiogroup is a promise about a set that is not there
+- A submit. This is `type="button"` deliberately: a segment inside a signup form that posted it would be a navigation nobody asked for
+- A long phrase. A row is read across at a glance, and a segment carrying a sentence is a row the reader has to work through one word at a time
+
+## Anatomy
+
+SegmentedControlItem renders 4 elements. A token binding names the part it applies to.
+
+- `root` — `<button>`, class `dds-segmentedcontrolitem`. The segment itself, and the whole of its hit target: the corners the focus ring follows, the side padding, and the row holding a glyph beside the words.
+  
+  It paints no ground of its own when it is the chosen one. That belongs to SegmentedControl's indicator, which is a single pill the row moves rather than one pill per segment switched on and off — two grounds cross-fading always reads as two grounds, and only a single positioned element can travel. What is left here is the hover tint, and it lands on unchosen segments alone: offering a treatment to the segment that already holds the value tells the reader something is available that they have already got.
+  
+  Its block padding is zeroed because a `<button>` carries `1px 6px` from the UA stylesheet and `appearance: none` does not clear it. The segment takes its height by stretching inside the row rather than by declaring one, so two inherited pixels inside a fixed box is exactly the kind of thing that goes unnoticed until a row sits two pixels proud of the Button beside it.
+  
+  It dims itself when barred, with one `opacity.disabled` over the whole box rather than a colour on each part — which is what keeps the label and its glyph fading together and reading as one unavailable object. That has to sit here rather than on the group: the group's own disabled closes every option at once, and a sweep over the row would dim all four segments to say one word is unavailable.
+  
+  It carries `size.target.min` on both axes, which is the one measure here that answers to a fingertip rather than to the type or to the row. Nothing else guarantees the segment a size: its width is its word plus its padding, and its height is whatever the groove hands down when it stretches — so a short word in a small row is exactly the case that would draw a target under the 24px WCAG asks for. A minimum rather than a size, so the stretch still decides the height and the words still decide the width wherever both already clear the floor.
+- `icon` — `<svg>`, class `dds-segmentedcontrolitem__icon`. A glyph before the label, helping a reader tell one mode from another faster than the words alone.
+  
+  The class lands on the `<svg>` itself rather than on a box around it, which is what Button and ButtonIcon in this package both do and for the same reason: every glyph in the icon package ships `width` and `height` presentation attributes defaulting to 24, and the only thing that overrides a presentation attribute is a CSS length on the element carrying it. A wrapper would keep its own measure while the mark kept the package's.
+  
+  It draws from `icon.control.*` rather than through Marketing's Icon, whose ramp is `icon.size.*`. The two do not line up — the control ramp steps 16, 18, 20 where the size ramp steps 16, 20 — so an md segment has no step to ask Icon for, and rounding to either neighbour would put this mark a measure away from the same glyph in the Button beside it.
+  
+  Its colour steps with the selection exactly as the label's does, because a glyph that stayed muted under a chosen word would read as a mark on something disabled. Rendered only when `icon` is set.
+- `label` — `<span>`, class `dds-segmentedcontrolitem__label`. The name of the value, and the segment's accessible name — a word or two, because a row of segments is read across rather than down.
+  
+  A span rather than the button's bare text, because the type, the colour and the weight all need a part to land on, and two of those three carry the selection: the ink steps from `color.fg.muted` to `color.fg.default`, and the weight from the body cut to the label cut. Marketing's Tab reaches the same arrangement by the same route.
+  
+  Its colour is given a duration and its weight is taken back out of the transition in `segmented-control-item-impl.css`. The generator lists every property that varies, and the face ships as separate cuts rather than a variable one, so an interpolated weight lands between two of them and snaps — and weight is the property that changes a word's width, which would drag the segment's neighbours along on every press and move the pill the row is measuring.
+- `sizer` — `<span>`, class `dds-segmentedcontrolitem__sizer`. The same words at the chosen weight, laid out and never drawn, so the label is already as wide as it will ever be.
+  
+  Without it, pressing a segment widens its word, which widens the segment, which slides every segment after it — and here that costs more than it does on a strip of tabs, because SegmentedControl measures the chosen segment to place its pill. A row that resizes at the moment of the press is a row whose pill is measured against a box that is still moving.
+  
+  `aria-hidden`, because this is the label a second time. An element rather than a `::after` with `content: attr(...)` for the same reason: generated content counts toward the accessible name, and a pseudo-element cannot be hidden from assistive technology.
+
+Apply these classes from the generated `segmentedControlItemParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `SegmentedControl`, `SegmentedControlItem`, `Tab`, `TabList`, `Button`, `ButtonIcon`, `Link`, `Card`, `CardButton` — in children or in any prop that takes a node
+
+## Props
+
+### selected — `boolean` (default `false`)
+
+Use when: Never from the call site in ordinary use — SegmentedControl injects it, because exactly one segment may be current and a segment cannot see its siblings. Passing it on a segment inside a group seeds which one starts chosen, and the group takes it from there
+Never for: Marking more than one. A row with two segments selected is a radiogroup announcing two answers to one question, and the group overwrites whatever it was given on every render regardless
+
+### disabled — `boolean` (default `false`)
+
+Use when: This one option is unavailable while the rest still answer — a plan the reader's account cannot take, a period an offer does not run for. It stays findable and simply refuses the press
+Never for: Closing the whole row. SegmentedControl has its own disabled for that, which dims as one object and marks no segment — a row barred segment by segment would put disabled on the segment holding the value, and that pair is refused
+
+### size — `sm` | `md` | `lg` (default `md`)
+
+- `sm` — A control seated in something already dense — a filter row, a picker in a navigation bar. Desktop only: below what a finger reliably hits
+- `md` — The default. Sized to a medium control, so the row lines up with the fields and buttons next to it
+- `lg` — A choice in a hero or a conversion band, where the control is the point of the section rather than an adjustment within it
+
+Use when: Never from the call site — SegmentedControl injects it. A row at mixed heights is not a row, so the height is the group's decision and is overwritten on every render
+Never for: Making one segment stand out. Every segment in a row is the same size; a choice that needs emphasis has it in the copy around the control
+
+### value — `string` **Required.**
+
+Use when: Always. It names this segment for a group that is told which value is in force from outside, and it is what reaches the consumer's onChange when the segment is pressed
+Never for: The words the reader sees. That is label — a value is an identifier the page matches on, and one doubling as copy breaks the moment the copy is reworded
+
+### label — `string` **Required.**
+
+Use when: Always — it is the segment's accessible name as well as its words, and a radio with no name is announced as a control with nothing in it. One or two words: a row is scanned across, and the segment that needs a phrase is a choice that wanted a list
+Never for: A sentence, or a value with its unit spelled out. 'Yearly' rather than 'Billed once a year' — the explanation belongs beside the control, where a reader who is not choosing still sees it
+
+### icon — `node`
+
+Use when: The glyph tells the modes apart faster than the words do — a card and a bank beside two payment methods. Import it from @deriv-com/quill-icons-web and pass the element
+Never for: Decoration. A row of segments is scanned, and a mark that says nothing the label does not is one more thing to look past on every one of them
+
+### onSelect — `callback`
+
+Use when: This segment reports its own presses — logging which plan a visitor looked at, say. It is called with this segment's value, and SegmentedControl chains its own handler after it rather than replacing it
+Never for: Holding which segment is current. That is the group's onChange, which fires once for the row; a page wiring up one handler per segment has written the group's job out by hand
+
+Also accepts everything from `ButtonHTMLAttributes<HTMLButtonElement>`.
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- Announced as: `radio`
+- `Enter` — Chooses this segment, as a press does. The button's own behaviour, left alone
+- `Space` — Chooses this segment, as a press does. The button's own behaviour, left alone
+- an accessible name drawn from label, because a radio announced without one is a control the reader is asked to choose between with nothing to tell them apart
+- aria-checked in both directions, never absence. role="radio" without it is announced as a control with no state, so 'not the value in force' is something that has to be said rather than a silence left for the reader to interpret
+- aria-disabled rather than the native attribute. A native disabled removes the button from the accessibility tree, so a reader would never learn the option exists — which is the opposite of what this prop is for, which is to say an option is there and unavailable
+- The press is refused while disabled. aria-disabled is a word to a screen reader and nothing to the browser, so a non-native disabled has to be enforced in the component or the segment announces itself as unavailable and works anyway.
+- One tab stop for the row, which SegmentedControl sets through tabIndex. A segment does not decide its own: every segment taking the tab key would make a reader pass through every answer to reach the next question.
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+- **A component is written along the reading axis, not along the page's left and right** — Every measure, inset and placement in this package names an axis rather than a side: inline-size and block-size, padding-inline and padding-block, inset-inline-start and inset-block-end, margin-inline: auto, text-align: start. Written that way a component follows whichever direction the page is read in, and a band whose claim ranges to the leading edge with its subject on the trailing one is the same composition in Arabic as in English, mirrored, with nothing restated. Written as left and right it is the same pixels in both, which is a layout nobody designed for the second language.
+
+The enum values follow the same rule and for the same reason. A prop that names where a picture sits takes start and end, never left and right — FeatureSplit, FeatureBullets and FeatureScroll all declare mediaPosition that way, and the flex directions they generate flip on their own because row already means the reading order. A value called left would have to be re-read as right by every author working in a mirrored page, which is a translation this system should be doing rather than asking for.
+
+The guidance a contract carries is part of the component, so it follows too. Describing a claim as ranging left is describing one of the two languages, and it was written that way here for a while: three of the opening bands said so in their own intent. A reader in a mirrored page meets that sentence and has to decide whether the component is wrong or the sentence is, and neither answer is one documentation should force.
+
+Two things genuinely have no logical form and are not covered by this. A CSS gradient takes a physical direction — there is no to inline-end — so a pattern that must mirror has to be stated twice under a direction query, and one that is periodic and centred, like PageHeader's rule grid, does not need to. A glyph that points the way onward is the other: an arrow is a picture of a direction, and mirroring it belongs to the icon set rather than to the component holding it.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ SegmentedControlItem for: The option names a slice of the page the reader moves to rather than a value they set
+   A tab carries aria-current, which says 'this is the one you are looking at'; a segment carries aria-checked, which says 'this is the value in force'. The page beneath a strip of tabs changes wholesale, while what a segment alters is usually one figure or one card next to it
+   → use `Tab` instead.
+
+❌ SegmentedControlItem for: The choice is on or off rather than one of several
+   Two segments reading 'On' and 'Off' is a switch drawn the long way round, and it spends a row of the page saying what one control says in place
+   → use `Button` instead.
+
+❌ SegmentedControlItem for: The option leads somewhere
+   Nothing here carries an href and nothing here navigates. A segment that took the reader off the page would be a menu drawn as a comparison
+   → use `Link` instead.
+
+❌ selected=true + disabled=true
+   The segment holding the value in force cannot also be the one the reader may not pick. Whichever of the two is true the other is a mistake, and the pair renders as a dimmed segment wearing the pill — a control that looks unavailable and is nonetheless the answer. It is unreachable by any honest route as well: the row moves selection with the arrow keys and steps over a barred segment, so nothing the reader can do arrives at it.
+
+❌ disabled=true + state=hover
+   A barred segment does not answer the pointer, so there is no tint for it to take. This is a styling-matrix exemption rather than an API constraint — disabled is a real value and hover is a real state; what does not exist is the pair, because the row sets pointer-events to none over a closed control and a segment barred on its own swallows the press. A tint on either would offer the reader something that is not on offer.
+
+❌ selected=true + state=hover
+   The chosen segment does not answer the pointer with a tint, because it is already the answer — a hover treatment there says 'you could pick this' about the thing the reader has picked. It would also land on the pill rather than on the groove, which is the one surface in this component whose distance from its ground is load-bearing. A styling-matrix exemption, not an API constraint: a chosen segment is hoverable and simply does not change.
+
+## Example
+
+```tsx
+import { SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+<SegmentedControlItem value="yearly" label="Yearly" selected />
+```
+
+## In use
+
+### Chosen, and not
+
+The ink and the weight both step. A segment told apart by colour alone is one a reader who cannot separate two greys has to guess at. Nothing here paints the pill — that is the row's to draw.
+
+```tsx
+import { SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+// The value in force
+<SegmentedControlItem value="yearly" label="Yearly" selected />
+
+// Not chosen
+<SegmentedControlItem value="monthly" label="Monthly" />
+```
+
+### Barred on its own
+
+One option unavailable while the rest answer. It dims as one object and stays findable: a reader never told the option exists cannot be told it is unavailable.
+
+```tsx
+import { SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+// Unavailable
+<SegmentedControlItem value="pro" label="Pro" disabled />
+```
+
+### The row's three heights
+
+Size arrives from SegmentedControl rather than the call site — a row at mixed heights is not a row. The segment declares no height of its own and stretches inside the groove.
+
+```tsx
+import { SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+// Small
+<SegmentedControlItem value="usd" label="USD" size="sm" selected />
+
+// Medium
+<SegmentedControlItem value="usd" label="USD" size="md" selected />
+
+// Large
+<SegmentedControlItem value="usd" label="USD" size="lg" selected />
+```
+
+### A glyph before the word
+
+Its colour steps with the selection exactly as the label's does — a mark left muted under a chosen word reads as something switched off.
+
+```tsx
+import { SegmentedControlItem } from '@deriv-com/dds-marketing'
+import { ChartCandlestickRegularIcon, GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+
+// Chosen, with a mark
+<SegmentedControlItem value="card" label="Card" selected icon={<GlobeRegularIcon />} />
+
+// Not chosen, with a mark
+<SegmentedControlItem value="transfer" label="Transfer" icon={<ChartCandlestickRegularIcon />} />
+```