@deriv-com/dds-marketing 0.1.0 → 1.0.0

package/.llm/components/segmentedcontrol.md

@@ -0,0 +1,366 @@
+<!-- GENERATED from segmented-control.contract.json. Do not edit. -->
+
+# SegmentedControl
+
+A row of joined segments from which exactly one is chosen, drawn from a short set of alternatives that exclude each other. What the reader picks sets a value the page beside it consumes — a billing period, a currency, a platform — rather than moving them anywhere.
+
+It holds which segment is chosen, how tall they all are, and whether the choice can be made at all. Those three belong to the row because no segment can answer them: only one may be current and a segment cannot see its siblings, a row at mixed heights is not a row, and closing one option is a different statement from closing the question.
+
+It measures one thing — where the chosen segment sits — so the pill can travel to it. That is the whole reason the pill is a single element the row moves rather than a ground each segment paints: two grounds cross-fading always reads as two grounds, and no selector can answer where a sibling is.
+
+## Use when
+
+- Two to four alternatives that exclude one another, where the whole set is worth showing at once and the reader decides by weighing them side by side rather than recalling which exist
+- What the reader picks becomes a value something next to it consumes — a period against which prices are quoted, a unit, a plan — which puts the control beside whatever it alters rather than at the head of the page
+- The alternatives are short enough to read across in a glance. A row is scanned, not worked through
+
+## Do not use
+
+- The choice swaps a whole slice of the page rather than setting a value → `TabList`
+- The alternatives are separate topics rather than values of one question → `Accordion`
+- There are more than about four, or the labels need more than a word or two → `SelectChip`
+- The choice is on or off → `Button`
+- The reader may pick several of the options at once, or none → `FilterChip`
+- Navigation. Nothing here carries an href and nothing here goes anywhere — a row whose segments led away would be a menu drawn as a comparison, and announced to a screen reader as a set of radio buttons
+- A sequence. Segments are alternatives and are pressed in any order; steps happen in one, and a row says otherwise to everyone who reads it
+- One segment. A set of one is a label wearing a pill, and 'chosen' marks it against nothing
+- A filter that can take several answers at once. Exactly one segment is current here, and the role says so — a set the reader can multi-select is a row of FilterChips
+
+## Anatomy
+
+SegmentedControl renders 2 elements. A token binding names the part it applies to.
+
+- `root` — `<div>`, class `dds-segmentedcontrol`. The groove the segments are shared out across, and the element carrying the group's role and its name.
+  
+  Its ground is `color.bg.track`, the role named for the channel a thing travels along — and the pill travelling is the whole of this component. An alpha rather than a ramp step, which is the opposite of what this contract argued at first and worth recording as a reversal rather than quietly corrected.
+  
+  The first version took `color.bg.subtle`, reasoning that the groove had to be a solid because the pill rises one step above it, and that an alpha laid over a page this component cannot see would let the page decide that distance. That is exactly backwards, and product had already proved it: a solid cannot know what is behind it, so it fails the moment the surface changes. Product's own SegmentedControl drew its track from `bg.subtle` until #193 moved it here, after a control inside a popup came out at ratio 1.00 against the panel and had no visible track at all.
+  
+  Marketing ships light only today, so that particular collapse is not reachable here — but the light-mode half of it is. `color.bg.subtle` is also this package's role for an alternating content band, so a row on one of those bands drew `#E6E8EA` on `#E6E8EA` and the groove disappeared. A billing toggle on a tinted pricing band is an ordinary place for this to sit.
+  
+  The pill answering it is `color.bg.surface-raised`, the role this package describes as a surface that lifts off the one behind it. It stays a solid, and that is what makes the pairing work: the groove darkens whatever ground it is drawn on and the pill is opaque over it, so the pill is always lighter than its own channel whatever the section beneath them is doing. Product reaches the same arrangement through `bg.selected-raised`, a role this package does not have and does not need — the two resolve to the same white.
+  
+  All four sides are inset by `space.inset.2xs`, so a seam of groove stays visible around the chosen segment and the pill reads as seated within the channel rather than filling it. That seam is what lets the lift register as a lift: a shape with ground showing right around it reads as resting on that ground rather than being part of it. The gap between segments is `space.gap.xs` and is the other half of the same frame — a pill framed tightly at its sides and generously above is framed unevenly, and a reader sees that without being able to name it.
+  
+  Its height is the control ramp's, bound directly, so a row sits flush with a Button of the same size beside it. The segments take their own height by stretching inside it, which is why this package needs no segment ramp of its own: a segment is whatever the control is, less the inset on either side, and it stays correct if either value is ever retuned. Product reaches the same alignment by declaring a second ramp and keeping the arithmetic in agreement by hand.
+  
+  The small step is the one to watch if either value is ever retuned. A segment is the control less twice the inset, which runs 24, 32 and 40 against a control ramp of 32, 40 and 48 — and the segment binds `size.target.min` as a floor on both axes, which is 24. So the small row lands exactly on that floor with nothing to spare: raise the inset or lower `size.control.sm` and the segment can no longer fit inside the groove it is stretching in, and it will overflow rather than shrink. Nothing checks this, because the two values are correct apart and only disagree together.
+  
+  It is the positioned ancestor, which is what makes the pill's offsets groove-relative — the one measurement this component takes is read against this box.
+  
+  It is also what dims when the row is closed, with one `opacity.disabled` over the whole groove rather than a mark on each segment. That is what keeps the chosen segment legal: a row that barred every segment would put disabled on the one holding the value, and the item refuses that pair. A segment barred on its own still dims itself; the two never coincide, because a row that is closed has nothing left to bar.
+  
+  It stops answering the pointer while it is closed, so no segment takes a hover tint inside a control that refuses the press. That is a structural rule rather than a token — nothing about it varies by brand or mode — and it belongs to the row rather than to any segment, because a segment barred on its own is still a segment the pointer may rest on.
+- `indicator` — `<span>`, class `dds-segmentedcontrol__indicator`. A single pill serving the whole row, moved to whichever segment is chosen rather than one pill per segment switched on and off.
+  
+  Only that arrangement lets it travel, and travelling is the point: two pills cross-fading always reads as two pills, while one pill has to be positioned — which means something has to know where the chosen segment sits. No selector can supply that answer and no container query reaches it either, the question being about a sibling's position rather than a box's own width. This is therefore the only measured thing in the component.
+  
+  It holds everything that would otherwise have belonged to the chosen segment: the ground, the corners, and the shadow doing the lifting. `elevation.surface.raised` is what separates it from the groove beyond colour alone — the two surfaces are a step apart and the shadow is what says which way.
+  
+  First in the DOM on purpose. It is absolutely positioned, so it paints above anything static; the segments after it are positioned too, and among positioned siblings the later one wins. That is what keeps the words on top with no z-index, which is just as well — no semantic role exists for one.
+  
+  Never a target. It sits behind the segments and refuses the pointer, so a press always reaches the button whose label it underlies. It never dims either, because it is only ever behind the chosen segment and the chosen segment is never disabled.
+  
+  It sets no `display`. An absolutely positioned box is blockified already, so the keyword would add nothing — and it is an author rule, which outranks the `hidden` attribute's UA `display: none` and would leave the pill in the render tree with nothing to mark. That is not harmless here the way an invisible box usually is: with no segment chosen the pill is given no size, and a zero-by-zero element still paints `elevation.surface.raised`, so the groove would carry a small shadow sitting where no answer is. TabList reached the same conclusion, and Accordion's panel was the same mistake: state that belongs to an attribute must not be contradicted by a stylesheet.
+
+Apply these classes from the generated `segmentedControlParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `SegmentedControlItem`
+- Never contains: `SegmentedControl`, `Tab`, `TabList`, `Button`, `ButtonIcon`, `Link`, `Card`, `CardButton`, `Accordion`, `AccordionItem`, `DropdownMenu`, `MenuItem`, `FilterChip`, `SelectChip`, `RemovableChip`, `Option` — in children or in any prop that takes a node
+- Holds at least 2
+
+## Props
+
+### layout — `hug` | `fill` (default `hug`)
+
+- `hug` — Every segment takes the width of its own words and the row takes the total. The default, and what suits a control sharing a line with something else — beside a heading, above a card, at the end of a toolbar. The reader sees labels of unequal length, which is how words look
+- `fill` — The segments split the container into equal shares and the row stretches across it. For a control as wide as whatever it heads — a period switch above a pricing table — where the segments should read as equals of matching weight rather than as a collection of names
+
+Use when: Decide it from what the row sits in rather than from how it looks on its own: a control that shares a line hugs, and one that heads a block fills
+Never for: Making a row wider to fill a gap in a layout. fill divides whatever it is given, so a row in a container far wider than its words draws segments with an acre of ground in each
+
+### 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: Match it to the controls the row sits beside — the height is bound to the same ramp a Button of that name takes, so the two line up
+Never for: Emphasis. A larger row is a bigger target, not a louder one; a choice that needs weight gets it from the copy around it
+
+### disabled — `boolean` (default `false`)
+
+Use when: The question cannot be answered yet — a period switch above prices that have not loaded, a plan picker before an account is chosen. The whole groove dims as one object and the row stops answering the pointer and the arrow keys
+Never for: Barring one option. That is the segment's own disabled, which leaves the rest answering — a row closed to say one word is unavailable dims the answer the reader already has
+
+### label — `string` **Required.**
+
+Use when: Always — a radiogroup with no name is announced as a set of choices with nothing said about what they are choices of. Name the question rather than the act: 'Billing period', not 'Choose a billing period'
+Never for: A heading. This is the group's accessible name and it is not drawn — a control that needs a visible heading gets one on the page above it, where a sighted reader can see it too
+
+### value — `string`
+
+Use when: The page is holding which segment is in force, which is the ordinary case here — the choice drives a price, a figure or a card rendered beside the control, so the page already has the answer. Passing it makes the row controlled: it shows what it is told and reports presses through onChange.
+
+Leave it off and the row holds its own answer, seeded from whichever segment arrived selected. That suits a control whose effect is entirely local.
+Never for: Half of a controlled row. A value passed with no onChange to move it is a control that cannot respond to being pressed, which reads as broken rather than as fixed — and it is the shape a page falls into by adding the value first
+
+### onChange — `callback`
+
+Use when: Whenever value is — together they are how a page holds the choice. It is called with the chosen segment's value after that segment's own onSelect, so a segment that reports its own presses keeps doing so inside a row
+Never for: Side effects a choice should not have. This says which value is in force; a row that also navigated, submitted or fetched on it would be doing the thing its intent says it does not
+
+Also accepts everything from `HTMLAttributes<HTMLDivElement>`.
+
+## 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: `radiogroup`
+- `Tab` — Enters the row at the chosen segment, and leaves it. One stop for the whole control, which is the radiogroup pattern — a reader tabs into the question rather than through every answer
+- `ArrowRight` — Chooses the next segment, wrapping at the end. Selection follows focus, because there is always exactly one answer and moving focus without moving the answer would leave the ring on one word and the value on another
+- `ArrowLeft` — Chooses the previous segment, wrapping at the start
+- `ArrowDown` — As ArrowRight. The row is horizontal, and answering both axes spares the reader a guess about which arrows this one listens for
+- `ArrowUp` — As ArrowLeft
+- `Home` — Chooses the first segment that answers
+- `End` — Chooses the last segment that answers
+- an accessible name from label, so a reader entering the group is told what these are alternatives of rather than that a group exists
+- aria-disabled on the group while it is closed, so a reader is told the question cannot be answered rather than finding a row that simply does not respond
+- One tab stop for the row, on the chosen segment or on the first when none is chosen. A tabIndex of -1 on every segment would make the control unreachable by keyboard the moment a value named nothing.
+- A barred segment is stepped over by the arrow keys rather than focused. Selection follows focus here, so landing on a segment whose press is refused would put the ring on one word and the answer on another.
+- A value naming no segment chooses none of them rather than falling back to the first. This is what the row does when a page asks for a value it does not have — a mismatch worth showing rather than papering over, since quietly choosing something else would tell the reader a value is in force that the page never set.
+- The group takes no focus of its own. Focus belongs to the segments, which are buttons; a row that took focus would be a stop that does nothing.
+
+## 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
+
+❌ SegmentedControl for: The choice swaps a whole slice of the page rather than setting a value
+   A strip of tabs says 'here is the same offer seen differently' and the page beneath it changes wholesale. A segmented control says 'this is the value in force', and what it alters is usually one figure or one card beside it. The roles follow the difference — aria-current against aria-checked — so picking the wrong one tells a reader the wrong thing before they press anything
+   → use `TabList` instead.
+
+❌ SegmentedControl for: The alternatives are separate topics rather than values of one question
+   A segmented control marks one of a set as in force, which only means something when the set answers a single question. A row of unrelated topics tells a reader a comparison exists that does not
+   → use `Accordion` instead.
+
+❌ SegmentedControl for: There are more than about four, or the labels need more than a word or two
+   A row is read across in one glance, and the point at which a reader has to work through it to choose is the point it should have opened a list. SelectChip is that control and still keeps the chosen value on show, which is the half a plain menu drops — a segmented control's whole job is that the answer stays visible. A long row also wraps or scrolls on a phone, and one that wrapped to two lines has stopped being a row.
+   → use `SelectChip` instead.
+
+❌ SegmentedControl for: The choice is on or off
+   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.
+
+❌ SegmentedControl for: The reader may pick several of the options at once, or none
+   Exactly one segment is in force here and role="radiogroup" says so, which is a promise about the set rather than a look. A chip is a toggle that reports whether it applies, so a row of them can be all on, all off or anything between — and a reader told these are radio buttons will not try to turn on a second.
+   → use `FilterChip` instead.
+
+## Example
+
+```tsx
+import { SegmentedControl, SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+<SegmentedControl label="Billing period">
+  <SegmentedControlItem value="monthly" label="Monthly" onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="yearly" label="Yearly" selected onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+```
+
+```tsx
+import { useState } from 'react'
+import { SegmentedControl, SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+// Controlled: SegmentedControl reports the value, not the event.
+const [value, setValue] = useState('')
+<SegmentedControl label="Billing period" value={value} onChange={setValue}>
+  <SegmentedControlItem value="monthly" label="Monthly" onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="yearly" label="Yearly" selected onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+```
+
+## In use
+
+Most rows below hold the same set, written once here:
+
+```tsx
+import { SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+const segmentedcontrolitems = (
+  <>
+    <SegmentedControlItem value="1d" label="1D" selected onSelect={(value) => { /* your handler */ }} />
+    <SegmentedControlItem value="1w" label="1W" onSelect={(value) => { /* your handler */ }} />
+    <SegmentedControlItem value="1m" label="1M" onSelect={(value) => { /* your handler */ }} />
+  </>
+)
+```
+
+### A value, not a destination
+
+The row sets what the prices beside it are quoted in. Nothing here navigates, and the pill marks the answer in force rather than the page the reader is on.
+
+```tsx
+import { SegmentedControl, SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+// Yearly in force
+<SegmentedControl label="Billing period">
+  <SegmentedControlItem value="monthly" label="Monthly" onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="yearly" label="Yearly" selected onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+
+// Monthly in force
+<SegmentedControl label="Billing period">
+  <SegmentedControlItem value="monthly" label="Monthly" selected onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="yearly" label="Yearly" onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+```
+
+### Hug, and fill
+
+Hug lets the words decide each segment's width and suits a row sharing a line with something else. Fill divides the container into equal shares, for a row as wide as whatever it heads.
+
+```tsx
+import { SegmentedControl, SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+// Hug — the default
+<SegmentedControl label="Account currency" layout="hug">
+  <SegmentedControlItem value="usd" label="USD" selected onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="eur" label="EUR" onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="gbp" label="GBP" onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+
+// Fill — equal shares
+<SegmentedControl label="Account currency" layout="fill">
+  <SegmentedControlItem value="usd" label="USD" selected onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="eur" label="EUR" onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="gbp" label="GBP" onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+```
+
+### The control ramp
+
+Each step is the height of a Button of the same name, so a row lines up with the controls beside it. The segments take their height from the groove rather than declaring one.
+
+```tsx
+import { SegmentedControl } from '@deriv-com/dds-marketing'
+
+// Small — desktop only
+<SegmentedControl label="Chart period" size="sm">{segmentedcontrolitems}</SegmentedControl>
+
+// Medium — the default
+<SegmentedControl label="Chart period" size="md">{segmentedcontrolitems}</SegmentedControl>
+
+// Large — a hero or a conversion band
+<SegmentedControl label="Chart period" size="lg">{segmentedcontrolitems}</SegmentedControl>
+```
+
+### One barred, and the row closed
+
+Two different statements. A barred segment leaves the rest answering; a closed row dims as one object and marks nothing — which is what keeps the chosen segment from ever being the disabled one.
+
+```tsx
+import { SegmentedControl, SegmentedControlItem } from '@deriv-com/dds-marketing'
+
+// One plan unavailable
+<SegmentedControl label="Plan">
+  <SegmentedControlItem value="standard" label="Standard" selected onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="plus" label="Plus" onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="pro" label="Pro" disabled onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+
+// The question cannot be answered yet
+<SegmentedControl label="Plan" disabled>
+  <SegmentedControlItem value="standard" label="Standard" selected onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="plus" label="Plus" onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="pro" label="Pro" onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+```
+
+### A glyph where the words are not enough
+
+Two payment methods a reader tells apart faster by the mark than by the noun. A glyph that only repeats its label is one more thing to look past on every segment.
+
+```tsx
+import { SegmentedControl, SegmentedControlItem } from '@deriv-com/dds-marketing'
+import { ChartCandlestickRegularIcon, GlobeRegularIcon } from '@deriv-com/quill-icons-web'
+
+// Marks beside the words
+<SegmentedControl label="Payment method">
+  <SegmentedControlItem value="card" label="Card" selected icon={<GlobeRegularIcon />} onSelect={(value) => { /* your handler */ }} />
+  <SegmentedControlItem value="transfer" label="Transfer" icon={<ChartCandlestickRegularIcon />} onSelect={(value) => { /* your handler */ }} />
+</SegmentedControl>
+```