@deriv-com/dds-marketing 1.0.2 → 1.1.1

package/.llm/components/resourcebanner.md

@@ -0,0 +1,247 @@
+<!-- GENERATED from resource-banner.contract.json. Do not edit. -->
+
+# ResourceBanner
+
+A dark panel at the end of an informational section that points readers at related guides, policies or reference pages — the "here's where to read more" block. A heading and a line on one side, a stacked list of links on the other.
+
+The reference site's ResourceBanner, named the same. The links are a list at every width, so one link and four read the same way: a reader counts them and picks one, and none of them is a call to action.
+
+The section sits on the page's own ground by default; `ground` paints the grey or the dark band behind the panel where the section needs setting apart from the ones around it. The panel is dark on all three.
+
+## Use when
+
+- Pointing readers at related guides, policies, or reference pages at the end of an informational section — the 'here's where to read more' block
+- A section of a legal, help or safety page has said what it has to and the detail lives elsewhere — the full terms, a risk disclosure, a help-centre article
+
+## Do not use
+
+- The block asks the reader to do something — open an account, start trading → `CtaBanner`
+- The resources are a set of destinations each worth a heading and a sentence → `FeatureCards`
+- The reader's questions have short answers that can be given on the page → `FaqAccordion`
+- A call to action. Nothing here is a button, and a resource the page wants pressed more than the others is not a resource
+- More than four or five links. Past that the stack competes with the words beside it, and the set is a page of links of its own
+- Links whose words only make sense beside the heading — "Read more", "Here". The stack is read as a list, and a screen reader lists links on their own
+
+## Anatomy
+
+ResourceBanner renders 8 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-resourcebanner`. The section. It paints the ground behind the panel and the ink to go with it — see `ground` — and asks its own width, so the panel folds on the section's measure rather than the window's. A region named by its heading, so a reader can jump to it and past it.
+- `inner` — `<div>`, class `dds-resourcebanner__inner`. The measure and the gutter, the same column every band holds its content in: size.content.max, space.inset.page, space.section.default.
+- `panel` — `<div>`, class `dds-resourcebanner__panel`. The dark card, and the reference's own: a rounded panel holding the words and the links. One column on a phone with the links under the words; two equal columns from the fold; and at full width the words take two shares to the links' one, because the words are read and the links are picked from.
+  
+  Painted color.bg.surface-card-strong, the dark card's fill, with color.fg.on-brand-strong for everything on it — white in both modes, since the panel does not change. On the grey band it lifts to color.bg.surface-card-strong-raised. The gap between the halves is space.heading.content: a heading group and what it introduces, turned on its side.
+- `content` — `<div>`, class `dds-resourcebanner__content`. The heading and the line under it. A gap rather than the title's margin, so a block with no description closes up rather than leaving the step behind.
+- `title` — `<h2>`, class `dds-resourcebanner__title`. What the links are for. h2 by default because the block is a section of a page; `headingLevel` moves the level and never the size.
+- `description` — `<p>`, class `dds-resourcebanner__description`. The sentence introducing the links, at body size and the description measure. Rendered only when `description` is set.
+- `list` — `<ul>`, class `dds-resourcebanner__list`. The resources, as a list rather than a stack of divs — a screen reader announces how many there are before reading one. A column at every width, so one link and four use the same layout. Under the words on a phone; centred in its column beside them from the fold, as the reference sets it, with the rows sharing one start edge so the set still reads as a list.
+- `item` — `<li>`, class `dds-resourcebanner__item`. One resource: a standalone Link in the panel's own ink, marked with Link's arrow, its up-right arrow when it leaves the site, or a file when it is a download. At least size.target.min tall, and the link stretches to fill it, so a row is never a smaller target than the rule allows. Positioned, because an external link or a download carries words that are heard and never drawn, and those are held inside the row.
+  
+  The rows arrive one after another under the words, in the order they are read.
+
+Apply these classes from the generated `resourceBannerParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `ResourceBanner`, `CtaBanner`, `CtaBannerSlider`, `PageHeader`, `LandingHero`, `ProductHero`, `Footer`, `Navbar`, `Button` — in children or in any prop that takes a node
+
+## Props
+
+### ground — `page` | `subtle` | `strong` (default `page`)
+
+- `page` — The default, and the page's own white. A section that has nothing to separate itself from what is above it
+- `subtle` — The reference design's arrangement: the dark panel on the light grey band. The one to reach for when the section ends a run of white ones and wants to read as its close. Painted as the band's tint laid over the page's own ground, so it is the same grey whatever is behind the section.
+- `strong` — `color.bg.brand-strong`, the dark band. The panel is a step lighter than it, so it still reads as a panel — but a dark panel on a dark band is a quiet one, and this is for a page whose sections around it are already dark
+
+Use when: Which of the page's three grounds the section paints behind the panel. The reference design sets its panel on a light grey band, which is `subtle`; the page's own white is the default because the section above knows nothing about this one, and the page is the only thing that can build the rhythm.
+
+The panel is dark on every ground and carries its own ink, so this changes only what surrounds it — and on the grey band the panel lifts a step, color.bg.surface-card-strong-raised, so in dark mode it does not blend into the band's tint.
+Never for: Marking importance. A list of further reading is the quietest thing on a page, and painting the band dark to make it louder is a page with its emphasis in the wrong place.
+
+And never the brand's coral, `color.bg.brand`, which is not offered. That ground belongs to the band that asks a reader to do something, and a list of links on it is a call to action with nothing to press.
+
+### title — `string` **Required.**
+
+Use when: Always. What the links are for, in a few words — "Learn more about staying safe", "Read more about trading risks".
+Never for: A sentence. The description is for the sentence; the title names what the reader will find.
+
+### headingLevel — `h2` | `h3` | `h4` (default `h2`)
+
+- `h2` — The default: the block is a section of the page, under the page's own h1
+- `h3` — The block closes a section that already carries the h2 it belongs to
+- `h4` — The block closes a subsection under an h3, on a long legal or help page whose outline runs that deep
+
+Use when: Matching the outline of the page around the block, so the heading keeps its place in the hierarchy rather than skipping a level. Size does not change with it — the heading is drawn at font.h2 at every level, the scale and the level being separate decisions.
+
+### description — `string`
+
+Use when: One sentence introducing the links — what the reader will find there, or why it is worth reading.
+Never for: A summary of the links. They say what they are; this says why they are together. A second sentence is copy the reader passes on the way to the list.
+
+### links — `data` `ResourceBannerLink[]` **Required.**
+
+Use when: Always. The resources, in the order they are read — one to four, each named for what is there: the guide, the policy, the page. Mark one `external` when it leaves the site, so it opens in a new tab and says so, and `download` when it is a file rather than a page. A row with no label or no href is dropped rather than drawn.
+Never for: A link that is the page's call to action, or a label that only makes sense beside the heading. Each one is heard on its own in a screen reader's list of links.
+
+### externalLabel — `string` (default `(opens in a new tab)`)
+
+Use when: What an external link's accessible name ends with, so a reader who cannot see the up-right mark is told before their tab changes. Never drawn — the mark says it to everyone else. Translate it with the page.
+
+### downloadLabel — `string` (default `(downloads a file)`)
+
+Use when: What a download's accessible name ends with, so a reader who cannot see the file mark knows the link saves something rather than opening a page. Never drawn. Translate it with the page, and name the format in the link's own label when it matters — "Risk disclosure (PDF)".
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- Announced as: `region`
+- `Tab` — Moves through the links in the order they are listed. Nothing in the block is a composite widget.
+- accessible name from title, so the block is a named region a screen reader can jump to and skip
+- The resources are a list element, so a screen reader announces how many there are before reading the first
+- An external link or a download says so in its accessible name, not only in its mark. The mark is decorative and announced as nothing, so `externalLabel` and `downloadLabel` are appended to the link's words, heard and never drawn
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+- **A component is written along the reading axis, not along the page's left and right** — Every measure, inset and placement in this package names an axis rather than a side: inline-size and block-size, padding-inline and padding-block, inset-inline-start and inset-block-end, margin-inline: auto, text-align: start. Written that way a component follows whichever direction the page is read in, and a band whose claim ranges to the leading edge with its subject on the trailing one is the same composition in Arabic as in English, mirrored, with nothing restated. Written as left and right it is the same pixels in both, which is a layout nobody designed for the second language.
+
+The enum values follow the same rule and for the same reason. A prop that names where a picture sits takes start and end, never left and right — FeatureSplit, FeatureBullets and FeatureScroll all declare mediaPosition that way, and the flex directions they generate flip on their own because row already means the reading order. A value called left would have to be re-read as right by every author working in a mirrored page, which is a translation this system should be doing rather than asking for.
+
+The guidance a contract carries is part of the component, so it follows too. Describing a claim as ranging left is describing one of the two languages, and it was written that way here for a while: three of the opening bands said so in their own intent. A reader in a mirrored page meets that sentence and has to decide whether the component is wrong or the sentence is, and neither answer is one documentation should force.
+
+Two things genuinely have no logical form and are not covered by this. A CSS gradient takes a physical direction — there is no to inline-end — so a pattern that must mirror has to be stated twice under a direction query, and one that is periodic and centred, like PageHeader's rule grid, does not need to. A glyph that points the way onward is the other: an arrow is a picture of a direction, and mirroring it belongs to the icon set rather than to the component holding it.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ ResourceBanner for: The block asks the reader to do something — open an account, start trading
+   A call to action is a button on the brand's coral. These are reading, not doing, and a list of links dressed as a promotion is a promotion with nothing to press
+   → use `CtaBanner` instead.
+
+❌ ResourceBanner for: The resources are a set of destinations each worth a heading and a sentence
+   A card per destination says what each one is; a link per destination only names it. Past a name, the reader is comparing rather than picking
+   → use `FeatureCards` instead.
+
+❌ ResourceBanner for: The reader's questions have short answers that can be given on the page
+   An answer sent elsewhere is an answer the reader has to go and get. If it fits on the page, put it there
+   → use `FaqAccordion` instead.
+
+## Example
+
+```tsx
+import { ResourceBanner } from '@deriv-com/dds-marketing'
+
+<ResourceBanner ground="subtle" title="Read more about trading risks" description="Our policies and guides explain how trading works, what it can cost you, and how we protect your account." links={[{"label":"Terms and conditions","href":"/terms-and-conditions"},{"label":"Risk disclosure (PDF)","href":"/regulatory/risk-disclosure.pdf","download":true},{"label":"How to trade responsibly","href":"https://example.com/help/responsible-trading","external":true}]} />
+```
+
+## In use
+
+### How many links
+
+The links are a list at every width, so one and four use the same layout. Past four the stack competes with the words.
+
+```tsx
+import { ResourceBanner } from '@deriv-com/dds-marketing'
+
+// One external link
+<ResourceBanner title="Learn more about staying safe" description="Read our guide on secure and responsible trading for more on protecting your account." links={[{"label":"Secure and responsible trading","href":"https://example.com/responsible","external":true}]} />
+
+// Four links, no description
+<ResourceBanner title="Our policies" links={[{"label":"Terms and conditions","href":"/terms-and-conditions"},{"label":"Privacy policy","href":"/privacy"},{"label":"Complaints policy","href":"/complaints"},{"label":"Risk disclosure (PDF)","href":"/regulatory/risk-disclosure.pdf","download":true}]} />
+```
+
+### The three grounds
+
+The panel is dark on every ground and carries its own ink; the ground changes only what is around it.
+
+```tsx
+import { ResourceBanner } from '@deriv-com/dds-marketing'
+
+// ground="page"
+<ResourceBanner ground="page" title="Read more about trading risks" links={[{"label":"Terms and conditions","href":"/terms-and-conditions"},{"label":"Risk disclosure (PDF)","href":"/regulatory/risk-disclosure.pdf","download":true}]} />
+
+// ground="subtle" — the reference's arrangement
+<ResourceBanner ground="subtle" title="Read more about trading risks" links={[{"label":"Terms and conditions","href":"/terms-and-conditions"},{"label":"Risk disclosure (PDF)","href":"/regulatory/risk-disclosure.pdf","download":true}]} />
+
+// ground="strong"
+<ResourceBanner ground="strong" title="Read more about trading risks" links={[{"label":"Terms and conditions","href":"/terms-and-conditions"},{"label":"Risk disclosure (PDF)","href":"/regulatory/risk-disclosure.pdf","download":true}]} />
+```
+
+### Inside a section
+
+Closing a section that already has its heading, the level drops and the size stays.
+
+```tsx
+import { ResourceBanner } from '@deriv-com/dds-marketing'
+
+// headingLevel="h4"
+<ResourceBanner title="Related guides" headingLevel="h4" links={[{"label":"Margin and leverage explained","href":"/help/margin"},{"label":"Trading glossary","href":"/help/glossary"}]} />
+
+// headingLevel="h3"
+<ResourceBanner title="Further reading on deposits" headingLevel="h3" description="Fees, limits and processing times for every payment method we support." links={[{"label":"Payment methods","href":"/payment-methods"},{"label":"Deposits and withdrawals help","href":"https://example.com/help/deposits","external":true}]} />
+```

