@deriv-com/dds-marketing 0.1.0 → 0.2.0

package/.llm/components/accordion.md

@@ -0,0 +1,193 @@
+<!-- GENERATED from accordion.contract.json. Do not edit. -->
+
+# Accordion
+
+A stack of rows whose headings stay and whose detail is put away until the reader asks for it. It exists so a long page can be read as a short one: the headings are the page, and each row is something the reader may or may not want. Two rows at least — a set is what makes it work, because a heading earns its place by being scanned against the ones around it. One row is open at a time and that is not configurable here: a marketing page is read by scrolling, and a set that could hold every row open is the long page the accordion was put there to shorten.
+
+## Use when
+
+- Questions a reader asks near a decision — what it costs, whether their money is safe, how long a withdrawal takes. Most go unread, which is the point: the ones that matter are found by scanning the headings
+- The long version of something the page has already said shortly — specifications, trading hours, the full terms. The heading is the topic and the panel is the detail nobody needs until they need it
+- A run of rows at one depth in the page's outline, sitting under a section heading of their own
+
+## Do not use
+
+- There is one thing to disclose rather than a set → `AccordionItem`
+- The reader is meant to read all of it → `Card`
+- Hiding what a reader has to know before deciding — a fee, a restriction, a condition on an offer. Disclosure a page is obliged to make is disclosure that stays on the page
+- Navigation. A row that goes somewhere when pressed is a link wearing a chevron, and a reader who opens it expecting words gets a page instead
+- A single row on its own. Two at least, because a heading is scanned against its neighbours and one heading has none
+- Steps in a sequence. Rows here are independent and in no order — a reader may open the third without the first, and nothing about the set says otherwise
+
+## Anatomy
+
+Accordion renders one element.
+
+- `root` — `<div>`, class `dds-accordion`. The set, and the rule that closes it. It draws no fill and no corner: a marketing page is white and an accordion on it is a list rather than a panel, so what separates the rows is a hairline and what ends the set is one more. A set that wants a surface under it goes inside a Card, which is the component that owns fills and corners — drawing one here would be a second card nobody could tell apart from the first.
+  
+  It draws no edge at all, and says so rather than staying silent: `border.width.none` is bound so that a set closing itself with a hairline is a change somebody has to make on purpose. Every rule here belongs to a row and sits above it, so the lines fall between the rows and nowhere else. A list ruled top and bottom as well reads as a box drawn around it, which is a panel — and a panel is a Card, which this is not.
+  
+  It holds which row is open, and it is the only thing that can: a row cannot see its siblings, so left to themselves they would all open. That is why `expanded` is injected rather than asked for — the set decides, and a row reports the press back so the set can move the answer.
+  
+  No role and no ARIA of its own. A run of headings each followed by a region is already a structure a screen reader can navigate; naming it a widget would put a reader inside something they have to learn their way out of.
+
+Apply these classes from the generated `accordionParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `AccordionItem`
+- Never contains: `Accordion`, `Card`, `CardButton` — in children or in any prop that takes a node
+- Holds at least 2
+
+## Props
+
+### headingLevel — `2` | `3` | `4` (default `3`)
+
+- `2` — The rows are the page's own sections, sitting directly under its title — a page that is nothing but questions is the case
+- `3` — The default. The set sits under a section heading of its own, which is where an accordion usually is
+- `4` — The set is inside a subsection that already carries a heading above it
+
+Use when: Where the rows sit in the page's outline. It belongs to the set rather than to a row because every row of one accordion is at one depth by definition, and a set whose rows disagreed would describe a hierarchy the design does not have — which a reader navigating by heading would be told exists
+Never for: Making a row's words larger or smaller. The level is the outline, not the type: every row takes the same step whatever depth it sits at, because a question is a question wherever the set is on the page
+
+Also accepts everything from `HTMLAttributes<HTMLDivElement>`.
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- `Tab` — Reaches each row's own control in turn. A run of headings is not a composite widget, so there are no arrow keys to learn and nothing traps the reader inside the set
+- The set carries no role of its own. A run of headings each followed by a region is a structure a screen reader already navigates, and naming it a widget would ask a reader to learn a way out of something they walked into.
+- Every row sits at the same heading level, pushed down from the set. Rows that disagreed would describe a depth the page does not have to anyone moving through it by heading.
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ Accordion for: There is one thing to disclose rather than a set
+   A single row is a disclosure, not an accordion: there is nothing to scan it against and nothing for opening it to close. The row works on its own — it owns its heading, its control and its panel — and a set of one is a wrapper that only says the row is alone
+   → use `AccordionItem` instead.
+
+❌ Accordion for: The reader is meant to read all of it
+   Copy behind a control is copy most readers will not open, and a page that hides what it needs the reader to know has shortened itself by losing the argument. An accordion is for what a reader goes looking for, not for what the page wants to say
+   → use `Card` instead.
+
+## Example
+
+```tsx
+import { Accordion, AccordionItem } from '@deriv-com/dds-marketing'
+
+<Accordion>
+  <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 */ }}>Card refunds can take up to five working days. Everything else is usually one.</AccordionItem>
+  <AccordionItem title="Which markets can I trade?" onExpandedChange={(expanded) => { /* your handler */ }}>Forex, indices, commodities and stocks, on one account.</AccordionItem>
+</Accordion>
+```
+
+## In use
+
+### One row open at a time
+
+Opening a row shuts the one before it. Not a setting: a marketing page is read by scrolling, and a set that could hold every row open is the long page the accordion was put there to shorten.
+
+```tsx
+import { Accordion, AccordionItem } from '@deriv-com/dds-marketing'
+
+// Press one, and the last one closes
+<Accordion>
+  <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 */ }}>Card refunds can take up to five working days. Everything else is usually one.</AccordionItem>
+  <AccordionItem title="Which markets can I trade?" onExpandedChange={(expanded) => { /* your handler */ }}>Forex, indices, commodities and stocks, on one account.</AccordionItem>
+</Accordion>
+```
+
+### Where the rows sit in the outline
+
+The level belongs to the set, not to a row: every row of one accordion is at one depth by definition. A reader moving through the page by heading finds all of them at the same step.
+
+```tsx
+import { Accordion, AccordionItem } from '@deriv-com/dds-marketing'
+
+// Under a section heading of its own — the default
+<Accordion headingLevel="3">
+  <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 */ }}>Card refunds can take up to five working days. Everything else is usually one.</AccordionItem>
+</Accordion>
+
+// A page that is nothing but questions
+<Accordion headingLevel="2">
+  <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 */ }}>Card refunds can take up to five working days. Everything else is usually one.</AccordionItem>
+</Accordion>
+
+// Inside a subsection that already has a heading
+<Accordion headingLevel="4">
+  <AccordionItem title="Is there a minimum deposit?" onExpandedChange={(expanded) => { /* your handler */ }}>There is no minimum on any account.</AccordionItem>
+  <AccordionItem title="How long do withdrawals take?" onExpandedChange={(expanded) => { /* your handler */ }}>Card refunds can take up to five working days.</AccordionItem>
+</Accordion>
+```

package/.llm/components/accordionitem.md

@@ -0,0 +1,236 @@
+<!-- GENERATED from accordion-item.contract.json. Do not edit. -->
+
+# AccordionItem
+
+One row of an Accordion: a heading that is always there, and the detail under it that is not. The heading is the whole of the target — the words and the chevron are one control, because a reader aiming at a row is aiming at the row rather than at the mark on the end of it. The chevron says which way the row is about to move rather than which way it just moved, so it is a promise rather than a report.
+
+## Use when
+
+- One row inside an Accordion — every row of a set is one of these
+- A single disclosure with no set around it: one topic whose detail is worth offering and not worth showing. The row is whole on its own, and it keeps its own open state when nothing is injecting one
+
+## Do not use
+
+- The heading goes somewhere rather than opening something → `CardButton`
+- A control inside the heading. The whole heading is one button, so a second one inside it is unreachable to a keyboard and ambiguous to a pointer — the rule about it is the one rule in this system that cannot live on any single component
+- A heading that is a sentence. It is scanned against the rows above and below it, and a row nobody can scan is a row nobody opens
+- Copy the reader is obliged to see. What is behind the control is what a reader goes looking for, not what the page needs them to have read
+- A panel that holds another Accordion. Rows inside rows put a reader two folds deep with no way to see where they are, and the outline they navigate by stops describing the page
+
+## Anatomy
+
+AccordionItem renders 7 elements. A token binding names the part it applies to.
+
+- `root` — `<div>`, class `dds-accordionitem`. The row, and the rule above it. It draws no fill: a row is a line of the page rather than a surface, and the hairline over it is the whole of what separates it from the row before.
+  
+  The rule is a `border-width` and a `border-color` with only the block-start edge given a style, which is how one side is drawn when a width binds all four at once.
+  
+  It is declared on every row and taken off the first, which makes the first row the exception rather than every other row the rule — the same way round Product's does it. A separator is between two things, so the row with nothing above it has none, and the set draws no rule beneath the last. What is left is lines between the rows and no box around them.
+- `heading` — `<div>`, class `dds-accordionitem__heading`. The heading, which is a real one: it takes `role="heading"` and the level the set pushed down, so a reader moving through the page by heading finds every row. A <div> wearing the role rather than an <h3> written out, because the level is a prop and an element cannot be chosen at runtime without six branches saying the same thing.
+  
+  It holds the control rather than being it. A heading that was itself a button would announce two things at once, and the pattern every screen reader expects is a heading with a button inside it.
+- `trigger` — `<button>`, class `dds-accordionitem__trigger`. The target, and all of it. The words and the chevron are one control because a reader aiming at a row aims at the row — a chevron-sized target on the end of a full-width heading is a mark most people miss and everyone on a phone misses.
+  
+  It carries `aria-expanded` and `aria-controls`, which is what makes the fold audible: the state is on the control the reader pressed rather than on the panel they cannot see.
+  
+  Full width and text-aligned to the start, which a button does not do by itself. A `<button>` centres its contents and shrinks to them, so without both it would be a short centred label floating in the middle of a row.
+  
+  And a floor in both directions, declared rather than left to emerge. A row is always taller than a fingertip once its padding is counted, but that is a size nobody wrote down: it moves the moment the inset scale does, and nothing says it was ever meant to be a target.
+  
+  `padding-inline: 0`, which is a reset rather than a measure. A browser gives a button its own horizontal padding — six pixels of it — and binding only the block axis left that in place, so the question sat six pixels right of the answer underneath it. Two things in a column that are supposed to line up, not lining up, for a reason nothing in the contract mentioned.
+  
+  Nothing insets the row from the sides at all, and that is the decision rather than the oversight. This is a ruled list on the page, not a panel: the rules run the width they are given and the words start where the page's own column starts. A set that wants an inset is one a page has put inside something that insets it.
+  
+  It opens at `space.inset.md`, which is the step the scale gained for exactly this. At the old twenty-four a shut row stood forty-nine pixels of air between one question and the next — the padding counts twice, once under the row above and once over the row below, so a measure that looks generous on its own doubles down the set. Twelve was the other way: that is a control's inset, and a row set like a form field reads as something to fill in rather than something to read.
+- `title` — `<span>`, class `dds-accordionitem__title`. The row's words. A <span> rather than an element of its own, because the heading above it already carries the role and the level — a second heading inside the first would put two in the outline where the page has one.
+  
+  It takes `font.label.md`, and the reason is the role rather than the size. This text is the control: the whole heading is one button, and `label.md` is the step named for interactive text — the default one, "one size for every control". `label.lg` is the step above it, for interactive text given prominence, which is a hero's call to action rather than a row of a list.
+  
+  `subtitle` was here first and was wrong twice over: it is for sub-section headers and secondary titles, a pricing plan's name, and a row of an accordion is neither however much it looks like one.
+  
+  `h5` is the near miss on the other side. These *are* headings — but the level is already carried by the role above, and a set of eight questions set at the heading step reads as eight sections of the page rather than one list of them. The outline and the type are separate decisions here, which is the same split `headingLevel` makes.
+  
+  It lands at the size the answer takes, and only its weight tells the two apart: `label.md` is medium where `body.md` is regular. That is a fine distinction for a heading to rest on, and what carries the rest of it is position — a question sits above its answer, alone on its row, with the chevron at the far end.
+- `marker` — `<svg>`, class `dds-accordionitem__marker`. The chevron, pointing the way the row is about to move rather than the way it went. One glyph turned over rather than two swapped: a swap replaces the mark between frames and there is nothing to watch, where the turn is itself the movement that says which way the fold went. The angle is applied in the implementation, because a rotation is not a property the contract can bind.
+  
+  Drawn by `Icon`, which is what owns a glyph's measure. The class stays on it — Icon clones onto the SVG it is handed and keeps whatever class was already there — so this part still names the two things that are the row's rather than the glyph's: its colour, and a duration that matches the fold.
+  
+  What moved out is everything about being a glyph. The width and the height are `Icon`'s, and so is the knowledge that a Quill glyph ships its own width and height attributes and a box around it changes nothing — which is a fact three components here were each carrying separately.
+  
+  The timing stays, and has to: Icon carries one duration for every mark of this kind, and this one is not turning on its own account. It turns with the panel, so it takes the panel's pair per side of the axis, and those rules outrank Icon's by a class.
+  
+  It is presentation and carries no name. What it says is already in `aria-expanded` on the control around it, and a mark announcing "expanded" beside a button that has just announced the same thing says it twice.
+  
+  It is timed with the fold rather than on its own. One duration for both directions left the chevron finishing its turn while the panel was still travelling, which reads as two things happening near each other rather than one thing opening — so it takes the panel's pair, on the same axis.
+- `panel` — `<div>`, class `dds-accordionitem__panel`. What the row was hiding. It stays in the document whether or not it is open, because a panel that unmounted would take its own height with it and there would be nothing to animate between — and a reader searching the page in the browser would not find words the page is holding.
+  
+  It is a grid of one track, and the track is what moves. A height cannot be animated from nothing to auto, and a number here would be a guess at how long an answer is — the one thing a panel's height cannot be is known.
+  
+  Its `display` varies by the axis rather than being declared once, and that distinction is the whole of whether a shut row takes space. `hidden` on the element carries `display: none` from the browser's own sheet, which any author rule outranks — so a panel told `display: grid` unconditionally is a grid box in the layout whether or not it is hidden, and the content's bottom inset shows through as a band under every shut row. Declared per value, `none` and `grid` agree with the attribute instead of overruling it.
+  
+  Opening takes `motion.duration.slow`, which the scale names for accordions in as many words, and `easing.enter` to settle rather than stop. Shutting is quicker and eased the other way, and that asymmetry is not tidiness: the collapse ends with `display` flipping to `none`, so a curve with a long tail leaves the last sliver crawling and then vanishing. `easing.exit` accelerates away and reaches nothing exactly as the duration runs out. The same tail on the way open sits at ninety-nine percent of the height, where nobody can see it — which is why one curve for both directions cannot be right however tidy it looks.
+- `content` — `<div>`, class `dds-accordionitem__content`. The words themselves, inside the track that moves. A second box is not redundant: the grid track collapses to no height and its contents have to be clipped by something that is not also the thing being measured, or the text spills out of a row that is closed.
+  
+  It closes at `space.inset.md`, the same step the trigger opens at, so an answer sits the same distance from its own question as from the rule beneath it. That is a squarer rhythm than the asymmetry it replaces and it gives up something: at equal gaps nothing but the rule says which heading an open answer belongs to. The rule is doing that work now. The gap above an answer is the trigger's own bottom padding; the gap below it is this. Equal, the answer sits as near the next question as its own, and a reader scanning an open set cannot tell which heading it belongs to.
+  
+  It takes no colour of its own, which is how it comes out the same ink as the question above it. The trigger binds no default colour either — it inherits — so leaving this one unbound is what makes the pair agree rather than a second binding that happens to name the same role, and it keeps them agreeing on a ground neither of them chose. An answer set a step lighter than its question reads as an aside, and an answer is not an aside: it is the thing the question was asked for, and the question is already doing the work of being the heading.
+
+Apply these classes from the generated `accordionItemParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: any content
+- Never contains: `Accordion`, `AccordionItem`, `CardButton` — in children or in any prop that takes a node
+- Holds at least 1
+
+## Props
+
+### expanded — `boolean`
+
+Use when: Whether the panel is showing. Inside an Accordion this is injected on every render and the set owns it — a row cannot see its siblings, so it cannot know it is the one that should close. Left off, the row owns itself: absent is not the same as false here, and that difference is the whole of how one component is both. `false` is a set saying the row is shut; absent is nobody saying anything, and the row answers its own presses from there
+Never for: Forcing a row open so its words are always visible. A panel that never shuts is copy behind a control that lies about what it does, and the reader who closes it once will not open it again. Note that passing it at all takes the row over: `expanded={false}` with no `onExpandedChange` to move it is a row that can never open, the same way a value with no handler is a field that cannot be typed in
+
+### onExpandedChange — `callback`
+
+Use when: The page needs to know the row was pressed — to record which question was asked, or to hold the answer itself. Inside an Accordion the set chains its own handler after this one, so a page keeps its report whether or not it is also controlling the row
+Never for: Doing something other than opening the row. It fires because a reader asked to see the words; navigating or submitting from it makes the chevron a lie
+
+### title — `string` **Required.**
+
+Use when: Always — it is the half of the row that is always on screen. A question in the reader's own words, or the name of the thing the panel details. A string rather than a node, for the reason CardBody's title is one: a node prop cannot be given text in an examples row, and a row nobody can show is worse than a heading that cannot hold a link
+Never for: The answer, shortened. A heading that summarises the panel gives the reader no reason to open it, and a set of them is the long page again in smaller type
+
+### headingLevel — `2` | `3` | `4` (default `3`)
+
+- `2` — The rows are the page's own sections. Set on the Accordion rather than here, which pushes it down
+- `3` — The default, and where an accordion usually sits — under a section heading of its own
+- `4` — The set is inside a subsection that already carries a heading
+
+Use when: Where this row sits in the page's outline. Inside an Accordion it is injected, because every row of one set is at one depth by definition. Set it here only on a row standing alone
+Never for: Changing how large the words are. The level is the outline and the type is `font.subtitle` either way — a row at h2 is not a bigger question than a row at h4
+
+Also accepts everything from `HTMLAttributes<HTMLDivElement>`.
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- Announced as: `button`
+- `Tab` — Moves to the row's control. One stop per row, on the heading's button — there is nothing else in a row that takes focus
+- `Enter` — Opens the row, or shuts it
+- `Space` — The same. A button answers both, and a reader who learned one does not have to learn the other
+- The control carries aria-expanded, and it is on the control rather than on the panel. A reader learns whether the row is open from the thing they are about to press, not from a region they cannot see until it opens.
+- The control names the panel with aria-controls, and the panel's id is stable across renders. An id that changed on every keystroke elsewhere on the page would point the control at nothing.
+- The panel is a named region, named by the control that opened it. A region is a landmark, and one without a name fills a screen reader's landmark list with anonymous entries — worse than declaring no role at all. Only one row is ever open, so exactly one such landmark exists at a time.
+- The panel stays in the document when the row is shut. Unmounting it takes its height away, so there is nothing to move between — and it takes the words out of the browser's own find-on-page, which is how a reader looks for an answer they half remember.
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ AccordionItem for: The heading goes somewhere rather than opening something
+   A chevron that turns and a chevron that leads are different promises. This opens a panel below itself and stays on the page; a row that navigated would take the reader away from a control that told them it was about to unfold
+   → use `CardButton` instead.
+
+## Example
+
+```tsx
+import { AccordionItem } from '@deriv-com/dds-marketing'
+
+<AccordionItem title="Is there a minimum deposit?">There is no minimum on any account.</AccordionItem>
+```
+
+## In use
+
+### Shut, and open
+
+The heading is always there and the detail is not. A row keeps its own state when nothing is injecting one, so it works on its own as well as inside a set.
+
+```tsx
+import { AccordionItem } from '@deriv-com/dds-marketing'
+
+// Shut — the panel is in the document, out of reach
+<AccordionItem title="How long do withdrawals take?">Card refunds can take up to five working days.</AccordionItem>
+
+// Open
+<AccordionItem expanded title="Is there a minimum deposit?">There is no minimum on any account.</AccordionItem>
+```
+
+### A row standing on its own
+
+Inside a set the level is injected and every row shares it. Set it here only on a row with no set around it, where nothing else can say how deep the page runs.
+
+```tsx
+import { AccordionItem } from '@deriv-com/dds-marketing'
+
+// h2 — the row is one of the page’s own sections
+<AccordionItem headingLevel="2" title="Security and your funds">We hold client money in segregated accounts.</AccordionItem>
+
+// h4 — inside a subsection that already has a heading
+<AccordionItem headingLevel="4" title="Segregated accounts">Client money is held apart from company money.</AccordionItem>
+```