@deriv-com/dds-marketing 0.2.0 → 1.0.0

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, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+- **A component is written along the reading axis, not along the page's left and right** — Every measure, inset and placement in this package names an axis rather than a side: inline-size and block-size, padding-inline and padding-block, inset-inline-start and inset-block-end, margin-inline: auto, text-align: start. Written that way a component follows whichever direction the page is read in, and a band whose claim ranges to the leading edge with its subject on the trailing one is the same composition in Arabic as in English, mirrored, with nothing restated. Written as left and right it is the same pixels in both, which is a layout nobody designed for the second language.
+
+The enum values follow the same rule and for the same reason. A prop that names where a picture sits takes start and end, never left and right — FeatureSplit, FeatureBullets and FeatureScroll all declare mediaPosition that way, and the flex directions they generate flip on their own because row already means the reading order. A value called left would have to be re-read as right by every author working in a mirrored page, which is a translation this system should be doing rather than asking for.
+
+The guidance a contract carries is part of the component, so it follows too. Describing a claim as ranging left is describing one of the two languages, and it was written that way here for a while: three of the opening bands said so in their own intent. A reader in a mirrored page meets that sentence and has to decide whether the component is wrong or the sentence is, and neither answer is one documentation should force.
+
+Two things genuinely have no logical form and are not covered by this. A CSS gradient takes a physical direction — there is no to inline-end — so a pattern that must mirror has to be stated twice under a direction query, and one that is periodic and centred, like PageHeader's rule grid, does not need to. A glyph that points the way onward is the other: an arrow is a picture of a direction, and mirroring it belongs to the icon set rather than to the component holding it.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ 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>
+```

package/.llm/components/featurebullets.md

@@ -0,0 +1,254 @@
+<!-- GENERATED from feature-bullets.contract.json. Do not edit. -->
+
+# FeatureBullets
+
+A section pairing a claim with a ruled list of what something includes, beside one picture.
+
+The list is the argument: each line is one thing a reader gets, and the column is meant to be counted rather than read. The check against each line is the component's own and the one thing the page does not supply — the same six strings with a bullet are a summary, with a check they are a promise.
+
+It sits on the page's own ground by default; `ground` paints the grey or the dark band where the section needs setting apart from the ones around it.
+
+## Use when
+
+- A page has to list what a product or a plan includes, and the list is the argument
+- Several benefits are each one line long and are read by scanning rather than reading
+- A claim needs something beside it, and a picture is the only thing there is to put there
+
+## Do not use
+
+- The items are two or three words and belong on one line → `Badge`
+- Each item needs a heading and a paragraph of its own → `Card`
+- The section opens the page → `ProductHero`
+- A comparison. Every line here is included and marked so; a list where some items are absent needs a mark for absence, which this has no way to say
+- Running prose broken into lines. A check against a sentence claims the sentence is a feature
+- The page's opening or closing band. This is a section in the middle of a page and carries no navigation of its own
+
+## Anatomy
+
+FeatureBullets renders 10 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-featurebullets`. The section. It paints the ground that separates it from the page above and below, and asks its own width so the split folds on the section's measure rather than the window's.
+  
+  It paints one of the page's three grounds and the ink that goes with it, in one decision — see `ground`. The ink is set here and inherited by everything inside, which is the package's rule about a section that paints a ground: stated once, it cannot be half-applied.
+- `inner` — `<div>`, class `dds-featurebullets__inner`. The measure and the gutter, holding the section's content in the same column as every other section on the page.
+- `split` — `<div>`, class `dds-featurebullets__split`. The two halves. A row at full width with the picture on whichever side `mediaPosition` names, and one column below the fold with the list first — because a reader on a phone came for the words, whichever side the picture takes on a desktop.
+- `content` — `<div>`, class `dds-featurebullets__content`. The claim and the list under it.
+  
+  It sets no gap of its own. The step from the claim to the list is the title's own `margin-block-end`, which is how FeatureSplit and FeatureScroll carry theirs — a column whose steps are a single gap can only ever say one thing, and the moment a second part joins it the two distances have to be told apart.
+- `title` — `<h2>`, class `dds-featurebullets__title`. What the list is a list of. `h2` because a section in the middle of a page sits under the page's own heading, and a second `h1` would be a second page.
+- `list` — `<ul>`, class `dds-featurebullets__list`. The inclusions, as a list rather than a stack of divs — a screen reader announces how many there are before reading one, which is the whole way this section is meant to be taken in.
+  
+  Nothing separates the rows: each carries its own rule on its start edge and its own padding inside it, so a gap here would be a second distance doing the first one's job and the rules would stop landing between the lines. `space.gap.none` is that said rather than left out — a part that binds nothing reads as one somebody forgot.
+- `item` — `<li>`, class `dds-featurebullets__item`. One inclusion. Ruled above rather than below, which is what Accordion does and for the same reason: every rule then belongs to a row and sits over it, so the lines fall between the rows and none is left under the last one.
+  
+  The rows arrive one after another as the section comes up, in the order they are read, so a set a reader is meant to count appears to count itself. It is the one place in this package where a longer cascade is right: everywhere else a block arrives as one thing, and here the arriving is the list's own argument being made.
+  
+  The rule is drawn in `color.border.subtle`, which is black at five per cent — an alpha, so it tints whatever it lands on, and on a dark band it tints black with black and draws nothing. `color.border.subtle-inverse` is the counterpart and is what the dark ground takes.
+- `mark` — `<span>`, class `dds-featurebullets__mark`. The check against each line, and the one thing here the page does not supply. It is what makes this a list of inclusions rather than a list: the same words with a bullet are a summary.
+  
+  Its colour follows the ground, and not for contrast — the mark is decoration and the title says what it says. `color.fg.brand-accent` is the brand red at full saturation and its own description limits it to the bare page, never a tint: on `color.bg.subtle` the role for a brand mark is `color.fg.brand`, and on the dark band it is the band's own ink. A mark that kept one value across three grounds would be right on one of them.
+- `text` — `<span>`, class `dds-featurebullets__text`. The line itself.
+- `media` — `<div>`, class `dds-featurebullets__media`. The picture, and one of the section's two halves rather than an addition to it. Held to a square and cropped to fill it, so a section is the same shape whatever the page passes — three of these down a page with three different crops is three sections that do not line up.
+
+Apply these classes from the generated `featureBulletsParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `FeatureBullets`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar`, `Table`, `Accordion` — 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. 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 one to reach for first when two sections need telling apart. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section — in dark mode the tint alone took on whatever it was set against, and on a light surface it was light ink on white.
+- `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
+
+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 dark is a page with no emphasis left, and a reader stops reading the grounds as meaning anything. Alternating for its own sake is the same mistake more slowly.
+
+And never the brand's own coral, `color.bg.brand`, which is not offered here. That ground belongs to the band that asks a reader to do something — the one place on a page where the brand colour is the point rather than decoration — and a feature section wearing it is a page with two calls to action, one of which does nothing. It is `color.bg.brand-strong` that this offers: the dark brand ground, which is a band breaking a page rather than a band asking for something.
+
+### mediaPosition — `end` | `start` (default `end`)
+
+- `end` — The default. The list is read first, which is the order the section argues in
+- `start` — The second of two on a page, so the two do not read as one column with a picture stuck to one side
+
+Use when: Which side the picture takes at full width. Alternating it down a page is what stops three of these in a row reading as one long column, and it is the page's decision rather than this section's — which is why it is a prop and not a rule.
+
+It is the arrangement at full width and never a promise about a phone: below the fold the list is always first, because a reader on a phone came for the words.
+Never for: Moving the picture on a phone. There is one column there and the list leads it
+
+### title — `string` **Required.**
+
+Use when: Always. What the list is a list of, in the fewest words that say it
+Never for: A sentence. The list underneath is the argument; this only has to name it
+
+### bullets — `data` `string[]` **Required.**
+
+Use when: Always. One line per thing included, each short enough to take in at a glance. Strings rather than nodes, because every line is marked the same way and a line free to bring its own mark is a list that stops being one
+Never for: A sentence per line, or a line that is not included in what the title names. The mark against each one is a claim the page is making
+
+### media — `node` **Required.**
+
+Accepts: *
+Use when: Always. The picture that sits beside the list — a screenshot, a photograph, an illustration. The section is a split and the picture is one half of it: without one the list runs to a measure it was never sized for, and what is left is a heading over a column with a gap beside it.
+Never for: Anything a reader has to read or press. It is held to a square and cropped to fill it, so words in it are cropped too
+
+## 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 past the section. Nothing in it is operable — the list is read, not used — so there is nothing here to land on.
+- accessible name from title, so the band is a named region a screen reader can jump to and skip rather than an unlabelled section a reader has to walk
+- The inclusions are a list element, so a screen reader announces how many there are before reading the first. A stack of divs reads as prose and loses the count, which is the one thing a reader scanning this section is taking from it
+- The mark against each line is decoration and is hidden from assistive technology. What it says — that the line is included — is what the section's own title says once, and announcing it per line is six repetitions of one fact
+- The picture is decoration and is hidden from assistive technology. What the section says is the title and the inclusions; a picture carrying something they do not is a section that reads as half empty to anyone who cannot see it
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+- **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
+
+❌ FeatureBullets for: The items are two or three words and belong on one line
+   A row of marks reads faster than a column of them, and six words do not need six rows
+   → use `Badge` instead.
+
+❌ FeatureBullets for: Each item needs a heading and a paragraph of its own
+   A list whose items are each a paragraph is a set of cards, and a reader scanning it has stopped scanning
+   → use `Card` instead.
+
+❌ FeatureBullets for: The section opens the page
+   A page's opening band is a claim, not an inventory
+   → use `ProductHero` instead.
+
+## Example
+
+```tsx
+import { FeatureBullets, AspectRatio } from '@deriv-com/dds-marketing'
+
+<FeatureBullets title="Everything a forex account includes" bullets={["Zero commission on every trade","Spreads from 0.0 pips","Over 50 currency pairs","Execution in under 100 milliseconds","24/7 customer support"]} media={<AspectRatio ratio="square" />} />
+```
+
+## In use
+
+### The ground it sits on
+
+The three grounds a page can put a section on. The page is white, so a band painting one of the other two is saying it is its own section — and the ink follows the ground.
+
+```tsx
+import { AspectRatio, FeatureBullets } from '@deriv-com/dds-marketing'
+
+// On the page itself
+<FeatureBullets ground="page" title="Everything a forex account includes" bullets={["Zero commission on every trade","Spreads from 0.0 pips","Over 50 currency pairs","Execution in under 100 milliseconds","24/7 customer support"]} media={<AspectRatio ratio="square" />} />
+
+// On the quiet ground
+<FeatureBullets ground="subtle" title="Everything a forex account includes" bullets={["Zero commission on every trade","Spreads from 0.0 pips","Over 50 currency pairs","Execution in under 100 milliseconds","24/7 customer support"]} media={<AspectRatio ratio="square" />} />
+
+// On the dark band
+<FeatureBullets ground="strong" title="Everything a forex account includes" bullets={["Zero commission on every trade","Spreads from 0.0 pips","Over 50 currency pairs","Execution in under 100 milliseconds","24/7 customer support"]} media={<AspectRatio ratio="square" />} />
+```
+
+### Which side the picture takes
+
+Alternating it down a page is what stops three of these in a row reading as one long column. Below the fold there is one column and the list leads it either way.
+
+```tsx
+import { AspectRatio, FeatureBullets } from '@deriv-com/dds-marketing'
+
+// Picture last — the default
+<FeatureBullets mediaPosition="end" title="Everything a forex account includes" bullets={["Zero commission on every trade","Spreads from 0.0 pips","Over 50 currency pairs","Execution in under 100 milliseconds","24/7 customer support"]} media={<AspectRatio ratio="square" />} />
+
+// Picture first — for the second of two
+<FeatureBullets mediaPosition="start" title="And everything a demo account includes" bullets={["Zero commission on every trade","Spreads from 0.0 pips","Over 50 currency pairs"]} media={<AspectRatio ratio="square" />} />
+```
+
+### How long the list runs
+
+Each line is one thing, short enough to take in at a glance. The rules fall between the rows, so the set is bounded by the section's own step rather than by a line above the first or under the last.
+
+```tsx
+import { AspectRatio, FeatureBullets } from '@deriv-com/dds-marketing'
+
+// Three
+<FeatureBullets title="What you get" bullets={["Zero commission on every trade","Spreads from 0.0 pips","Over 50 currency pairs"]} media={<AspectRatio ratio="square" />} />
+
+// Five
+<FeatureBullets title="What you get" bullets={["Zero commission on every trade","Spreads from 0.0 pips","Over 50 currency pairs","Execution in under 100 milliseconds","24/7 customer support"]} media={<AspectRatio ratio="square" />} />
+```