@deriv-com/dds-marketing 0.1.0 → 0.2.0

package/.llm/components/tablerow.md

@@ -0,0 +1,285 @@
+<!-- GENERATED from table-row.contract.json. Do not edit. -->
+
+# TableRow
+
+One row of a table: the cells that answer the same questions in the same order as every other row. It owns the rule under it and whether it reads as picked, and nothing about what any cell holds.
+
+Being picked is drawn here rather than on the checkbox that sets it, because selection is a fact about the row: a reader scanning a table needs to see which rows are in the set without checking every box in the first column.
+
+## Use when
+
+- A record, with one cell per column
+- A row a reader can pick, where `selected` draws the state the page is holding
+
+## Do not use
+
+- The whole row is a target that navigates → `CardButton`
+- A message spanning every column. A row that says "no results" is a sentence wearing a record's markup, and it is announced cell by cell against headers that do not apply to it
+- A visual separator. The rule between rows is `dividers` on the table; an empty row is a record with nothing in it as far as anything reading the table is concerned
+- Holding which rows are selected. `selected` draws the answer; keeping it is the page's, in its own state
+
+## Anatomy
+
+TableRow renders one element.
+
+- `root` — `<tr>`, class `dds-tablerow`. The row, and the wash that says it is picked. It draws no rule of its own: a `<tr>` border is painted only while a table collapses its borders, and this table separates them so it can hold a corner. So the rule is the cells', handed down from here — every cell draws the line above it, and a run of cells across one row draws one line.
+  
+  Selected is a fill rather than an edge. A row already sits between two rules, so a third line to say it is picked competes with the structure; a wash reads as the row rather than as a boundary around it, and it survives a row whose neighbours are also picked, where an outline would draw four lines between two rows.
+  
+  It takes its size and its rule from the section above and hands both to every cell, so a row's air, its cells' padding and the line between rows are one decision made once.
+  
+  The highlight under the pointer is gated to devices that have one, in table-row-impl.css. A touch screen reports a hover that never ends — the last row tapped keeps the wash until something else is tapped — so a highlight meant to say "a press would land here" ends up saying it about a row the reader has already left. No other component in this package gates its hover, which makes this a departure worth naming rather than a convention being followed.
+
+Apply these classes from the generated `tableRowParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `TableCell`, `TableHeaderCell`
+- Never contains: `Table`, `TableHead`, `TableBody`, `TableRow` — in children or in any prop that takes a node
+- Holds at least 1
+
+## Props
+
+### selected — `boolean` (default `false`)
+
+Use when: The page is holding this row in a set the reader has picked — for an export, a bulk action, a comparison. It draws the state and reports nothing: the checkbox in the row is what a reader presses, and what it reports belongs to the page
+Never for: The row under the pointer, or the row a reader last looked at. Hover is the browser's and this is a persistent answer — a row that highlighted on approach would say the reader had picked everything they passed over
+
+### hoverable — `boolean` (default `true`)
+
+Use when: Handed down by the table. It draws a wash under the pointer so a reader knows which row a press would land on — and only on a device that has a pointer, which the row's own stylesheet gates
+Never for: Saying a row is chosen. Hover is where the pointer is and nothing more; `selected` is the answer a reader gave, and a row that looked picked on approach would say they had picked everything they passed over
+
+### dividers — `rows` | `grid` | `none` (default `rows`)
+
+- `rows` — The default. A line between rows and none between columns, which is what stops the eye slipping from one row's start to another's end — the mistake a wide table invites and the one a reader never notices making
+- `grid` — Lines both ways, for a table read as a matrix rather than as a list of records: a rate card, a comparison where the reader traces a column as often as a row. It is more lines than most tables need, so it should be asked for
+- `none` — No lines at all. Right for two or three rows, where the rules are more structure than data, and for a table whose columns are already separated by their alignment
+Never for: Marking a group. A missing line is not a heading — a table that wants sections wants a header row inside the body, or two tables. Nor `grid` as decoration on a long table: every vertical line is another thing between a reader and the value they came for
+
+### headerCase — `upper` | `title` (default `upper`)
+
+- `upper` — The house setting: column names in capitals, at the role that suits them. A header is read once where the data under it is read many times, and capitals are what stop it competing
+- `title` — Names drawn as they were written, at twelve pixels. Right where the names are long, are proper nouns whose own capitals would be flattened, or are in a script with no case at all
+
+### overflow — `wrap` | `truncate` (default `wrap`)
+
+- `wrap` — The default. Text too long for its column wraps and the row grows taller, so nothing is hidden — right whenever the value is the point and a reader has to read all of it
+- `truncate` — Rows must stay one line high — a dense table a reader scans down, where a row that grew would break the rhythm they are scanning by. The value is clipped with an ellipsis and the whole of it is still reachable, so this trades seeing for scanning rather than losing anything
+Never for: Making a column narrow enough to be worth truncating. Clipping is what a column does when it has run out of room, not a way to give it less — a table of ellipses has hidden its data behind a hover on every cell
+
+### size — `sm` | `md` | `lg` (default `md`)
+
+- `sm` — Compact. Dense data a reader scans rather than reads — a ledger, a positions table, anything where fitting more rows on screen is worth more than air around each one
+- `md` — Balanced, and the default: rows a reader moves through at reading pace, with enough room that the eye does not slip between them
+- `lg` — Spacious. Few rows, each carrying something substantial — a plan comparison, a summary of three accounts. Reach for it when the table is the page rather than a part of it
+Never for: Making the text bigger or smaller. It changes how tall a row is and nothing else — the type stays one size down the whole table, because a reader comparing values across three tables at three densities is comparing the values rather than the tables. A table too wide for its column scrolls, and a smaller size only makes the same problem harder to read
+
+Also accepts everything from `HTMLAttributes<HTMLTableRowElement>`.
+
+## 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: `row`
+- a selected row says so to a screen reader as well as to the eye, which aria-selected on the row supplies. A fill is drawn and never announced, so a reader who cannot see it is told nothing about which rows are in the set
+- the row holds one cell per column, in the same order as every other row. A short row shifts every value after it under the wrong header for anyone reading a cell at a time
+
+## 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.
+
+## Anti-examples
+
+❌ TableRow for: The whole row is a target that navigates
+   A row that is one press is a different component: it takes focus, announces itself as a control and forbids the controls inside it. A table row holds cells, and cells hold links and buttons of their own — making the row pressable would make every one of them unreachable
+   → use `CardButton` instead.
+
+## Example
+
+```tsx
+import { TableRow, TableCell } from '@deriv-com/dds-marketing'
+
+<TableRow>
+  <TableCell>Alice Johnson</TableCell>
+  <TableCell>alice@example.com</TableCell>
+  <TableCell>Engineer</TableCell>
+</TableRow>
+```
+
+## In use
+
+Most rows below hold the same set, written once here:
+
+```tsx
+import { TableCell } from '@deriv-com/dds-marketing'
+
+const tablecells = (
+  <>
+    <TableCell>Alice Johnson</TableCell>
+    <TableCell>alice@example.com</TableCell>
+    <TableCell>Engineer</TableCell>
+  </>
+)
+```
+
+### Picked, and not
+
+Selection is a fact about the row, so it is drawn here rather than on the checkbox that sets it — a reader scanning sees the set without checking every box.
+
+```tsx
+import { TableRow } from '@deriv-com/dds-marketing'
+
+// An ordinary row
+<TableRow selected={false}>{tablecells}</TableRow>
+
+// Picked — a wash, not an outline
+<TableRow selected>{tablecells}</TableRow>
+```
+
+### Under the pointer
+
+A wash saying which row a press would land on. Gated to devices that have a pointer, because a touch screen reports a hover that never ends.
+
+```tsx
+import { TableRow } from '@deriv-com/dds-marketing'
+
+// hoverable
+<TableRow hoverable>{tablecells}</TableRow>
+
+// Read-only
+<TableRow hoverable={false}>{tablecells}</TableRow>
+```
+
+### Dividers
+
+Handed to the cells, which draw the line above themselves — a row cannot, its borders not being painted once a table separates them.
+
+```tsx
+import { TableRow } from '@deriv-com/dds-marketing'
+
+// rows
+<TableRow dividers="rows">{tablecells}</TableRow>
+
+// grid
+<TableRow dividers="grid">{tablecells}</TableRow>
+
+// none
+<TableRow dividers="none">{tablecells}</TableRow>
+```
+
+### Row density
+
+Taken from the section above and handed to every cell, so a row's air and its cells' padding are one decision.
+
+```tsx
+import { TableRow } from '@deriv-com/dds-marketing'
+
+// sm
+<TableRow size="sm">{tablecells}</TableRow>
+
+// md
+<TableRow size="md">{tablecells}</TableRow>
+
+// lg
+<TableRow size="lg">{tablecells}</TableRow>
+```
+
+### When a value is too long
+
+Passed to every cell in the row, so one long value does not behave differently from the ones beside it.
+
+```tsx
+import { TableCell, TableRow } from '@deriv-com/dds-marketing'
+
+// wrap
+<TableRow overflow="wrap">
+  <TableCell>Charlotte Featherstonehaugh-Willoughby</TableCell>
+  <TableCell>charlotte@example.com</TableCell>
+  <TableCell>Engineer</TableCell>
+</TableRow>
+
+// truncate
+<TableRow overflow="truncate">
+  <TableCell>Charlotte Featherstonehaugh-Willoughby</TableCell>
+  <TableCell>charlotte@example.com</TableCell>
+  <TableCell>Engineer</TableCell>
+</TableRow>
+```
+
+### The case of the names it holds
+
+Passed to the cells. Only a header cell draws it; a data cell has no case decision.
+
+```tsx
+import { TableRow } from '@deriv-com/dds-marketing'
+
+// upper — capitals
+<TableRow selected={false} headerCase="upper">{tablecells}</TableRow>
+
+// title — as written
+<TableRow selected={false} headerCase="title">{tablecells}</TableRow>
+```

package/.llm/components/tablist.md

@@ -0,0 +1,210 @@
+<!-- GENERATED from tab-list.contract.json. Do not edit. -->
+
+# TabList
+
+A strip of comparable versions of one thing, one of them showing at a time. What it says is that these are the same offer seen differently — a billing period, a platform, a market class — rather than places the site has. Two at least: selected means selected against something, and a strip of one is a heading that highlights.
+
+It holds which tab is current and nothing else. The content each tab reveals belongs to the page, because a marketing page already has all of it written and the strip is only deciding which slice shows. That is why there is no panel here and no ARIA tab role: role="tab" is a promise about a tabpanel this component cannot see, and a promise it cannot keep is worse than the group it actually is.
+
+## Use when
+
+- Two or three versions of one offer differ in a way a reader wants to compare — monthly against yearly, one platform against another
+- The page has already written every version, and showing them at once would be repetition rather than information
+- The reader's choice changes what they see and nothing else — no route, no account, nothing the page has to remember
+
+## Do not use
+
+- The sections are separate topics rather than versions of one thing → `Accordion`
+- Every version is worth reading → `Card`
+- The tabs would go to other pages → nothing here does this
+- Navigation. This is a group of buttons, not a landmark: nothing here carries an href, and a strip whose items led away would be a menu drawn as a comparison
+- A sequence. Tabs are alternatives and are pressed in any order — steps happen in one, and a strip says otherwise to everyone who reads it
+- One tab. A set of one is a heading with a border, and the selected state marks it against nothing
+- More than about four. A strip is scanned across in a glance, and the point at which a reader has to read it to choose is the point it should have been a list
+
+## Anatomy
+
+TabList renders 3 elements. A token binding names the part it applies to.
+
+- `root` — `<div>`, class `dds-tablist`. The strip, and the thing that knows which tab is current. A tab cannot see its siblings, so `selected` is injected rather than asked for — left to themselves every tab would answer for itself and all of them would show as current. Accordion owns which row is open for the same reason, and seeds itself the same way: a strip given no `value` takes its first answer from whichever tab arrived selected, falls back to the first tab when none did, and moves it itself from then on. A strip is always showing one of its slices, so it always marks one — a strip marking nothing is a page whose content has no heading over it.
+  
+  It draws the rail: a hairline along the bottom at `border.width.default` in `color.border.subtle`, which the tabs sit on and the bar covers where one is current. Product's carries a `divider` axis to turn it off; there is one strip here and it always has its rail, because a marketing page is white and a strip with no line under it is a row of words nobody reads as a control.
+  
+  `role="group"` with a name, which is the honest role for what this is. Not `role="tablist"`: that names a widget whose tabs own panels through `aria-controls`, and the panels here belong to the page. Not `role="navigation"` either, which is where this parts company with Product's — a landmark says the items go places, and these change what is showing on the page the reader is already on.
+- `list` — `<div>`, class `dds-tablist__list`. The row the tabs sit in, and the box the bar is positioned against. It scrolls sideways rather than wrapping: a strip that wrapped to two lines is no longer a row to scan across, and on a phone a fourth tab has to go somewhere.
+  
+  It is the positioned ancestor, which is what makes the bar's offsets content-relative — so the mark travels with the scroll instead of needing it subtracted. Its bottom padding is the bar's own thickness, keeping the bar inside the scroll container rather than hanging past it where the overflow would clip it or earn a second scrollbar.
+- `indicator` — `<span>`, class `dds-tablist__indicator`. One bar, moved rather than switched. `border.width.thick` of `color.bg.brand`, rounded at `radius.pill`, measured to the width of the current tab's content — the words rather than the pill, so it does not run out under the padding either side.
+  
+  Rendered whether or not anything is current, because it is a declared part and the generated test asserts every one of those reaches the DOM. Hidden when there is nothing to mark, which keeps it out of the accessibility tree as well as off the screen.
+  
+  It is decoration and announces nothing. What it marks is said by the tab itself, which carries `aria-current` — a reader who cannot see the bar is told which version they are on rather than left to infer it from a mark they have no access to.
+  
+  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 leaves the bar in the render tree with nothing to mark. 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 `tabListParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `Tab`
+- Never contains: `TabList`, `Accordion`, `AccordionItem`, `Card`, `CardButton`, `Button` — in children or in any prop that takes a node
+- Holds at least 2
+
+## Props
+
+### label — `string` **Required.**
+
+Use when: Always — a group with no name is a group a screen reader announces as nothing, and the reader is told there is a set without being told what it is a set of. Name what the tabs switch between rather than the act of switching: 'Billing period', not 'Choose a billing period'
+Never for: A heading. This is the group's accessible name and it is not drawn — a strip that needs a visible heading gets one on the page above it, which is a heading a sighted reader can see too
+
+### value — `string`
+
+Use when: The page is holding which tab is current, because the choice also drives what is rendered beneath the strip — the ordinary case here. Passing it makes the strip controlled: it shows what it is told and reports presses through onChange.
+
+Leave it off and the strip holds its own answer, seeded from whichever tab arrived selected and from the first tab when none did. That is for a strip whose slices are all on the page already and only need showing one at a time, and it is what Accordion does with its rows.
+Never for: Half of a controlled strip. A value passed without an onChange to move it is a strip that cannot respond to being pressed — which reads as a broken control rather than a fixed one, and 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 pressed tab's value after that tab's own onSelect, so a tab that reports its own presses keeps doing so inside a set
+Never for: Side effects a press should not have. This says which version the reader is looking at; a strip 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: `group`
+- `Tab` — Moves to each tab in turn. A group of buttons is not a composite widget, so there is no roving tabindex and no arrow keys to learn — the reader keeps the key they already have, and nothing traps them inside the strip
+- accessible name from label, so a reader entering the group is told what these are versions of rather than that a group exists
+- The group takes no focus of its own. Focus belongs to the tabs, which are buttons and are reached with the tab key; a strip that took focus would be a stop that does nothing.
+- A value naming no tab selects none of them rather than falling back to the first. This is what the strip does when a page asks for a version it does not have — a mistake worth showing rather than papering over, not an arrangement to build on purpose. A strip nobody has given a value at all marks its first tab, because it is showing that tab's slice.
+- The panels belong to the page, and so does wiring them. This group makes no aria-controls claim because it can see no panel — a page that wants the tab and its content associated says so itself, and role="tablist" here would have promised it.
+
+## 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.
+
+## Anti-examples
+
+❌ TabList for: The sections are separate topics rather than versions of one thing
+   These are the two components here that answer "there is more than fits", and they answer different questions. An accordion is a list of topics a reader picks one of; a strip is one topic in several forms a reader compares. A set of unrelated topics behind tabs tells a reader a comparison exists that does not
+   → use `Accordion` instead.
+
+❌ TabList for: Every version is worth reading
+   A reader skimming a landing page does not press anything, so a strip is a decision to make some of the page optional. Two cards side by side is how a page shows both at once and is read by someone who never touches it
+   → use `Card` instead.
+
+❌ TabList for: The tabs would go to other pages
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+## Example
+
+```tsx
+import { TabList, Tab } from '@deriv-com/dds-marketing'
+
+<TabList label="Billing period">
+  <Tab value="label-1" label="Label 1" selected onSelect={(value) => { /* your handler */ }} />
+  <Tab value="label-2" label="Label 2" onSelect={(value) => { /* your handler */ }} />
+  <Tab value="label-3" label="Label 3" onSelect={(value) => { /* your handler */ }} />
+</TabList>
+```
+
+```tsx
+import { useState } from 'react'
+import { TabList, Tab } from '@deriv-com/dds-marketing'
+
+// Controlled: TabList reports the value, not the event.
+const [value, setValue] = useState('')
+<TabList label="Billing period" value={value} onChange={setValue}>
+  <Tab value="label-1" label="Label 1" selected onSelect={(value) => { /* your handler */ }} />
+  <Tab value="label-2" label="Label 2" onSelect={(value) => { /* your handler */ }} />
+  <Tab value="label-3" label="Label 3" onSelect={(value) => { /* your handler */ }} />
+</TabList>
+```
+
+## In use
+
+### A comparison, not a menu
+
+Two versions of one offer. The page renders the matching slice beneath — the strip decides nothing else and owns no panel.
+
+```tsx
+import { Tab, TabList } from '@deriv-com/dds-marketing'
+
+// Yearly current
+<TabList label="Billing period">
+  <Tab value="monthly" label="Monthly" onSelect={(value) => { /* your handler */ }} />
+  <Tab value="yearly" label="Yearly" selected onSelect={(value) => { /* your handler */ }} />
+</TabList>
+
+// Monthly current
+<TabList label="Billing period">
+  <Tab value="monthly" label="Monthly" selected onSelect={(value) => { /* your handler */ }} />
+  <Tab value="yearly" label="Yearly" onSelect={(value) => { /* your handler */ }} />
+</TabList>
+```