@deriv-com/dds-marketing 0.2.0 → 1.0.1

package/.llm/components/tablist.md

@@ -96,7 +96,7 @@ This is the phone's breakpoint, size.breakpoint.md, and not the wider one that d
 
 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.
+- **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, CardButton and TextInput 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.
 
@@ -148,6 +148,14 @@ The target and the mark are separate decisions, and conflating them is what prod
 
 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
 

package/.llm/components/testimonialrow.md

@@ -0,0 +1,235 @@
+<!-- GENERATED from testimonial-row.contract.json. Do not edit. -->
+
+# TestimonialRow
+
+A section that lets a review service's numbers back the page: a heading with the overall rating under it — and a way to where the reviews were collected — over a row of rated reviews the reader moves along, each a short review under its star rating with the reviewer's name, and two arrows under the row that step it a card at a time. Several are in view at once and nothing moves on its own.
+
+The reference design's Testimonial in its review-row form. It names no review platform: the score, its wording and where it links are the page's, so the same section serves whichever service the reviews came from.
+
+## Use when
+
+- Five to ten short, rated reviews collected by a review service, where seeing several at once is the point and the overall score is worth stating
+- A page that has made its claims and wants customers' own ratings to back them — a homepage's "What our customers say"
+
+## Do not use
+
+- Two to five quotes the page chose, from partners or customers, each a few sentences and read one at a time → `TestimonialSlider`
+- A single review → `FeatureSplit`
+- Reviews nobody wrote, or a rating nobody gave. The stars and the summary are a score in a review service's name — keep each rating and the overall score in step with the source, and link to it, or leave them out
+- A review service's own marks. Its logo, wordmark and brand colour belong to its own widget, under its own rules; this draws each card's stars in the page's accent and names the service in words
+- Long reviews. A card is read on the way along the row; one that needs more than a sentence or two is a review the reader skips
+
+## Anatomy
+
+TestimonialRow renders 20 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-testimonialrow`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, which is what the row's breakout and the cards' share of it are measured against. A region named by its heading.
+- `inner` — `<div>`, class `dds-testimonialrow__inner`. The measure and the gutter, the same column every band holds its content in.
+- `header` — `<div>`, class `dds-testimonialrow__header`. The heading and the overall rating under it, FeatureCards' header and its arrangement: ranged to the start on a phone and centred from the fold. It sets no gap: each part's own margin is the step.
+- `title` — `<h2>`, class `dds-testimonialrow__title`. Whose reviews these are. `h2`, ranged to the start on a phone and centred from the fold with the rating under it, as every other block's heading is.
+- `summary` — `<p>`, class `dds-testimonialrow__summary`. The overall rating, in the page's words, under the heading as the section's description: a standalone Link to where the reviews were collected when the summary gives an `href` — brand ink and a mark, taking the band's ink on the dark band — or plain words without one. Held to the description measure. Drawn only for a section given a `summary`. Rendered only when `summary` is set.
+- `carousel` — `<div>`, class `dds-testimonialrow__carousel`. The row and the footer under it, held together at space.gap.xl — closer than the section's own step from the heading, so the arrows read as belonging to the row.
+- `track` — `<div>`, class `dds-testimonialrow__track`. The row: the cards side by side at space.grid.gutter, the space between cards wherever they sit, scrolling across with a stop at each card. It runs out to the band's edges while its first card lines up with the heading — a gutter on the row itself that scrolls away with it, so a card is cut off by the band rather than by the column. A named group with a tab stop of its own, Scroller's rule, so a keyboard can reach the cards a pointer scrolls to. No scrollbar: the arrows under it are the standing sign that it moves.
+- `review-link` — `<a>`, class `dds-testimonialrow__review-link`. For a review that gives an `href`: the whole card is a link to it, wrapping the card's figure, opening in a new tab. It is what takes the row's measure. Its name is the card's words — stars, review and reviewer — which is what a reader is choosing between. Lifts on hover the way CardButton does.
+- `item` — `<figure>`, class `dds-testimonialrow__item`. One review, in a card: a `figure`, so the words and the person they are attributed to are one thing to assistive technology. The card's fill follows the ground — see `ground`. Most of the column on a phone, two and a half across from the fold and three and a half from 64rem, so one is always cut off; every card as tall as the row and never shorter than size.review-card.min, its stars above the words and the reviewer's name at its foot.
+- `rating` — `<span>`, class `dds-testimonialrow__rating`. A card's five stars, filled to its rating — whole and half stars — in the brand's accent. One image to assistive technology, named by `ratingLabel`, so it is heard as a score rather than as five pictures. Drawn only for a review that gives a rating.
+- `star` — `<span>`, class `dds-testimonialrow__star`. One star: an empty star with a filled one laid over it in the same cell. A half star clips the fill to its first half — the right half in a right-to-left page.
+- `star-track` — `<svg>`, class `dds-testimonialrow__star-track`. The empty star, in the accent at opacity.track — the track the fill travels over, drawn in one colour with it so it reads on every ground and in both themes without a colour of its own.
+- `star-fill` — `<svg>`, class `dds-testimonialrow__star-fill`. The filled star, in the accent at full strength. Drawn only for a star the rating reaches.
+- `quote` — `<blockquote>`, class `dds-testimonialrow__quote`. What was said, at the body step. It fills the card, so the reviewer's name sits at the foot of every card in the row.
+- `author` — `<figcaption>`, class `dds-testimonialrow__author`. Who wrote it: their name, and where they are if the review gives it.
+- `name` — `<span>`, class `dds-testimonialrow__name`. Who wrote it — the name the review service shows.
+- `detail` — `<span>`, class `dds-testimonialrow__detail`. Where they are, quieter than the name. Drawn only for a review that gives one. Muted on the page and the grey band; on the dark band it takes color.fg.muted-inverse, the band's own quieter ink.
+- `footer` — `<div>`, class `dds-testimonialrow__footer`. The arrows, back in the column under the row. Ranged to the start on a phone, with the heading and the cards; centred from the fold, so the way through the row sits under the middle of it. Drawn only for two reviews or more: one review has no arrows, and an empty footer would still open the gap under the row.
+- `nav` — `<div>`, class `dds-testimonialrow__nav`. Two ButtonIcons in their secondary variant — Button's secondary drawn as a circle, and a carousel's two directions, the case that variant names — stepping the row back and on by one card and the gap after it. Drawn for two reviews or more, and hidden while the row has nowhere to go in either direction. On the dark band they take the inverse tone, which keeps the tint and turns it white.
+- `nav-slot` — `<span>`, class `dds-testimonialrow__nav-slot`. Where one arrow stands. At either end of the row the arrow that has nowhere to go stays in its slot, receded to opacity.disabled and inert — so both directions show from the first render, the pair keeps its width and does not shift as the reader scrolls, and a keyboard never lands on a control that does nothing. ButtonIcon has no disabled state, by its own ruling, which is why this is its slot's job.
+
+Apply these classes from the generated `testimonialRowParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `TestimonialRow`, `TestimonialSlider`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white. The cards are the recessed gray that sets them off
+- `subtle` — The grey band, the reference design's ground for this section. The cards turn white on it. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section
+- `strong` — `color.bg.brand-strong`, the dark band, for a section a reader should arrive at. The heading, the summary and the cards' words turn white, and the cards take color.bg.surface-card-strong — gray.900 in both themes, the colour a page card takes in dark mode — so the band reads as a dark-mode section in either theme. The arrows take ButtonIcon's inverse tone
+
+Use when: Which of the page's grounds the section paints, and with it the cards' fill: the recessed surface on the page, the raised white on the grey band — the reference design's slate band — and the strong card on the dark band, gray.900 in both themes.
+Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left. And never a dark card on the dark band: a few sentences of white on dark gray is a paragraph a reader works through rather than a quote they take in.
+
+### title — `string` **Required.**
+
+Use when: Always. Whose reviews these are, in a few words — "What our customers say".
+Never for: A review, or the score. The reviews are the content and the summary states the score; the heading says whose they are.
+
+### reviews — `data` `TestimonialRowReview[]` **Required.**
+
+Use when: Always. The reviews, in the order they run along the row — five to ten of a sentence or two, each with the reviewer's name, its `rating` and, where there is one, the `href` of the review itself. An empty list draws nothing.
+Never for: A review that was not written by the person named, or a rating changed from the one they gave.
+
+### summary — `data` `TestimonialRowSummary`
+
+Use when: The overall rating, in the page's own words under the heading — "Rated 4.5 out of 5 on our review site" — as a standalone Link to where the reviews were collected when it has an `href`. Words rather than stars: they name the service, they are translated with the page, and the score is stated once rather than drawn beside a sentence that already says it.
+Never for: A number the source does not show today.
+
+### ratingLabel — `callback`
+
+Use when: The accessible name of a card's stars, given its rating as drawn — rounded to the nearest half, so what is heard is what is seen. The stars are drawn rather than written, so this is what a screen reader hears for them. Without it they are named "Rated 5 out of 5"; pass it to translate that with the page.
+Never for: Visible text. It names the stars to assistive technology and is never drawn.
+
+### label — `string` (default `Reviews`)
+
+Use when: The name the row is announced by. The row is a scrolling region a keyboard has to be able to reach, so it carries a tab stop and a name of its own — Scroller's rule. Its own name rather than the section's, so a screen reader moving into it hears what it is. Translate it with the page.
+
+### previousLabel — `string` (default `Previous reviews`)
+
+Use when: The accessible name of the arrow stepping the row back. A glyph announces nothing, so this is the whole of the control's name. Translate it with the page, and keep it parallel to nextLabel.
+
+### nextLabel — `string` (default `Next reviews`)
+
+Use when: The accessible name of the arrow stepping the row on, for the reason previousLabel exists.
+
+## 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: `region`
+- `Tab` — Moves to the row, then through any review that links, then to the arrows that have somewhere to go.
+- `Enter` — On a review that links, opens it. On an arrow, steps the row by one card.
+- `ArrowLeft` — On the focused row: scrolls it the way the key points — the browser's own scrolling, made reachable by the row's tab stop. Towards the start in a left-to-right page, towards the end in a right-to-left one.
+- `ArrowRight` — On the focused row: scrolls it the way the key points, the mirror of ArrowLeft.
+- accessible name from title, so the section is a named region a reader can jump to and skip
+- Each review is a figure holding a blockquote and its figcaption, so the words and the person they are attributed to are announced together.
+- The row is a named group with a tab stop of its own, so a keyboard can reach and scroll it whether or not any review links.
+- Each card's stars are one image named by its rating, and an arrow with nowhere to go is drawn receded and inert rather than left a control 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, CardButton and TextInput 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
+
+❌ TestimonialRow for: Two to five quotes the page chose, from partners or customers, each a few sentences and read one at a time
+   A chosen quote has no score and deserves the reader's full attention; TestimonialSlider shows one at a time, with the name of who said it
+   → use `TestimonialSlider` instead.
+
+❌ TestimonialRow for: A single review
+   One review is not a row; set it beside a picture as a split, or leave the score to the page's own copy
+   → use `FeatureSplit` instead.
+
+## Example
+
+```tsx
+import { TestimonialRow } from '@deriv-com/dds-marketing'
+
+<TestimonialRow title="What our customers say" reviews={[{"quote":"Trading with Deriv has been great. Low spreads, and withdrawals reach me quickly.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/1","detail":"United Kingdom"},{"quote":"An easy, smooth trading experience — the platform does what I need without getting in the way.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/2","detail":"Malaysia"},{"quote":"Support answered my question about deposits within minutes, in my own language.","name":"A Deriv customer","rating":4.5,"href":"https://example.com/reviews/3","detail":"South Africa"},{"quote":"I have used a few brokers. This is the one I stayed with, mostly for the range of markets.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/4","detail":"Brazil"},{"quote":"Clear charts, fast execution and no surprises in the fees.","name":"A Deriv customer","rating":4,"href":"https://example.com/reviews/5","detail":"Nigeria"},{"quote":"Opening an account took a few minutes, and verifying it took less than a day.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/6","detail":"Indonesia"}]} summary={{"label":"Rated 4.5 out of 5 by our customers","href":"https://example.com/reviews"}} />
+```
+
+## In use
+
+### A row of rated reviews
+
+Several short reviews in view at once, each under its stars, in a row that runs to the band's edge — the overall rating under the heading, two arrows under the row. It never moves on its own.
+
+```tsx
+import { TestimonialRow } from '@deriv-com/dds-marketing'
+
+// Reviews with a summary
+<TestimonialRow title="What our customers say" reviews={[{"quote":"Trading with Deriv has been great. Low spreads, and withdrawals reach me quickly.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/1","detail":"United Kingdom"},{"quote":"An easy, smooth trading experience — the platform does what I need without getting in the way.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/2","detail":"Malaysia"},{"quote":"Support answered my question about deposits within minutes, in my own language.","name":"A Deriv customer","rating":4.5,"href":"https://example.com/reviews/3","detail":"South Africa"},{"quote":"I have used a few brokers. This is the one I stayed with, mostly for the range of markets.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/4","detail":"Brazil"},{"quote":"Clear charts, fast execution and no surprises in the fees.","name":"A Deriv customer","rating":4,"href":"https://example.com/reviews/5","detail":"Nigeria"},{"quote":"Opening an account took a few minutes, and verifying it took less than a day.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/6","detail":"Indonesia"}]} summary={{"label":"Rated 4.5 out of 5 by our customers","href":"https://example.com/reviews"}} />
+
+// Without a summary — the heading alone
+<TestimonialRow title="What our customers say" reviews={[{"quote":"Trading with Deriv has been great. Low spreads, and withdrawals reach me quickly.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/1","detail":"United Kingdom"},{"quote":"An easy, smooth trading experience — the platform does what I need without getting in the way.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/2","detail":"Malaysia"},{"quote":"Support answered my question about deposits within minutes, in my own language.","name":"A Deriv customer","rating":4.5,"href":"https://example.com/reviews/3","detail":"South Africa"},{"quote":"I have used a few brokers. This is the one I stayed with, mostly for the range of markets.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/4","detail":"Brazil"},{"quote":"Clear charts, fast execution and no surprises in the fees.","name":"A Deriv customer","rating":4,"href":"https://example.com/reviews/5","detail":"Nigeria"},{"quote":"Opening an account took a few minutes, and verifying it took less than a day.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/6","detail":"Indonesia"}]} />
+```
+
+### The three grounds
+
+The cards are the recessed gray on the page, white on the grey band, and the strong gray.900 card on the dark band — the colour a page card takes in dark mode.
+
+```tsx
+import { TestimonialRow } from '@deriv-com/dds-marketing'
+
+// ground="page"
+<TestimonialRow title="What our customers say" reviews={[{"quote":"Trading with Deriv has been great. Low spreads, and withdrawals reach me quickly.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/1","detail":"United Kingdom"},{"quote":"An easy, smooth trading experience — the platform does what I need without getting in the way.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/2","detail":"Malaysia"},{"quote":"Support answered my question about deposits within minutes, in my own language.","name":"A Deriv customer","rating":4.5,"href":"https://example.com/reviews/3","detail":"South Africa"},{"quote":"I have used a few brokers. This is the one I stayed with, mostly for the range of markets.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/4","detail":"Brazil"},{"quote":"Clear charts, fast execution and no surprises in the fees.","name":"A Deriv customer","rating":4,"href":"https://example.com/reviews/5","detail":"Nigeria"},{"quote":"Opening an account took a few minutes, and verifying it took less than a day.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/6","detail":"Indonesia"}]} summary={{"label":"Rated 4.5 out of 5 by our customers","href":"https://example.com/reviews"}} />
+
+// ground="subtle"
+<TestimonialRow title="What our customers say" reviews={[{"quote":"Trading with Deriv has been great. Low spreads, and withdrawals reach me quickly.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/1","detail":"United Kingdom"},{"quote":"An easy, smooth trading experience — the platform does what I need without getting in the way.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/2","detail":"Malaysia"},{"quote":"Support answered my question about deposits within minutes, in my own language.","name":"A Deriv customer","rating":4.5,"href":"https://example.com/reviews/3","detail":"South Africa"},{"quote":"I have used a few brokers. This is the one I stayed with, mostly for the range of markets.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/4","detail":"Brazil"},{"quote":"Clear charts, fast execution and no surprises in the fees.","name":"A Deriv customer","rating":4,"href":"https://example.com/reviews/5","detail":"Nigeria"},{"quote":"Opening an account took a few minutes, and verifying it took less than a day.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/6","detail":"Indonesia"}]} summary={{"label":"Rated 4.5 out of 5 by our customers","href":"https://example.com/reviews"}} ground="subtle" />
+
+// ground="strong"
+<TestimonialRow title="What our customers say" reviews={[{"quote":"Trading with Deriv has been great. Low spreads, and withdrawals reach me quickly.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/1","detail":"United Kingdom"},{"quote":"An easy, smooth trading experience — the platform does what I need without getting in the way.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/2","detail":"Malaysia"},{"quote":"Support answered my question about deposits within minutes, in my own language.","name":"A Deriv customer","rating":4.5,"href":"https://example.com/reviews/3","detail":"South Africa"},{"quote":"I have used a few brokers. This is the one I stayed with, mostly for the range of markets.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/4","detail":"Brazil"},{"quote":"Clear charts, fast execution and no surprises in the fees.","name":"A Deriv customer","rating":4,"href":"https://example.com/reviews/5","detail":"Nigeria"},{"quote":"Opening an account took a few minutes, and verifying it took less than a day.","name":"A Deriv customer","rating":5,"href":"https://example.com/reviews/6","detail":"Indonesia"}]} summary={{"label":"Rated 4.5 out of 5 by our customers","href":"https://example.com/reviews"}} ground="strong" />
+```

