@deriv-com/dds-marketing 0.1.0 → 1.0.0

package/.llm/components/breadcrumb.md

@@ -0,0 +1,205 @@
+<!-- GENERATED from breadcrumb.contract.json. Do not edit. -->
+
+# Breadcrumb
+
+The trail of ancestors above the current page on a marketing site, showing the visitor where they are in the site hierarchy. Every level but the last is a link back to that section; the last is where they already are. On a marketing site the trail is often the only structural cue a visitor has — they may have arrived from a search result or a campaign link and have no mental model of the site yet. It renders every level it is given and wraps rather than collapsing, because hiding levels describes a shallower hierarchy than the one the visitor is in.
+
+## Use when
+
+- The page sits inside a section hierarchy, and the levels above it are places the visitor can navigate to — a product page inside a markets section, a blog post inside a category
+- A visitor who arrived by search, social link or campaign URL needs to learn where they landed and how the site is organised around them
+
+## Do not use
+
+- The visitor is moving through the stages of a sign-up or onboarding flow rather than standing in a hierarchy → nothing here does this
+- There is exactly one place to go back to, and it is the previous page rather than a parent section → nothing here does this
+- The only route to a destination. A trail is a secondary affordance — it may be below the fold, it is the first thing a narrow viewport wraps, and a visitor who arrived by deep link may never read it. Anything reachable only from here is unreachable
+- Levels the hierarchy does not have. Padding a trail to look substantial describes a structure the visitor will not find when they climb it
+- Progress through a sign-up, checkout or onboarding flow, which is a task and not a place
+- Holding anything but its own items. The trail is a list of levels; a control sitting inside it is a control the visitor must tab through to reach the page
+
+## Anatomy
+
+Breadcrumb renders 3 elements. A token binding names the part it applies to.
+
+- `root` — `<nav>`, class `dds-breadcrumb`. The landmark. A nav rather than a plain wrapper because the trail is navigation a screen reader user should be able to jump to, and its accessible name is what tells them which navigation they have jumped to.
+- `list` — `<ol>`, class `dds-breadcrumb__list`. The levels, in order. Ordered rather than unordered because the order is the meaning — this trail read backwards describes a different hierarchy — and a list at all because that is what conveys the number of levels to someone who cannot see the row. Its own margin, padding and marker are cleared. It wraps rather than scrolling or truncating.
+- `separator` — `<li>`, class `dds-breadcrumb__separator`. The chevron between two levels. An li rather than a bare svg because an ol may only contain list items, and hidden from assistive technology because it is punctuation. Rendered between items and never before the first.
+  
+  The glyph inside it is drawn by `Icon` and has no part of its own any more. It had one, and the whole of what that part said was a width and a height — which is Icon's to say, and was being said here only because there was no Icon when this was written.
+
+Apply these classes from the generated `breadcrumbParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Can contain: `BreadcrumbItem`
+
+## Props
+
+### label — `string` (default `Breadcrumb`)
+
+Use when: Always, and the default is almost always right. It names the landmark rather than the page — a screen reader user listing the landmarks on a page hears this, and "Breadcrumb" is the word they are listening for
+Never for: The current page's own name, which the last item already carries. A landmark named after the page it sits on is announced twice and identifies nothing
+
+Also accepts everything from `HTMLAttributes<HTMLElement>`.
+
+## 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: `navigation`
+- an accessible name on the landmark, so a user listing the page's landmarks can tell this navigation from the others
+- the levels in an ordered list, so their number and their order reach a screen reader structurally rather than through the chevrons between them
+- separators hidden from assistive technology. They are punctuation, and a trail that announces them doubles its length with content that names no level
+
+## 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
+
+❌ Breadcrumb for: The visitor is moving through the stages of a sign-up or onboarding flow rather than standing in a hierarchy
+   A trail names places that exist whether or not the visitor reaches them; a flow's stages exist only inside the task, and numbering them as ancestors says the visitor can return to a step they may not be able to
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ Breadcrumb for: There is exactly one place to go back to, and it is the previous page rather than a parent section
+   A one-level trail is a back action wearing a trail's clothes. It teaches a structure the site does not have, and the affordance the visitor wants is a link they can click
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+## Example
+
+```tsx
+import { Breadcrumb, BreadcrumbItem } from '@deriv-com/dds-marketing'
+
+<Breadcrumb>
+  <BreadcrumbItem label="Markets" href="/markets" />
+  <BreadcrumbItem label="Forex" href="/markets/forex" />
+  <BreadcrumbItem label="EUR/USD" current />
+</Breadcrumb>
+```
+
+## In use
+
+### A trail, and the page at its end
+
+Every level above the current page links back to it. The last is the page itself — text rather than a link, and announced as where the visitor is.
+
+```tsx
+import { Breadcrumb, BreadcrumbItem } from '@deriv-com/dds-marketing'
+
+// Three levels, the last one the page
+<Breadcrumb>
+  <BreadcrumbItem label="Markets" href="/markets" />
+  <BreadcrumbItem label="Forex" href="/markets/forex" />
+  <BreadcrumbItem label="EUR/USD" current />
+</Breadcrumb>
+
+// One level above — the shallowest useful trail
+<Breadcrumb>
+  <BreadcrumbItem label="Markets" href="/markets" />
+  <BreadcrumbItem label="Forex" current />
+</Breadcrumb>
+```
+
+### Depth
+
+The trail grows with the hierarchy rather than being trimmed to fit. A visitor who arrived from a campaign link reads it to learn where they landed.
+
+```tsx
+import { Breadcrumb, BreadcrumbItem } from '@deriv-com/dds-marketing'
+
+// Five levels, wrapping rather than scrolling
+<Breadcrumb>
+  <BreadcrumbItem label="Markets" href="/markets" />
+  <BreadcrumbItem label="Forex" href="/markets/forex" />
+  <BreadcrumbItem label="Major pairs" href="/markets/forex/major" />
+  <BreadcrumbItem label="EUR/USD" href="/markets/forex/major/eurusd" />
+  <BreadcrumbItem label="Contract details" current />
+</Breadcrumb>
+```
+
+### A level with nowhere to go
+
+A level naming a grouping rather than a page renders as plain text, without claiming to be the current one. It is passed through; the last level is arrived at.
+
+```tsx
+import { Breadcrumb, BreadcrumbItem } from '@deriv-com/dds-marketing'
+
+// The middle level groups, and is no destination
+<Breadcrumb>
+  <BreadcrumbItem label="Help centre" href="/help" />
+  <BreadcrumbItem label="Account" />
+  <BreadcrumbItem label="Verification" current />
+</Breadcrumb>
+```

package/.llm/components/breadcrumbitem.md

@@ -0,0 +1,186 @@
+<!-- GENERATED from breadcrumb-item.contract.json. Do not edit. -->
+
+# BreadcrumbItem
+
+One level in a Breadcrumb on a marketing site. It renders either a link back to that level or, for the level the visitor is already on, plain text marked as the current page. It knows nothing about the levels around it — what order they come in and what sits between them belongs to the trail, not to any level in it.
+
+## Use when
+
+- Rendering one level of a Breadcrumb — every level in a trail is one of these
+- The level needs a short name the visitor recognises as a place: the section name, not a sentence about it
+
+## Do not use
+
+- The destination is somewhere the visitor goes to act rather than a level they climb back to → nothing here does this
+- A level on its own, outside a Breadcrumb. The separators, the ordering and the landmark all belong to the trail, so a lone item is a link with none of the meaning that made it a level
+- The page title. The current item names the page in the trail, in the words the parent level would use for it — a heading is free to be longer, and copying one into the trail makes the row wrap for nothing
+- A level the visitor cannot actually reach. An item with no href is text, and text the visitor tries to click is a promise the trail did not keep
+
+## Anatomy
+
+BreadcrumbItem renders 3 elements. A token binding names the part it applies to.
+
+- `root` — `<li>`, class `dds-breadcrumbitem`. The level, as a list item. An li because the trail is an ordered list and this is one of its entries; it carries no colour of its own, so whichever of the two parts below renders is what the visitor reads.
+  
+  It takes `font.label.sm`, which is the role rather than merely the size. A trail is interactive text in a supporting position — the step's own description names footer links — and that is what a breadcrumb is: navigation the page offers without asking to be read. `body.sm` is the other measure at fourteen and is for disclaimers and copyright lines, which a trail is not.
+  
+  The whole role rather than a family and a size. A step changed without the line box it belongs to takes its leading from whatever the page happens to set, which is a measurement nobody made.
+  
+  The weight is not the root's, because the two kinds of level disagree about it: a link is regular and the level the visitor is on is not. Each part names its own, and the difference between them is the whole of how a trail says where you are.
+- `link` — `<a>`, class `dds-breadcrumbitem__link`. The way back to this level. A real anchor rather than a handler on a span, so it opens in a new tab on the modifier the visitor already knows, it is announced as a link, and the keyboard reaches it without a line of script. Underlined only on hover: a trail whose every level is underlined competes with the page's own content for attention. Rendered only when `href` is set.
+- `current` — `<span>`, class `dds-breadcrumbitem__current`. The level the visitor is on. A span rather than a link, because there is nowhere for it to go, and heavier than the levels before it so the end of the trail is where the eye stops. Carries aria-current, which is the only thing that tells a screen reader user which of these levels is the page they are reading. Rendered only when `current` is set.
+
+Apply these classes from the generated `breadcrumbItemParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+
+## Props
+
+### label — `string` **Required.**
+
+Use when: Always — it is the level's name, and the item renders nothing without it. The word the parent level would use for this place: "Forex", not "Forex markets and instruments"
+Never for: A description of the level, or the page's full title. The trail is a row of names, and a name that explains itself is the thing that makes it wrap
+
+### href — `string`
+
+Use when: The level is one the visitor can return to — which is every level above the current page
+Never for: The current page. Linking the page to itself gives the visitor a link that does nothing and adds a tab stop that leads nowhere
+
+### current — `boolean` (default `false`)
+
+Use when: This is the level the visitor is on, which is the last item in the trail. It renders as text rather than a link and is announced as the current page
+Never for: Emphasis on a level that is not the current page. It is a statement about where the visitor is, not a way to make one level louder — and setting it alongside href asks for a link the item will not render
+
+Also accepts everything from `LiHTMLAttributes<HTMLLIElement>`.
+
+## 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: `listitem`
+- `Tab` — move focus to this level, when it is a link. The current page is text and takes no focus, so a trail of four levels is three tab stops
+- `Enter` — follow the link to this level, when the item is not the current page
+- the current page marked with aria-current="page", which is what identifies one of the levels as where the visitor is. Not verified here: the generated assertions compare an ARIA attribute against "true", and this one carries "page"
+- no link on the current page. An anchor pointing at the page it sits on is a tab stop that leads nowhere
+- a focus ring on every level that is a link, since the trail is often the first thing a keyboard user tabs into on the page
+
+## 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
+
+❌ BreadcrumbItem for: The destination is somewhere the visitor goes to act rather than a level they climb back to
+   A trail level is a place. A control that performs something is announced as a button and belongs where the action does, not in the hierarchy above the page
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ current=true + href is set
+   The two together ask for a link from the page to itself — a tab stop that goes nowhere. The component already declines to render one, current winning over href; this is the same refusal a compiler can make first.
+
+## Example
+
+```tsx
+import { BreadcrumbItem } from '@deriv-com/dds-marketing'
+
+<BreadcrumbItem label="Markets" href="/markets" />
+```
+
+## In use
+
+### A level, and the page
+
+The two states a trail is built from. Every level above the current page is a link; the page itself is text, heavier, and announced as where the visitor is.
+
+```tsx
+import { BreadcrumbItem } from '@deriv-com/dds-marketing'
+
+// A level above — a link back to it
+<BreadcrumbItem label="Markets" href="/markets" />
+
+// The current page — text, not a link
+<BreadcrumbItem label="Forex" current />
+```
+
+### A level with nowhere to go
+
+An item with neither href nor current renders as bare text — what an unresolved level looks like, not a state to reach for.
+
+```tsx
+import { BreadcrumbItem } from '@deriv-com/dds-marketing'
+
+// No href — text the visitor may still try to click
+<BreadcrumbItem label="Archived" />
+```