package/.llm/components/scenescroll.md

@@ -0,0 +1,222 @@
+<!-- GENERATED from scene-scroll.contract.json. Do not edit. -->
+
+# SceneScroll
+
+A full-screen section of two scenes — each a photograph filling the band with a heading and a line over it — that change over as the reader scrolls: the screen holds still while the second photograph dissolves in over the first and the first scene's words give way to the second's. Two states of one thing told by the scroll — day and night, before and after, the market open and the market that never closes.
+
+The reference design's DayNightTransition, made generic: nothing in it is about the time of day. The change-over is scrubbed by the scroll itself and run by the stylesheet alone — the section is a tall track whose view timeline drives the dissolve while a screen-tall stage stays pinned inside it — so it runs forward as the reader scrolls down, back as they scroll up, and stands still while the page does. Without a scroll timeline, for a reader who asked for less motion, and before any script, the two scenes are simply drawn one after the other, each a screen tall, with both sets of words readable.
+
+## Use when
+
+- Two states of one thing a page wants felt rather than listed — the markets by day and by night, a trader's screen before and after, a market open around the clock
+- One immersive moment on a product or campaign page, between lighter sections, where two photographs carry the argument and the words are a heading and a line each
+- The opening band of a campaign page built around that change, at headingLevel h1
+
+## Do not use
+
+- There is one photograph, not two states of something → `ImageBanner`
+- Three or more things to show, each with a picture → `FeatureScroll`
+- The page's opening band, with an action to take → `LandingHero`
+- One statement on its own, revealed as the reader scrolls → `TextScroll`
+- Words a reader must not miss — a price, a disclaimer, a legal line. Each scene's words are on screen for only part of the pass
+- Two of these on one page, or one beside another pinned section. Each holds the screen for a screen and a half of scrolling, and two make the page feel stuck
+- Photographs with words in them. The words are the headings and the lines, where a screen reader and a translation reach them; a photograph saying them is under a scrim and cropped to fill
+- An action. There is no slot for one: a button that dissolves away as the reader scrolls is one they cannot rely on, so the page's next section carries it
+
+## Anatomy
+
+SceneScroll renders 9 elements. A token binding names the part it applies to.
+
+- `root` — `<section>`, class `dds-scenescroll`. The section, a region named by the first scene's title. Where the scroll drives the change-over it is the track: two and a half screens tall, and the view timeline the dissolve runs down. Elsewhere it is as tall as the two scenes it holds. It paints color.bg.brand-strong under the photographs and sets color.fg.on-brand-strong, white in both modes, for the words over them. It clips with `overflow: clip` if it ever clips, never `hidden`, which would make it a scroll container and freeze the timeline and the pin.
+- `stage` — `<div>`, class `dds-scenescroll__stage`. What the reader sees. Where the scroll drives the change-over it is a screen tall and pinned to the top of the window for the length of the track, with both scenes stacked in its one cell. Elsewhere it is a column of the two scenes, one after the other with nothing between them.
+- `scene` — `<div>`, class `dds-scenescroll__scene`. One scene, drawn twice — `data-scene` says which. A screen tall, the photograph behind and the words over it, inset by the section's air and the page's gutter. Isolated, so the second scene's photograph covers the first scene's words as well as its photograph as it dissolves in.
+- `media` — `<div>`, class `dds-scenescroll__media`. The scene's photograph, filling the scene edge to edge and square-cornered, under a scrim of color.bg.overlay so the white words keep AA contrast over any photograph, a pale one included. The second scene's photograph and its scrim dissolve in together over the first's.
+- `image` — `<img>`, class `dds-scenescroll__image`. The photograph, drawn from the scene's `image` and cropped to fill the scene. Its `alt` is the scene's own: empty for a photograph that is decoration, which most are here.
+- `content` — `<div>`, class `dds-scenescroll__content`. The scene's words — its title and the line under it — over the photograph, held to the heading group's measure. At the top of the stage and at the start below 62rem, under the room a navigation bar takes; centred across and down from 62rem — the reference design's arrangement, at its 992px. Where the scroll drives the change-over the first scene's words fade out and then the second scene's fade in, in the same place; both are in the DOM and read in order the whole time, and neither is ever hidden from assistive technology.
+- `title` — `<h2>`, class `dds-scenescroll__title`. The scene's title. The first scene's is at `headingLevel` and names the section; the second's is one level under it. Both drawn at the size `headingLevel` names, font.h2 or font.h1.
+- `description` — `<p>`, class `dds-scenescroll__description`. The line under a scene's title, at the large body step and the description measure. Drawn only for a scene that has one.
+- `link` — `<div>`, class `dds-scenescroll__link`. The section's way on, right under the words. While the scenes change over, both scenes' words share one area of the stage, as tall as the taller of them, and the link is the row under it — under the text on every screen, and still while the text changes. At the top of the stage with the words below 62rem, at the start; centred with them from 62rem. In the plain fallback, where the scenes stack, it follows the second. Rendered only when `link` is set.
+
+Apply these classes from the generated `sceneScrollParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+- Never contains: `SceneScroll`, `FeatureScroll`, `LandingHero`, `ProductHero`, `PageHeader`, `Footer`, `Navbar` — in children or in any prop that takes a node
+
+## Props
+
+### headingLevel — `h2` | `h1` (default `h2`)
+
+- `h2` — The default: the section sits under the page's own h1, and the scenes' titles are drawn at font.h2
+- `h1` — The section opens a campaign page and the first scene's title is the page's heading — the reference design's hero use. Drawn at font.h1, the opening band's size
+
+Use when: Where the first scene's title sits in the page's outline. The second scene's title takes the level under it — h2 under an h1, h3 under an h2 — because it is the second half of the section the first one names, not a section of its own. Both are drawn at the same size, the one this names: a scene is a screen of photograph, and an h2 sized as a card title would be lost on it.
+Never for: Making a mid-page section look like a hero. h1 is the page's heading, and a page has one.
+
+### first — `data` `SceneScrollScene` **Required.**
+
+Use when: Always. The scene the section opens on: a title in a few words, a line under it where the title needs one, and the photograph filling the band behind them. Its title names the section, so it is the one to write as the section's heading. Give the photograph's width and height; `alt` empty unless it shows something the words do not.
+Never for: A scene that says the same as the second with a different picture. The change-over is the argument; two scenes that agree have nothing to change between.
+
+### second — `data` `SceneScrollScene` **Required.**
+
+Use when: Always. The scene the section changes over to, in the same shape as the first. A title of about the same length as the first, so the words change in place rather than jumping, and a photograph of the same composition where there is one, so the dissolve reads as one place changing rather than a cut.
+Never for: A continuation of the first scene's sentence. A reader who arrives by heading, or who scrolls past fast, reads each title on its own.
+
+### link — `node`
+
+Accepts: Link
+Use when: A way on for the reader who wants more — "See trading hours", "Learn more". A standalone Link under the words, and it stays put through the change-over: it belongs to the section rather than to either scene, so it never fades while the reader is reaching for it.
+Never for: A button, or a different link per scene. One way on for the section; something to press that changed under the pointer would be the one thing a reader could not rely on.
+
+## Accessibility
+
+Guaranteed by the component. Write none of it by hand: the ids these attributes point at are generated per instance, so an attribute set from outside either says the same thing twice or points at nothing.
+
+- Announced as: `region`
+- `Tab` — Moves past the section. Nothing in it is operable — the scenes are read, not used — so there is nothing here to land on.
+- The section is a region named by the first scene's title, through aria-labelledby, so a reader can jump to it and past it. Named by a heading already on the page rather than a hidden label of its own, so what is announced is what is shown
+- Both scenes' words are in the DOM, in order — the first scene's title and line, then the second's — whatever the scroll has faded. The visual change-over never hides either scene's words from assistive technology, never removes them, and never re-orders them
+- The words over the photographs keep AA contrast whatever the photograph: each scene's photograph sits under a scrim of color.bg.overlay, and the words are white in both modes, so a pale photograph is darkened rather than trusted to be dark
+- Without a scroll timeline, for a reader who asked for less motion, and before any script, nothing is faded and nothing is pinned: the two scenes are drawn one after the other, each with its words at full strength
+- Each photograph's alt is the one its scene was given — empty for a photograph that is decoration
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, CardButton and TextInput simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+- **A component is written along the reading axis, not along the page's left and right** — Every measure, inset and placement in this package names an axis rather than a side: inline-size and block-size, padding-inline and padding-block, inset-inline-start and inset-block-end, margin-inline: auto, text-align: start. Written that way a component follows whichever direction the page is read in, and a band whose claim ranges to the leading edge with its subject on the trailing one is the same composition in Arabic as in English, mirrored, with nothing restated. Written as left and right it is the same pixels in both, which is a layout nobody designed for the second language.
+
+The enum values follow the same rule and for the same reason. A prop that names where a picture sits takes start and end, never left and right — FeatureSplit, FeatureBullets and FeatureScroll all declare mediaPosition that way, and the flex directions they generate flip on their own because row already means the reading order. A value called left would have to be re-read as right by every author working in a mirrored page, which is a translation this system should be doing rather than asking for.
+
+The guidance a contract carries is part of the component, so it follows too. Describing a claim as ranging left is describing one of the two languages, and it was written that way here for a while: three of the opening bands said so in their own intent. A reader in a mirrored page meets that sentence and has to decide whether the component is wrong or the sentence is, and neither answer is one documentation should force.
+
+Two things genuinely have no logical form and are not covered by this. A CSS gradient takes a physical direction — there is no to inline-end — so a pattern that must mirror has to be stated twice under a direction query, and one that is periodic and centred, like PageHeader's rule grid, does not need to. A glyph that points the way onward is the other: an arrow is a picture of a direction, and mirroring it belongs to the icon set rather than to the component holding it.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ SceneScroll for: There is one photograph, not two states of something
+   One photograph with words over it is a cover banner; a scene that never changes over is a section a screen tall for nothing
+   → use `ImageBanner` instead.
+
+❌ SceneScroll for: Three or more things to show, each with a picture
+   FeatureScroll pins a picture beside a list of stops a reader moves through; this is exactly two full-screen scenes and the change between them
+   → use `FeatureScroll` instead.
+
+❌ SceneScroll for: The page's opening band, with an action to take
+   An opening band asks for something under its claim; this has no action, and a call to action dissolving away under the scroll is one a reader cannot rely on
+   → use `LandingHero` instead.
+
+❌ SceneScroll for: One statement on its own, revealed as the reader scrolls
+   A sentence brightening word by word is the moment there; here the photographs are
+   → use `TextScroll` instead.
+
+## Example
+
+```tsx
+import { SceneScroll } from '@deriv-com/dds-marketing'
+
+<SceneScroll first={{"title":"Your trading desk, at the open","description":"Charts, prices and positions in one place, ready when the market is.","image":{"src":"/sample-band-ground.svg","alt":"","width":1600,"height":900}}} second={{"title":"And the same desk, at the close","description":"Every trade of the day in one view, with nothing left to reconcile.","image":{"src":"/sample-stop-blue.svg","alt":"","width":800,"height":600}}} />
+```
+
+## In use
+
+### Where it sits in the page's outline
+
+h2 under the page's own heading, or h1 when the section opens a campaign page. The size follows the level; the second title is always one level under the first.
+
+```tsx
+import { SceneScroll } from '@deriv-com/dds-marketing'
+
+// h2 — a section of the page, the default
+<SceneScroll first={{"title":"Your trading desk, at the open","description":"Charts, prices and positions in one place, ready when the market is.","image":{"src":"/sample-band-ground.svg","alt":"","width":1600,"height":900}}} second={{"title":"And the same desk, at the close","description":"Every trade of the day in one view, with nothing left to reconcile.","image":{"src":"/sample-stop-blue.svg","alt":"","width":800,"height":600}}} />
+
+// h1 — the opening band of a campaign page
+<SceneScroll headingLevel="h1" first={{"title":"Your trading desk, at the open","description":"Charts, prices and positions in one place, ready when the market is.","image":{"src":"/sample-band-ground.svg","alt":"","width":1600,"height":900}}} second={{"title":"And the same desk, at the close","description":"Every trade of the day in one view, with nothing left to reconcile.","image":{"src":"/sample-stop-blue.svg","alt":"","width":800,"height":600}}} />
+```
+
+### Two states of one thing
+
+Day and night is one pair among many. Photographs of the same composition make the dissolve read as one place changing rather than a cut.
+
+```tsx
+import { SceneScroll } from '@deriv-com/dds-marketing'
+
+// Markets that never close
+<SceneScroll first={{"title":"Markets that never close","description":"Trade forex, stocks and commodities from the first bell to the last.","image":{"src":"/sample-band-ground.svg","alt":"","width":1600,"height":900}}} second={{"title":"And trade on through the night","description":"Derived indices run every hour of every day, weekends included.","image":{"src":"/sample-stop-purple.svg","alt":"","width":800,"height":600}}} />
+```
+
+### With a way on
+
+An optional link under the words. It holds still through the change-over, so it is under whichever scene's text is showing.
+
+```tsx
+import { Link, SceneScroll } from '@deriv-com/dds-marketing'
+
+// A link under the words
+<SceneScroll first={{"title":"Your trading desk, at the open","description":"Charts, prices and positions in one place, ready when the market is.","image":{"src":"/sample-band-ground.svg","alt":"","width":1600,"height":900}}} second={{"title":"And the same desk, at the close","description":"Every trade of the day in one view, with nothing left to reconcile.","image":{"src":"/sample-stop-blue.svg","alt":"","width":800,"height":600}}} link={<Link href="/trading-hours" tone="inherit">See trading hours</Link>} />
+```

package/.llm/components/select.md

@@ -222,6 +222,23 @@ Never for: Marking every optional control on a form where most are optional —
 Use when: Saying what the status means: what is wrong and how to fix it, what to look at, or what was confirmed
 Never for: Restating the status. "Error" beside a red control says nothing the colour has not, and the colour is the part a colour-blind reader may not get
 
+### requiredLabel — `string` (default `required`)
+
+Use when: The word drawn beside the label when requiredMark is text. Translate it with the page: the mark exists to say what it means in the reader's own language, which an English default does not.
+
+### optionalLabel — `string` (default `optional`)
+
+Use when: The word drawn beside the label of an optional field. Translate it with the page, as requiredLabel is.
+
+### labelTooltipLabel — `string`
+
+Use when: The accessible name of the button that opens labelTooltip. Without it the button is named "About" and the label; pass it to translate that with the page.
+Never for: Visible text. It names the button to assistive technology and is never drawn.
+
+### searchLabel — `string`
+
+Use when: The name and placeholder of the search field a searchable list opens with. Without it the field reads "Search" and the label; pass it to translate that with the page.
+
 Also accepts everything from `ButtonHTMLAttributes<HTMLButtonElement>`.
 
 ## States