package/.llm/components/testimonialslider.md

@@ -0,0 +1,254 @@
+<!-- GENERATED from testimonial-slider.contract.json. Do not edit. -->
+
+# TestimonialSlider
+
+A section that lets the people who use the product say what it did for them: a heading over one quote at a time, in a card, with the name of who said it. Two or more quotes rotate in place — one in view, the next fading in where it stood — and dots show where the reader is and move to any quote pressed.
+
+The reference design's Testimonial in its quote form. Its review-row form — rated reviews collected by a review service — is TestimonialRow.
+
+## Use when
+
+- Two to five real quotes from partners or customers, each a few sentences, read one at a time
+- A page that has made its claims and wants someone other than the brand to back them
+
+## Do not use
+
+- A single quote → `FeatureSplit`
+- Ratings and review counts from a review site → `TestimonialRow`
+- Quotes nobody said. A testimonial is a claim made in someone else's name, and an invented one is a false claim — use real, attributable words or none
+- More than a few sentences per quote. A quote is read while it is in view; one that needs scrolling inside the card is never finished
+
+## Anatomy
+
+TestimonialSlider renders 15 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-testimonialslider`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width. A region named by its heading, announced as a carousel when it rotates, so a reader can jump to it and past it and knows it moves.
+- `inner` — `<div>`, class `dds-testimonialslider__inner`. The measure and the gutter, the same column every band holds its content in.
+- `title` — `<h2>`, class `dds-testimonialslider__title`. Whose words these are. `h2`, ranged to the start on a phone and centred from the fold with the card under it, as every other block's heading is.
+- `carousel` — `<div>`, class `dds-testimonialslider__carousel`. The card and the dots under it, held together at space.gap.xl — the reference design's step from the card to its dots, and closer than the section's own step from the heading, so the dots read as belonging to the card rather than as a part of the section.
+- `track` — `<div>`, class `dds-testimonialslider__track`. The quotes, stacked in one place. Every card sits in the same grid cell, so the section is as tall as its longest quote and nothing below it moves when one changes for another. Only the quote in view is drawn; the rest are at opacity.hidden, inert and hidden from assistive technology. A change is a fade in place on motion.duration.slow and motion.easing.shift — the dots' own timing — and the words then arrive the way every block's do. It is also what the two corner pictures are placed against, so they sit over the card whichever quote is in view and do not fade with it, and what keeps them inside the card's rounded corner as they drift.
+- `item` — `<figure>`, class `dds-testimonialslider__item`. One quote, in a card: a `figure`, so the quote and the person it is attributed to are one thing to assistive technology. The card's fill follows the ground — see `ground`. Ranged to the start on a phone and centred from the fold, the reference design's arrangement.
+- `image-start` — `<span>`, class `dds-testimonialslider__image-start`. A picture laid over the card's top start corner, a square at size.testimonial-art, running up behind the card's top edge — by its own corner radius and the whole of its drift, so its top corners never show — and set in from its start side — space.inset.xl from the fold, and space.inset.lg from the end side on a phone, where it moves to the top end corner. No frame of its own — the picture is the art, a PNG with or without a transparent ground — so it sets only its place. Drifts down by motion.distance.drift while the section passes through the view — scroll-driven, so it moves with the reader's scroll and back again — and holds still for a reader who asked for less motion or a browser with no scroll timeline. Decorative: hidden from assistive technology, and nothing a pointer can land on. The one shown on a phone, moved to the top end corner above the quote — the side a start-aligned quote leaves empty — and drifting half as far, so less of it has to stay tucked away. Rendered only when `imageStart` is set.
+- `image-end` — `<span>`, class `dds-testimonialslider__image-end`. imageStart's pair at the card's bottom end corner, running down behind the card's bottom edge the same way and set in from its end side by space.inset.xl, drifting up as the other drifts down. Not drawn on a phone, where there is room for one picture and it is the opening one. Rendered only when `imageEnd` is set.
+- `image` — `<img>`, class `dds-testimonialslider__image`. The picture in each corner — inside image-start and inside image-end alike — square — cropped to fill it, so any picture is 1:1 whatever shape it arrives in — with its corners rounded at radius.container-item. No border and no ground behind it, so a PNG with a transparent ground shows the card through it. An empty alt: the box around it is hidden from assistive technology, and it is decoration.
+- `quote` — `<blockquote>`, class `dds-testimonialslider__quote`. What was said, at the large body step and held to the description measure.
+- `author` — `<figcaption>`, class `dds-testimonialslider__author`. Who said it: their picture, if there is one, beside their name and what they do.
+- `avatar` — `<img>`, class `dds-testimonialslider__avatar`. The person's picture, round at size.avatar. Decorative — the name beside it says who it is — so it takes an empty alt. Drawn only for a quote that gives one.
+- `name` — `<span>`, class `dds-testimonialslider__name`. Who said it.
+- `detail` — `<span>`, class `dds-testimonialslider__detail`. Where they are or what they do, quieter than the name. Drawn only for a quote that gives one. Muted on the page and the grey band; on the dark band it takes color.fg.muted-inverse, the band's own quieter ink.
+- `controls` — `<div>`, class `dds-testimonialslider__controls`. PaginationDots, in its accent variant — coral marks in the brand's accent — under the card: where the reader is, and a way to any quote. Ranged to the start on a phone with the quote above it, centred from the fold with the card. With the swipe, the whole of how a reader moves it.
+
+Apply these classes from the generated `testimonialSliderParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `TestimonialSlider`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white. The card is the recessed gray that sets it off
+- `subtle` — The grey band, the reference design's ground for this section. The card turns white on it. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section
+- `strong` — `color.bg.brand-strong`, the dark band, for a section a reader should arrive at. The heading and the quote turn white and the card takes color.bg.surface-card-strong — gray.900 in both themes, the colour a page card takes in dark mode, and TestimonialRow's card on the same band — so the band reads as a dark-mode section in either theme. The coral dots sit on it
+
+Use when: Which of the page's grounds the section paints, and with it the card's fill: the recessed surface on the page, the raised white on the grey band — the reference design's slate testimonial — and the strong card on the dark band, gray.900 in both themes, so the card has an edge on each.
+Never for: Marking importance. Every section on a page painted a ground is a page with no emphasis left.
+
+### title — `string` **Required.**
+
+Use when: Always. Whose words these are, in a few — "What our partners say", "What our customers say".
+Never for: A quote. The quotes are the content; the heading says whose they are.
+
+### quotes — `data` `TestimonialSliderQuote[]` **Required.**
+
+Use when: Always. The quotes, in the order they rotate — two to five, each a few sentences, each with the name of who said it. An empty list draws nothing; one quote is drawn still, with no dots.
+Never for: A quote that was not said. Every one is attributed to a person or a role, and the page is answerable for each.
+
+### imageStart — `string`
+
+Use when: A decorative picture, laid over the card's top start corner — a photograph, a product screen, any small piece of art, usually a PNG — as a path or a URL. It is drawn as it is, with rounded corners and no frame, so a transparent ground shows the card through it. Drawn square and cropped to fill its square, so a picture whose subject sits in its middle crops best. It runs up behind the card's top edge, so the edge cuts straight across it, set in from the side, stays put while the quotes rotate, and drifts down by motion.distance.drift as the section passes through the view. The one shown on a phone, where it moves to the top end corner above the quote and drifts half as far, so more of it shows. Decorative: it takes an empty alt and is hidden from assistive technology.
+Never for: Anything a reader needs: a logo that says who the quotes are from, words, the face of the person quoted. It is hidden from assistive technology so it is art or it is missing.
+
+### imageEnd — `string`
+
+Use when: A decorative picture at the card's bottom end corner, the pair to imageStart: drawn the same way behind the card's bottom edge, and drifting up as the other drifts down, so the two read as depth. Drawn from the fold only: a phone has room for one, and it is the opening one. Decorative, as imageStart is.
+Never for: The same as imageStart's: art only.
+
+### autoplay — `boolean` (default `false`)
+
+Use when: Whether it advances on its own, holding each slide for motion.duration.dwell. Off by default, so a slider nobody configured stays still. On, it holds while the pointer is over it or focus is inside it, never moves for a reader who asked for less motion, and stops for good once the reader presses anything in it — a slide, its action, a dot — or swipes it. A press stops it for good — the WAI carousel pattern's rule that a reader who has interacted is reading, not watching. That gives a reader a way to stop the rotation, which WCAG 2.2.2 asks for, but not a visible one: nothing says a press will stop it, so a page that needs 2.2.2 met plainly should still offer its own pause, or leave autoplay off.
+Never for: A banner whose slides carry more than a reader can take in during motion.duration.dwell — turn it off rather than shorten the copy to fit the timer.
+
+### controlsLabel — `string` (default `Testimonials`)
+
+Use when: The name the dots are announced by. Its own name rather than the section's, so a screen reader moving into the dots hears what they are. Translate it with the page.
+
+### slideLabel — `string` (default `Slide`)
+
+Use when: The word each dot is announced by, before its number — 'Slide 2'. Translate it with the page, as controlsLabel is; a page that translates only the group's name still has every dot announced in English.
+
+## 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: `region`
+- `Tab` — Moves to the dots, past the quotes: a quote holds nothing to press. Quotes out of view are inert.
+- `Enter` — On a dot, moves to that quote
+- accessible name from title, so the section is a named region a reader can jump to and skip
+- Each quote is a figure holding a blockquote and its figcaption, so the words and the person they are attributed to are announced together.
+- Every quote out of view is inert and hidden from assistive technology, and the one in view is named by its position — '2 / 3'.
+- Under autoplay, a hold while the pointer is over the section or focus is inside it, no movement for a reader who asked for less motion, and a stop for good once the reader presses anything in it or swipes it — CtaBannerSlider's rules, shared through use-rotation.
+- The corner pictures are decorative: an empty alt and hidden from assistive technology, so the quotes are announced without them.
+
+## 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, CardButton and TextInput 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
+
+❌ TestimonialSlider for: A single quote
+   One quote does not rotate; set it beside a picture of the person as a split, or let it close a section on its own
+   → use `FeatureSplit` instead.
+
+❌ TestimonialSlider for: Ratings and review counts from a review site
+   Reviews a service collected carry a rating each and an overall score, and are read as a set rather than one at a time; this block draws quotes the page chose, with no score
+   → use `TestimonialRow` instead.
+
+## Example
+
+```tsx
+import { TestimonialSlider } from '@deriv-com/dds-marketing'
+
+<TestimonialSlider title="What our partners say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka"},{"quote":"It was only once my account managers reached out and showed me how to make the most of the programme that I really began to grow.","name":"Deriv partner","detail":"Nigeria"},{"quote":"Payouts arrive when they should, every time. That reliability is why I recommend Deriv to the traders I work with.","name":"Deriv partner","detail":"Malaysia"}]} imageStart="/sample-card-image.svg" imageEnd="/sample-card-image.svg" />
+```
+
+## In use
+
+### Rotating between quotes
+
+One quote in view, dots to move between them. It holds while hovered or focused, stops once pressed, and stays still for a reader who asked for less motion.
+
+```tsx
+import { TestimonialSlider } from '@deriv-com/dds-marketing'
+
+// Three quotes, rotating
+<TestimonialSlider title="What our partners say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka"},{"quote":"It was only once my account managers reached out and showed me how to make the most of the programme that I really began to grow.","name":"Deriv partner","detail":"Nigeria"},{"quote":"Payouts arrive when they should, every time. That reliability is why I recommend Deriv to the traders I work with.","name":"Deriv partner","detail":"Malaysia"}]} autoplay />
+
+// Moved by hand only
+<TestimonialSlider title="What our partners say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka"},{"quote":"It was only once my account managers reached out and showed me how to make the most of the programme that I really began to grow.","name":"Deriv partner","detail":"Nigeria"},{"quote":"Payouts arrive when they should, every time. That reliability is why I recommend Deriv to the traders I work with.","name":"Deriv partner","detail":"Malaysia"}]} />
+
+// One quote, drawn still
+<TestimonialSlider title="What our partners say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka"}]} />
+```
+
+### The three grounds
+
+The card is the recessed gray on the page, white on the grey band, and the strong gray.900 card on the dark band — the colour a page card takes in dark mode.
+
+```tsx
+import { TestimonialSlider } from '@deriv-com/dds-marketing'
+
+// ground="page"
+<TestimonialSlider title="What our partners say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka"},{"quote":"It was only once my account managers reached out and showed me how to make the most of the programme that I really began to grow.","name":"Deriv partner","detail":"Nigeria"},{"quote":"Payouts arrive when they should, every time. That reliability is why I recommend Deriv to the traders I work with.","name":"Deriv partner","detail":"Malaysia"}]} />
+
+// ground="subtle"
+<TestimonialSlider ground="subtle" title="What our partners say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka"},{"quote":"It was only once my account managers reached out and showed me how to make the most of the programme that I really began to grow.","name":"Deriv partner","detail":"Nigeria"},{"quote":"Payouts arrive when they should, every time. That reliability is why I recommend Deriv to the traders I work with.","name":"Deriv partner","detail":"Malaysia"}]} />
+
+// ground="strong"
+<TestimonialSlider ground="strong" title="What our partners say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka"},{"quote":"It was only once my account managers reached out and showed me how to make the most of the programme that I really began to grow.","name":"Deriv partner","detail":"Nigeria"},{"quote":"Payouts arrive when they should, every time. That reliability is why I recommend Deriv to the traders I work with.","name":"Deriv partner","detail":"Malaysia"}]} />
+```
+
+### With a picture of who said it
+
+An avatar beside the name, round at size.avatar. Decorative: the name says who it is.
+
+```tsx
+import { TestimonialSlider } from '@deriv-com/dds-marketing'
+
+// With an avatar
+<TestimonialSlider title="What our customers say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka","avatar":"/sample-card-image.svg"},{"quote":"It was only once my account managers reached out and showed me how to make the most of the programme that I really began to grow.","name":"Deriv partner","detail":"Nigeria","avatar":"/sample-card-image.svg"},{"quote":"Payouts arrive when they should, every time. That reliability is why I recommend Deriv to the traders I work with.","name":"Deriv partner","detail":"Malaysia","avatar":"/sample-card-image.svg"}]} />
+```
+
+### With pictures in the corners
+
+Two decorative pictures in opposite corners that drift against the scroll — the top one down, the bottom one up. A phone shows only the top one.
+
+```tsx
+import { TestimonialSlider } from '@deriv-com/dds-marketing'
+
+// With corner pictures
+<TestimonialSlider title="What our partners say" quotes={[{"quote":"I was searching for a trading platform when I found Deriv. The more I read, the more I learned — not only about trading forex here, but about the partner programme too.","name":"Deriv partner","detail":"Sri Lanka"},{"quote":"It was only once my account managers reached out and showed me how to make the most of the programme that I really began to grow.","name":"Deriv partner","detail":"Nigeria"},{"quote":"Payouts arrive when they should, every time. That reliability is why I recommend Deriv to the traders I work with.","name":"Deriv partner","detail":"Malaysia"}]} imageStart="/sample-card-image.svg" imageEnd="/sample-card-image.svg" />
+```