@deriv-com/dds-marketing 0.2.0 → 1.0.1

package/.llm/components/divider.md

@@ -95,7 +95,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.
 
@@ -147,6 +147,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/dropdownmenu.md

@@ -6,7 +6,7 @@ A button that opens a short set of destinations. Pressing one goes somewhere and
 
 It is the host MenuItem was written against. A row whose role is menuitem means nothing to a screen reader outside an element whose role is menu, so until this landed MenuItem was a contract and a stylesheet waiting for one. What this adds is everything a row cannot know about itself: that there is a set, how long it is, which one the reader is on, and that Escape puts them back on the button they pressed.
 
-The trigger is drawn here by default rather than passed in, which is where this parts company with product's menu of the same name. There the trigger is a Button handed over, on the argument that Button is where a button is decided. Marketing's Button cannot take that job: it is an anchor with a required href — a link, always — and a link that opens a menu is a link that does not navigate. ButtonIcon renders a real button but takes no words, and a set of destinations is chosen by reading them. So there is no button-with-words in this package to hand in, and the trigger is this component's to draw. That argument still holds and is the reason the drawn trigger is the default. What it does not cover is a trigger with no words at all: A control with no words is exactly what the paragraph above rules out for a set of destinations, and exactly right for a set of page numbers, which are read by their shape rather than their wording. What gets passed is the caller's business — ButtonIcon, or a button they drew themselves, which is what Pagination's break turned out to need. So `trigger` exists for that case — Pagination's break between two runs of pages — and for no other. Pass nothing and this still draws the whole thing, chevron included.
+The trigger is drawn here by default rather than passed in, which is where this parts company with product's menu of the same name. There the trigger is a Button handed over, on the argument that Button is where a button is decided. Marketing's Button could not take that job when this was built: it was an anchor with a required href — a link, always — and a link that opens a menu is a link that does not navigate. It now renders a button when given no href, so that reason no longer holds on its own. ButtonIcon renders a real button but takes no words, and a set of destinations is chosen by reading them. So there is no button-with-words in this package to hand in, and the trigger is this component's to draw. That argument still holds and is the reason the drawn trigger is the default. What it does not cover is a trigger with no words at all: A control with no words is exactly what the paragraph above rules out for a set of destinations, and exactly right for a set of page numbers, which are read by their shape rather than their wording. What gets passed is the caller's business — ButtonIcon, or a button they drew themselves, which is what Pagination's break turned out to need. So `trigger` exists for that case — Pagination's break between two runs of pages — and for no other. Pass nothing and this still draws the whole thing, chevron included.
 
 A marketing page reaches for a menu where a set of destinations is too long to sit in the navigation and too short to deserve a page — the languages a site is published in, the regions it operates in, the pages a long index skipped over. Not for a toolbar of operations: a page has nothing to operate on, which is the whole difference from the menus an application builds.
 
@@ -34,9 +34,9 @@ DropdownMenu renders 6 elements. A token binding names the part it applies to.
   Inline rather than a block, because a menu button sits in a row of other things: a navigation bar, a footer column, the end of a band. A block root would take the width of whatever contains it and put the trigger at the start of an empty line.
 - `trigger` — `<button>`, class `dds-dropdownmenu__trigger`. The button that opens it, drawn here unless one is handed in.
   
-  That is the one structural difference from product's menu, and it is forced rather than chosen: this package's Button is an anchor with a required href, so it is a link and cannot be a trigger; ButtonIcon is a real button and has no words. A set of destinations is chosen by reading them, so the trigger needs words, and nothing in this package draws a button with words. Drawing one here is the only honest answer left — and it is confined to this component rather than offered as a new button, because the moment it takes a variant it is a second place a button is decided.
+  That is the one structural difference from product's menu, and it was forced rather than chosen: when this was built, this package's Button was an anchor with a required href, so it was a link and could not be a trigger; ButtonIcon is a real button and has no words. A set of destinations is chosen by reading them, so the trigger needs words, and nothing in this package draws a button with words. Drawing one here is the only honest answer left — and it is confined to this component rather than offered as a new button, because the moment it takes a variant it is a second place a button is decided.
   
-  It wears the secondary button's look — an outlined pill, no fill — and takes no variant to change it. A menu of supporting destinations is not the step a page was built to produce, so the brand fill would be the one thing on the band claiming to be the point, and `one-primary-per-view` is the rule that says why. One look, because there is one job.
+  It wears the secondary button's look — an outlined pill, no fill — and takes no variant to change it. A menu of supporting destinations is not the step a page was built to produce, so the brand fill would be the one thing on the band claiming to be the point, and `one-primary-per-action-group` is the rule that says why. One look, because there is one job.
   
   A real `<button>`, with `type="button"` set rather than left to the element's own default of submit: a language picker dropped into a newsletter band would otherwise send the form on the way to opening.
   
@@ -48,7 +48,7 @@ DropdownMenu renders 6 elements. A token binding names the part it applies to.
   
   Plain, it gives up the edge and nothing else. The target is the same size, the ground under a pointer is the same, and the focus ring is untouched — a control that shed its outline and its focus ring together would be one a keyboard reader could no longer find. `border.width.none` against the `border-style: solid` above rather than a second border-style: one property carries the difference, and the style stays where it is so nothing has to be put back.
   
-  And plain, it takes the ink around it rather than naming one. The variant's whole premise is that something else has already said what this is — which means something else has also decided what colour reads on it. `color.fg.default` is a near-black chosen for paper, and a switcher carrying it into a bar standing on a dark hero is the one thing in that bar nobody can read. Link and Button both give up their ink the same way and call it `tone="inherit"`; here it is not a second axis, because a plain control has already given up its edge and its ground and there is no version of it that should keep its own colour.
+  And plain, it takes the ink around it rather than naming one. The variant's whole premise is that something else has already said what this is — which means something else has also decided what colour reads on it. `color.fg.default` is a near-black chosen for paper, and a switcher carrying it into a bar standing on a dark hero is the one thing in that bar nobody can read. Link gives up its ink the same way and calls it `tone="inherit"`; here it is not a second axis, because a plain control has already given up its edge and its ground and there is no version of it that should keep its own colour.
   
   Plain at the small step is the one place the two axes come apart. `size` sets the type and the height together, which is right for a control standing on its own — but a bar wants the smaller type in a finger-sized target, which is exactly what the destinations beside it are: `font.label.sm` in a box of `size.control.md`. Without this the switcher was eight pixels shorter than its neighbours and the difference was invisible until a pointer landed on it and drew a fill that did not match the row.
   
@@ -150,7 +150,7 @@ Never for: A menu whose rows do something on the spot rather than go somewhere.
 ### trigger — `node`
 
 Use when: A control this component should open rather than draw — one whose mark is the whole of it, with no words to read. A ButtonIcon is the obvious candidate and not the only one: Pagination's break between two runs of page numbers passes a button of its own, because it has to match the numbered targets either side of it and this package's ButtonIcon has no transparent form to do that with. Given one, `icon` and `label`'s words go unused: what is drawn is what was passed. What this component still supplies is the half a page gets wrong — that the control announces a menu and whether it is open, that Escape returns focus to it, and that the arrow keys move through the rows.
-Never for: Anything that is not a button. A menu opened by a div is a menu a keyboard cannot reach, and one opened by this package's Button is a link that does not navigate — Button is an anchor here, which is the reason this component drew its own trigger to begin with. Nor for a control with words on it, which is what the drawn trigger is already for and does better, the chevron included.
+Never for: Anything that is not a button. A menu opened by a div is a menu a keyboard cannot reach, and one opened by this package's Button with an href is a link that does not navigate — Button was an anchor always when this component drew its own trigger, which is why it did. Nor for a control with words on it, which is what the drawn trigger is already for and does better, the chevron included.
 
 ### open — `boolean`
 
@@ -188,7 +188,7 @@ Guaranteed by the component. Write none of it by hand: the ids these attributes
 - shutting returns focus to the trigger. A menu that shuts and leaves focus where the surface was drops a keyboard visitor at the top of the document, several tabs from the button they pressed
 - a row that cannot be used stays in the menu and is announced as unavailable rather than being removed. A set that changes shape between openings is one a visitor has to learn twice
 - the menu is absent from the document when shut rather than hidden, so no destination is reachable by a visitor tabbing past a closed button
-- the trigger is a real button. A menu opened by a div is a menu a keyboard cannot reach, and one opened by a link is a link that does not navigate — which is why this package's own Button, an anchor with a required href, could not be the trigger
+- the trigger is a real button. A menu opened by a div is a menu a keyboard cannot reach, and one opened by a link is a link that does not navigate — which is why this package's own Button, then an anchor with a required href, could not be the trigger
 
 ## Rules
 
@@ -204,7 +204,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.
 
@@ -256,6 +256,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/faqaccordion.md

@@ -0,0 +1,217 @@
+<!-- GENERATED from faq-accordion.contract.json. Do not edit. -->
+
+# FaqAccordion
+
+A section of questions and answers: a heading over an Accordion, one question open at a time. The answers are put away until a reader asks for one, so a page can carry the ten things people ask before they sign up without being ten paragraphs long.
+
+The rows are AccordionItems, handed in as children; this draws the heading and the column and wraps them in the Accordion that keeps one open. Everything about a row — the rule between rows, the chevron, the keyboard — is Accordion's.
+
+## Use when
+
+- The questions a reader asks before acting — fees, limits, how long a withdrawal takes — near the end of a landing page or on a help page
+- Objections a page has to answer without making every reader read every answer
+
+## Do not use
+
+- The answers are short enough to read all at once → `FeatureBullets`
+- Each item is a feature, not a question → `FeatureCards`
+- Content a reader must see — terms, risk warnings, anything the page is obliged to show. A folded answer is one most readers never open
+- Navigation. A row that opens to a list of links is a menu wearing a question
+
+## Anatomy
+
+FaqAccordion renders 4 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-faqaccordion`. The section. It paints the ground and the ink to go with it — see `ground` — and asks its own width, so the heading centres on the section's measure rather than the window's.
+- `inner` — `<div>`, class `dds-faqaccordion__inner`. The measure and the gutter, the same column every band holds its content in, and the step from the heading to the questions: space.heading.content.
+- `title` — `<h2>`, class `dds-faqaccordion__title`. What the questions are about. `h2` because a section sits under the page's own heading, and every question below it is an `h3` — Accordion's own default level. Starts on a phone, centred from the fold.
+- `list` — `<div>`, class `dds-faqaccordion__list`. The questions, as wide as the column — the reference design's list runs the content width. It holds the Accordion this draws around the rows, which keeps one open and rules between them and nowhere else. On the dark band it is also where the questions are turned round, since AccordionItem has no tone of its own: see `ground`.
+
+Apply these classes from the generated `faqAccordionParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `AccordionItem`
+- Never contains: `Accordion`, `FaqAccordion`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+- Holds at least 2
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white. A section that has nothing to separate itself from what is above it — most of them — and the ground a reader is already on
+- `subtle` — A quiet step off the page, for a band that wants to read as its own section without changing the page's voice — the reference design's slate FAQ. 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. It stops the page rather than dividing it, so it is for a section a reader should arrive at — and one per page is usually one more than enough. The questions turn round with it: white headings, a muted chevron and rules in the band's own veil, fixed like the band
+
+Use when: Which of the page's three grounds this section paints. A marketing page is white, and a band that wants to be seen as a band takes one of the other two — so this is how a page builds its rhythm: white, white, grey, white, dark. Two in a row is a deliberate pair rather than an accident, and the section above knows nothing about the one below it, so the page is the only thing that can decide.
+
+The ink follows the ground and is not a second decision: a dark band carries white type because this sets both halves in one value, which is what the painted-ground-carries-its-ink rule exists to stop a page getting wrong.
+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. What the questions are about, in the fewest words — "Frequently asked questions", "Withdrawals".
+Never for: A question. The rows are the questions; the heading is what they share.
+
+## 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 from question to question. Each heading is a button; Enter or Space opens its answer and closes whichever was open — the keyboard is AccordionItem's.
+- accessible name from title, so the section is a named region a screen reader can jump to and skip
+- The questions are headings one level under the section's own, so a reader moving by heading lands on each question and the outline reads as the page's.
+
+## 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
+
+❌ FaqAccordion for: The answers are short enough to read all at once
+   A list a reader scans needs nothing opened; folding six one-line answers makes six clicks of what was one glance
+   → use `FeatureBullets` instead.
+
+❌ FaqAccordion for: Each item is a feature, not a question
+   Features are compared side by side; questions are looked up one at a time
+   → use `FeatureCards` instead.
+
+## Example
+
+```tsx
+import { FaqAccordion, AccordionItem } from '@deriv-com/dds-marketing'
+
+<FaqAccordion title="Frequently asked questions">
+  <AccordionItem title="Is there a minimum deposit?" onExpandedChange={(expanded) => { /* your handler */ }}>There is no minimum on any account. Fund it with whatever you plan to trade.</AccordionItem>
+  <AccordionItem title="How long do withdrawals take?" onExpandedChange={(expanded) => { /* your handler */ }}>Most withdrawals reach you within one working day. Card refunds can take up to five.</AccordionItem>
+  <AccordionItem title="Which markets can I trade?" onExpandedChange={(expanded) => { /* your handler */ }}>Forex, stocks, stock indices, commodities, cryptocurrencies and derived indices, all from one account.</AccordionItem>
+  <AccordionItem title="Is my money safe?" onExpandedChange={(expanded) => { /* your handler */ }}>Client funds are held in segregated accounts, separate from the company's own.</AccordionItem>
+  <AccordionItem title="Can I try trading without risking money?" onExpandedChange={(expanded) => { /* your handler */ }}>Every account comes with a free demo account, funded with virtual money and reloadable whenever you like.</AccordionItem>
+</FaqAccordion>
+```
+
+## In use
+
+Most rows below hold the same set, written once here:
+
+```tsx
+import { AccordionItem } from '@deriv-com/dds-marketing'
+
+const accordionitems = (
+  <>
+    <AccordionItem title="Is there a minimum deposit?">There is no minimum on any account. Fund it with whatever you plan to trade.</AccordionItem>
+    <AccordionItem title="How long do withdrawals take?">Most withdrawals reach you within one working day. Card refunds can take up to five.</AccordionItem>
+    <AccordionItem title="Which markets can I trade?">Forex, stocks, stock indices, commodities, cryptocurrencies and derived indices, all from one account.</AccordionItem>
+  </>
+)
+```
+
+### The three grounds
+
+The page for a section with nothing to set it apart, the grey band to close a page, the dark band for one a reader should arrive at — the questions turned round with it.
+
+```tsx
+import { FaqAccordion } from '@deriv-com/dds-marketing'
+
+// ground="page"
+<FaqAccordion title="Frequently asked questions">{accordionitems}</FaqAccordion>
+
+// ground="subtle"
+<FaqAccordion ground="subtle" title="Frequently asked questions">{accordionitems}</FaqAccordion>
+
+// ground="strong"
+<FaqAccordion ground="strong" title="Frequently asked questions">{accordionitems}</FaqAccordion>
+```
+
+### How many questions
+
+Two at least, because a set is what makes an accordion worth opening. One open at a time, and rules only between rows.
+
+```tsx
+import { AccordionItem, FaqAccordion } from '@deriv-com/dds-marketing'
+
+// Two questions
+<FaqAccordion title="Withdrawals">
+  <AccordionItem title="Is there a minimum deposit?" onExpandedChange={(expanded) => { /* your handler */ }}>There is no minimum on any account. Fund it with whatever you plan to trade.</AccordionItem>
+  <AccordionItem title="How long do withdrawals take?" onExpandedChange={(expanded) => { /* your handler */ }}>Most withdrawals reach you within one working day. Card refunds can take up to five.</AccordionItem>
+</FaqAccordion>
+
+// Four questions
+<FaqAccordion title="Frequently asked questions">
+  <AccordionItem title="Is there a minimum deposit?" onExpandedChange={(expanded) => { /* your handler */ }}>There is no minimum on any account. Fund it with whatever you plan to trade.</AccordionItem>
+  <AccordionItem title="How long do withdrawals take?" onExpandedChange={(expanded) => { /* your handler */ }}>Most withdrawals reach you within one working day. Card refunds can take up to five.</AccordionItem>
+  <AccordionItem title="Which markets can I trade?" onExpandedChange={(expanded) => { /* your handler */ }}>Forex, stocks, stock indices, commodities, cryptocurrencies and derived indices, all from one account.</AccordionItem>
+  <AccordionItem title="Is my money safe?" onExpandedChange={(expanded) => { /* your handler */ }}>Client funds are held in segregated accounts, separate from the company's own.</AccordionItem>
+</FaqAccordion>
+```