@deriv-com/dds-marketing 0.1.0 → 0.2.0

package/.llm/components/textinput.md

@@ -0,0 +1,467 @@
+<!-- GENERATED from text-input.contract.json. Do not edit. -->
+
+# TextInput
+
+One line of text a visitor types before they are a customer. A marketing page asks for very little and has no standing to ask for more: an email for a newsletter, a name and a message on a contact form, a work address to book a demo. Every one of those is a stranger deciding whether the thing on offer is worth handing something over for, and the field is where that decision gets made or lost.
+
+That is the whole difference from a field in an application, and it is why this is not Product's TextInput with fewer props. An app's field is filled by someone who has already signed up, inside a task they have committed to, and can afford to ask for an account number in a particular format. A landing page's field is filled by someone with no account, no stake, and a back button — so it asks for one thing, says what it will do with it, and is legible enough at a glance that nobody has to work out what goes in it.
+
+One field for one value — and it now carries the same furniture Product's does: affixes, ornaments, a clear button, an explanation beside the label, and the four verdicts a check can return. What is still not here is the family. A one-time code, a phone field with country logic, an amount field with its own arithmetic: those are components rather than props, and a page needing one has stopped being marketing.
+
+## Use when
+
+- A page asks for an email — a newsletter, a waitlist, a download behind an address
+- A short form stands between the reader and something they want: a demo booking, a contact request, a callback
+- A value is genuinely one line and the reader can type it without looking anything up
+
+## Do not use
+
+- The value is more than a line — a message, a description, an enquiry → nothing here does this
+- The reader is choosing from a set rather than typing → nothing here does this
+- The field is a query against something on the page → nothing here does this
+- Asking for more than the page has earned. Every extra field is a reason to leave, and a marketing form is judged on how little it asks — a name and an email convert where a name, an email, a company, a role and a phone number do not
+- Sensitive data. A landing page has no account, no session and usually no reason to be trusted with anything more than an address. Card numbers, identity documents and passwords belong behind a sign-in, on a page built to hold them
+- A label the reader cannot see. The placeholder is not a label — it disappears the moment they type, taking with it the only thing telling them what the field was for, and it is the first thing lost when someone comes back to check what they filled in
+- Layout. A disabled field holding a value the reader cannot change is not a way to present information — that is copy, and it reads better as copy
+
+## Anatomy
+
+TextInput renders 16 elements. A token binding names the part it applies to.
+
+- `root` — `<div>`, class `dds-textinput`. The field and everything that explains it, stacked. A column rather than a row: a label beside its field survives one language and one width, and a marketing page is neither — it is translated, and it is read at 360 pixels as often as at 1440.
+  
+  It is the stacking context for the whole component, so the gap between the label, the control and whatever sits underneath is one decision made here rather than three margins that drift apart.
+- `label-row` — `<div>`, class `dds-textinput__label-row`. Holds the label and, when there is one, the button that explains it. The trigger cannot sit inside the <label>: a label forwards its clicks to the field, so a button in there is an ambiguous target and the no-nested-interactive rule refuses it.
+  
+  Always rendered, so the markup has one shape whether the field carries an explanation or not.
+- `label` — `<label>`, class `dds-textinput__label`. What the field is for, in words, above it and always drawn.
+  
+  Always, and this is the one thing about this component not open to negotiation. A placeholder is not a label: it vanishes on the first keystroke, so the reader loses it exactly when they start needing it, and it is gone entirely when they come back to check what they typed. A field labelled only by its placeholder is also a field a screen reader announces as "edit blank" the moment the user has typed anything at all.
+  
+  It is a real `<label>` with a `for`, rather than an `aria-label` on the input. Clicking the words focuses the field, which is the behaviour every reader already expects and the one thing `aria-label` cannot give them.
+- `required-mark` — `<span>`, class `dds-textinput__required-mark`. The mark beside the label saying this one cannot be skipped. Red, in `color.fg.required` rather than `color.fg.danger` — the same colour today and a separate decision, because required is not a verdict. A field marked required has not failed anything yet, and the day error red moves, this should not move with it unless somebody decides it should.
+  
+  It is a mark and not the message. Carrying the requirement in colour alone would leave it to a reader who can see red, which is why `aria-required` on the field says the same thing in the accessibility tree and neither one is doing the job alone. Rendered only when `required` is set.
+- `optional-mark` — `<span>`, class `dds-textinput__optional-mark`. The word beside the label saying this one may be skipped.
+  
+  Not hidden from screen readers, unlike the required mark: there is no ARIA attribute for optional, so this text is the only thing carrying it. It joins the accessible name and is read as 'Label optional' — verbose, and the alternative is saying nothing at all. Rendered only when `optional` is set.
+- `label-tooltip` — `<button>`, class `dds-textinput__label-tooltip`. The button that reveals the explanation, drawn beside the label rather than under it.
+  
+  A tab stop by intent. An explanation only a pointer can reach is one half the people filling the form never see, and the cost is one stop before a field that opted into having more to say. Rendered only when `labelTooltip` is set.
+- `control` — `<div>`, class `dds-textinput__control`. The box the reader aims at: the border, the ground, the radius and the focus ring live here rather than on the input.
+  
+  A wrapper around a single input looks like an element that does nothing, and it is the opposite. It is what lets the field be styled as a target without touching the input's own box, which browsers style in ways that differ per platform and are not entirely overridable; and it is where a leading glyph or a clear button would attach the day this component earns one. Without it, adding either means re-drawing the border somewhere else and every bound token moves.
+- `leading-icon` — `<span>`, class `dds-textinput__leading-icon`. A mark at the start of the field, before the value. Decoration that hints at what goes in the box — never the label, which is drawn above and always. Rendered only when `leadingIcon` is set.
+- `prefix` — `<span>`, class `dds-textinput__prefix`. Fixed text before the value, inside the box — a currency mark, a scheme. Part of the field's furniture and not part of its value: it is never submitted, and the reader cannot select or edit it. Rendered only when `prefix` is set.
+- `field` — `<input>`, class `dds-textinput__field`. The input itself, transparent and borderless — the control around it draws all of that. It carries the text, the placeholder, the type, and every state the browser owns.
+  
+  Its own background is `transparent` rather than a ground of its own, so the control's ground shows through and the readonly and disabled states each need colouring in one place instead of two that can disagree.
+- `suffix` — `<span>`, class `dds-textinput__suffix`. Fixed text after the value, inside the box — a unit, a domain. The same furniture as the prefix, at the other edge. Rendered only when `suffix` is set.
+- `clear` — `<button>`, class `dds-textinput__clear`. The button that empties the field, drawn at its trailing edge once there is something to empty.
+  
+  Gone when the value is not the reader's to change. Dimming it was not enough: the button sits inside the control, so the disabled state's opacity made it look unavailable while it stayed live and still emptied the field. Rendered only when `clearable` is set. Not rendered at all while `disabled` or `readonly`.
+- `trailing-icon` — `<span>`, class `dds-textinput__trailing-icon`. A mark at the end of the field, after the value. It holds the trailing edge, and the clear button appears inside it rather than shoving it sideways on every keystroke. Rendered only when `trailingIcon` is set.
+- `helper` — `<span>`, class `dds-textinput__helper`. Standing guidance under the field — what the address is for, what happens after they press send. It is there before anything goes wrong and stays there while the reader types.
+  
+  On a marketing form this is often the most valuable line on the page: "We will only email you about the launch" is the sentence that decides whether the address is real, and it belongs under the field rather than in the privacy policy.
+  
+  It gives way to the message when there is one. Both at once is two lines of small grey and red text under a field the reader is trying to fix, and the one that matters is the one they did not expect. Rendered only when `helperText` is set.
+- `message` — `<span>`, class `dds-textinput__message`. What went wrong, and enough to fix it. Replaces the helper rather than joining it.
+  
+  It says what to do, not that something is wrong: the field is already red and the reader can see that. "Enter an address like name@example.com" is a message; "Invalid" is the component telling the reader they have failed and leaving them there.
+  
+  It is announced as well as drawn — `aria-describedby` points the field at it — because a reader who submitted and was bounced back to a field they cannot see the bottom of gets nothing from a red line.
+  
+  A glyph sits beside the words, so a status is never carried by colour alone — red and the shape of a circled exclamation say the same thing to a reader who cannot tell the red from the grey. Rendered only when `status` is set.
+- `message-icon` — `<span>`, class `dds-textinput__message-icon`. The box the status glyph sits in, and the reason it is a part rather than the bare Icon it started as.
+  
+  Aligned to the start of the block axis, a glyph is a flex item as tall as itself — sixteen pixels against a line of type that is twenty-one — so its middle sat above the first line's and the words beside it read as pushed down. This is a box exactly one line of the message tall with the glyph centred in it, which puts the two middles on each other whatever the line turns out to hold.
+  
+  It carries the message's own font size and line height and nothing else; the height is those two multiplied, which happens in text-input-impl.css because a binding carries one token and not an expression over two. Absent for a pending check, which has no glyph — marketing has no Spinner to turn. Rendered only when `status` is set.
+
+Apply these classes from the generated `textInputParts` constant rather than writing the strings by hand.
+
+## Composition
+
+- Takes no children. Everything it renders comes from props
+
+## Props
+
+### size — `sm` | `md` | `lg` (default `md`)
+
+- `sm` — A field in a dense desktop arrangement — a filter row above a list, a field beside body copy rather than heading a section. Not on a phone, where thirty-two is below what a finger reliably hits
+- `md` — The default, and nearly every form on a page — an inline signup, a contact form in a section
+- `lg` — A hero's single field, or a conversion band where the form is the reason the section exists and has to be found from a distance
+
+### status — `none` | `error` | `warning` | `success` | `pending` (default `none`)
+
+- `none` — Nothing has been checked yet, which is the field for nearly all of its life — including before it has been filled in. Empty is not an error
+- `error` — Validation has failed and the reader has to change the value before the form will go anywhere
+- `warning` — The value is usable but worth a second look — a work address on a form that expected a personal one. The reader may keep it
+- `success` — A check has run and passed, and saying so is worth a line — an address confirmed as deliverable before the reader commits to it
+- `pending` — A check is in flight. The value is still the reader's to change while it runs
+Never for: Decoration, or a permanent state. A status is the result of checking a value, so a field that always looks like a warning is telling the reader nothing
+
+### type — `text` | `email` | `tel` | `url` (default `text`)
+
+- `text` — A name, a company, anything with no keypad or validation of its own
+- `email` — An address. It brings the right keypad on a phone — the @ without a modifier — which is the difference between a typo and a lost signup
+- `tel` — A phone number, for the numeric keypad. It does no validation and should not pretend to: numbers differ by country and a field that rejects a valid one is worse than a field that accepts anything
+- `url` — A website, on a form that asks for one
+Never for: Standing in for validation. The type chooses a keypad and a browser hint; what makes an address real is checked after the reader has submitted, and said in the message
+
+### label — `string` **Required.**
+
+Use when: Always — it names the field, it is drawn, and clicking it focuses the input. One or two words: 'Email', 'Full name', 'Work email'
+Never for: A sentence, or an instruction. What the field will do with the value is the helper's job, and a label long enough to wrap stops being something the eye can pair with a box
+
+### labelTooltip — `string`
+
+Use when: A field needs a sentence the label has no room for — why the address is being asked for, what happens to it
+Never for: Anything the reader must read to fill the field in. A tooltip is opened on purpose, so what is behind it is what a reader chose to want; the format and the consequence belong in helperText, which is simply there
+
+### placeholder — `string`
+
+Use when: Showing the shape of the value where the shape is not obvious — 'name@example.com' on an email field. It is an example, and it is allowed to be skipped
+Never for: The label. It disappears on the first keystroke, it is gone when the reader comes back to check, and it is announced as nothing once the field has text in it
+
+### helperText — `string`
+
+Use when: Saying what happens to the value — what the page will send, how often, what it will not do with the address. On a marketing form this is frequently what decides whether the reader types a real one
+Never for: Repeating the label in a longer form. A field labelled 'Email' with a helper reading 'Enter your email' has spent a line saying nothing
+
+### leadingIcon — `node`
+
+Accepts: QuillSystemIcon
+Use when: A mark that says what the field takes at a glance — an envelope on an address, a globe on a site
+Never for: The label. A glyph names nothing on its own, and a field identified only by a picture is a guess
+
+### prefix — `string`
+
+Use when: A fixed part of the value the reader should not have to type — a currency mark, https://
+Never for: Part of the value you expect back. It is furniture: it is never submitted and the reader cannot edit it
+
+### suffix — `string`
+
+Use when: A fixed tail — a unit, a domain every address on this form shares
+Never for: A unit the reader might need to change. If it is a choice it is a control, not a label stuck to the end of the box
+
+### trailingIcon — `node`
+
+Accepts: QuillSystemIcon
+Use when: A mark at the far edge that comments on the value rather than introducing it
+Never for: Anything pressable. It is an ornament, not a control — a button in here has no name and no keyboard route
+
+### clearable — `boolean` (default `false`)
+
+Use when: A field the reader is likely to retype rather than edit — a search term, a long address typed on a phone
+Never for: A short field on a desktop form. Select-all and type is already one gesture, and the button costs a target inside the box for every field that has one
+
+### clearLabel — `string` **Required when clearable=true.**
+
+Use when: Required whenever clearable is set. It is the button's only name — the glyph says nothing to a screen reader
+Never for: Describing the field. 'Clear email address' names the action; 'Email address' names the thing it acts on and is read as a second field
+
+### inputMode — `numeric` | `decimal`
+
+- `numeric` — Digits and nothing else — a postcode, a reference number
+- `decimal` — A number that may carry a separator — an amount
+Never for: Validation, or type. It chooses the keypad a phone raises and constrains nothing at all
+
+### statusMessage — `string` **Required when status=error, or when status=warning.**
+
+Use when: Saying what to change, when the status is an error. It replaces the helper while it is showing
+Never for: Announcing that something is wrong without saying what. The field is already red — a message reading 'Invalid' has added a colour and no information
+
+### required — `boolean` (default `false`)
+
+Use when: The form cannot be sent without this one, and the reader is better off knowing before they reach the button. It draws the mark and sets aria-required
+Never for: Validation. It says a field must be filled; whether what was filled in is any good is the status's job, after they submit
+
+### requiredMark — `text` | `asterisk` (default `text`)
+
+- `text` — The default. The word 'required' says what it means in the reader's own language and needs no key
+- `asterisk` — A dense form where the word would repeat down the column, and a legend explains the mark once
+Never for: Carrying the requirement on its own. The mark is decorative either way — aria-required on the field is what says it to a screen reader
+
+### optional — `boolean` (default `false`)
+
+Use when: Most of the form is required and one field is not. Marking the exception is what tells the reader anything
+Never for: Every field on a form where nothing is required. Marking all of them says the same as marking none, and costs a word on each
+
+Also accepts everything from `InputHTMLAttributes<HTMLInputElement>`.
+
+## States
+
+States you set. Everything else is driven by the browser.
+
+- `disabled` — The field is unavailable and nothing the reader does here will change that — a form waiting on something else to finish
+  Avoid when: The field is merely empty, or the form has not been submitted yet. A form that opens with half its fields switched off is a puzzle
+- `readonly` — written `readOnly` in JSX — The value is fixed but still worth reading — an address carried over from the previous step. It stays focusable and its text stays selectable, which is what separates it from disabled
+  Avoid when: Presenting information the reader cannot change. That is copy, and a greyed-out box is a worse way to show it
+
+## 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: `textbox`
+- `Tab` — move focus
+- programmatic label association
+- aria-invalid when the status is an error
+- aria-describedby pointing at statusMessage
+- aria-describedby pointing at helperText when no status is showing
+- aria-required when required
+
+## Rules
+
+- **On a phone a section's actions stack and each fills the width, including when there is only one** — On a phone a page's actions stack, and each one fills the width. Not most of it, and not the width its label happens to need — the whole column.
+
+Two side by side is what this replaces. On the narrowest screen each gets half a column minus the gap, which is rarely enough for a real label: the words wrap inside the pills, the two buttons come out different heights, and the pair reads as a broken row rather than as a choice. Stacked, each has the whole width and neither has to shorten its words to fit.
+
+A single action fills too, and that is the part worth saying, because it is the one that looks unnecessary. A lone button has the room to sit at its natural width and still should not: a full-width control is the phone's convention for the thing the screen is asking you to do, and a pill hugging its label reads as one option among others that are not there. It also makes the target predictable — the whole width, wherever the thumb lands — which a centred pill does not.
+
+Filling is the row's job rather than the button's. A button has no width of its own and is not given one; the row it sits in becomes a column and stretches its children, so nothing about the control changes and the same button is full width here and its own size on a desktop.
+
+This is the phone's breakpoint, size.breakpoint.md, and not the wider one that decides whether a heading is centred. Those are different questions and they break at different widths: a heading stops being centred when the measure is the screen, while a button stops being full width much sooner than that — stretched across a tablet it is a long way from its own label, and a label centred in a metre of pill is harder to hit than one in a pill the size of the words.
+
+What this is not about is every row of controls. A set of filter chips, a pagination strip, a toolbar, a link sitting after a sentence — none of these is the page asking for something, and stacking them to full width would turn a strip the eye skims into a list it has to read. The test is whether the row is the call to action the section was written for.
+  Guidance only — cannot be checked automatically.
+- **Never nest one interactive element inside another** — Nested interactive elements produce ambiguous hit targets and an unreachable inner control for keyboard and screen-reader users. This is why the rule cannot live on any single component — it constrains Button, Link, Input and Switch simultaneously.
+  Guidance only — cannot be checked automatically.
+- **A section that paints a ground sets the ink to go with it** — A page sits on color.bg.page, and a section that separates itself from it takes one of three grounds. color.bg.subtle is the light one and needs nothing further — the page's own ink still reads on it. The other two are dark and do not: color.bg.brand-strong takes color.fg.on-brand-strong, and color.bg.brand takes color.fg.on-solid. Both are white, and both are written as the role rather than the white they resolve to. Set one of those backgrounds without its ink and the text inherits whatever the page was already using, which is near-black on a dark band — legible to nobody, and invisible to every check here, because each pair passes contrast on its own and nothing can tell whether a section used both.
+
+color.bg.brand carries a second limit that is not about forgetting. Its ink measures 3.39:1, which clears the 3:1 a heading needs and misses the 4.5:1 running copy needs. A coral band may carry a headline and a call to action; a paragraph on one is text the reader has to work through at a ratio the waiver on that role does not cover — the waiver says so itself. A section with copy in it takes color.bg.brand-strong, which is near-black and carries white at full contrast.
+
+color.bg.strong is not a section ground. It is the inverted fill for an action that has to outrank what surrounds it, and the components that paint it — Button and ButtonIcon in their inverse form — already set both halves in one rule, which is the pattern a hand-painted section has to copy.
+  Guidance only — cannot be checked automatically.
+- **Every gap inside a section names the relationship it expresses, and the same relationship keeps its measure when it turns on its side** — A section's spacing is named by the relationship it expresses, not chosen by size. Every gap in a section has a role token, and reaching for a step off the generic scale because it happens to be the right number is how two sections written by two people stop lining up: the numbers agree today and drift the first time one of them is tuned.
+
+The heading group is three steps, not one gap. An eyebrow sits nearer its title than the title sits to its description, and the actions sit further from the description than either — space.heading.eyebrow-title, space.heading.title-description, space.heading.description-actions, in that order. A single `gap` on the group cannot say this; it sets all three the same and the block reads as evenly spaced lines rather than as a mark, a name and a paragraph. The eyebrow has to identify itself for this to work, because a group that opens with a title must not give its description the eyebrow's tighter step.
+
+The step between a title and its description follows the size of the title, which is why there are two of it. What a reader sees is not the gap but the gap plus the leading above it, and leading scales with the type: under a display title the leading is most of the space, under a card's title it is half as deep. One value for both makes a card look loose at the size that made a section look right. So space.heading.title-description is the display step and space.heading.title-description-compact is the step at a card's size, and the choice is made by how big the title is rather than by what kind of block it sits in.
+
+Every one of those steps is smaller than the gap below the group, and that ordering is what holds the group together as one thing. space.heading.content is the step between a heading group and the content it introduces, and it is the widest measure inside a section: the one gap the eye reads as a change of subject rather than as a continuation.
+
+That step is the same whether the content is under the heading or beside it. A split is the same relationship turned on its side — a heading group and the content it introduces — so the space between the two halves is space.heading.content, not a gutter. When the split collapses to one column on a phone the gap becomes vertical again, which is where it started, and nothing has to change for that to be right.
+
+space.grid.gutter is between two things of the same kind. Two cards in a row are the same kind; the two halves of a split are not, which is why the gutter is the wrong measure there even when the number would have looked acceptable. The gutter runs on both axes, so a grid reads as an even field rather than as rows with a seam down them.
+
+space.inset.card is the card's, not the page's. A row of cards padded differently is a row of different cards, and the fill is the only edge they have. A page composing a row does not get to choose it.
+
+Column count is not a breakpoint decision. A row holds as many columns as fit before a column would be narrower than size.grid.column-min, and drops one when they would not. Written as a fixed count that collapses at a breakpoint, a four-up row keeps four columns at every width above the phone and sets its copy two or three words to a line through the whole of the tablet range — and on a narrow desktop, which no breakpoint sits on at all. The threshold is a property of the row rather than of a card: a card fills whatever cell it is given.
+
+What this does not cover is the space above and below a section, which is space.section.default and space.section.compact, and the page's own side margin, which is space.inset.page. Those are the section's outside; everything here is its inside.
+  Guidance only — cannot be checked automatically.
+- **A section's title is centred over stacked content, starts beside content in columns, and starts on a phone** — Two arrangements, and the title's alignment is decided by which one it is introducing rather than chosen per section.
+
+Content stacked under the title — a row of cards, an accordion, a set of steps — takes a centred title. The heading group and the block below it share one axis, so a centred title is symmetric with the thing it names, and the eye drops from the middle of the words to the middle of the set. A title starting at the left over a centred or full-width block reads as belonging to the first column rather than to all of them.
+
+Content beside the title — a split, a picture in the other half, anything laid out in columns — takes a title that starts where its content starts. The two share a left edge, and that edge is what says they are one thing read across rather than two stacked. Centring the title there breaks the only alignment the reader has to hold the halves together, and it drifts further from its content the wider the page gets.
+
+The heading group is what carries this, not the heading alone. An eyebrow, a title and a description are read as one block and align together; aligning the title without them leaves a centred heading over start-aligned copy, which reads as a mistake rather than as a choice.
+
+Centred means all of it, not just the words. A badge, a row of actions, a picture — these are flex children, and a flex child is placed by align-items rather than by text-align, so a block that only sets the text leaves everything that is not text at the start. A hero is the case that shows it: its title and copy centred while its badge and its buttons did not.
+
+A capped block centres itself as well as its words. A heading group takes size.heading-group.max, and a cap that is not centred leaves the measure at the start of the column with the words centred inside it — composed, and a long way left of the middle it appears to be in.
+
+Both arrangements go to the start on a phone. A centred block reverts below the breakpoint, and the reason is the measure: on a phone the measure is the screen, so a centred title wraps to three or four ragged lines and the eye loses the left edge it was tracking — the same symmetry that reads as composure on a desktop is what makes it hard to scan on a phone. Centring there has to be asked for twice, and a section title is not one of the things that asks: it is centred because there is room for it, and on a phone there is not. Going back to the start means all of it too, and a capped block is the one that hides a leftover: its words go to the start while its measure stays in the middle of the column, which reads as a title still centred over a badge and buttons that are not — the box in the middle and the line inside it at the edge.
+
+A hero is a section like any other: its badge, title, copy and actions are one stacked block, so it is centred on a desktop and starts on a phone with everything else.
+
+What this is not about is a page whose body is a form or a document. A title over a sign-up form or a guide is not introducing a set of content — it is the first line of the thing itself, and it keeps the alignment the body has, which for running text is the start. The distinction is whether the block below is content the title names or content the title is part of.
+  Guidance only — cannot be checked automatically.
+- **Anything a pointer has to hit is at least 24px in both directions** — A control sized by its contents is as big as its contents, and a glyph is chosen for how it reads rather than for how easily it is hit. An icon-only button with no padding is a 16px target — smaller than the pad of a finger, and smaller than the tremor of a hand using a mouse.
+
+WCAG 2.2 asks for 24 by 24 CSS pixels at AA. The exceptions are narrower than they look: inline targets inside a sentence are exempt, and so is a small target with 24px of clear space around it — but a clear button sits against the field it empties, and a field is itself a target, so the spacing exemption does not apply to the case that keeps arising.
+
+The target and the mark are separate decisions, and conflating them is what produces both faults. Growing the glyph to 24px makes it shout; leaving the button at 16px makes it hard to hit. So the glyph keeps the size that reads correctly beside its text, and the box around it declares a minimum of its own — which is what size.target.min is for.
+
+Declared rather than emergent. Padding plus contents does clear 24px in several components today, and it is the weaker statement: it is a size nobody wrote down, so it moves when the type scale or the glyph does, and nothing says it was meant to be a target at all.
+  Guidance only — cannot be checked automatically.
+
+## Anti-examples
+
+❌ TextInput for: The value is more than a line — a message, a description, an enquiry
+   Nothing here does this yet. A single-line field holding a paragraph shows the reader a sliver of what they wrote and no way to read it back, which on a contact form is the one place they most want to check themselves before sending.
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ TextInput for: The reader is choosing from a set rather than typing
+   Nothing here does this either, and typing where a choice was meant is worse than it looks: free text has to be parsed, corrected and matched, and every mismatch is a submission the page silently loses.
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ TextInput for: The field is a query against something on the page
+   A search is its own component, not a text field with a magnifier in it — it owns a submit gesture and what happens on empty. The clear button is here now; those two are not, and a field pressed into the job is still missing them.
+   → nothing in this system does this. Not a gap waiting to be filled — the case belongs outside it.
+
+❌ status=error + statusMessage missing or empty
+   A field turned red with nothing saying why is a reader stuck at a form with no way forward — and on a marketing page, a reader who leaves
+
+❌ status=warning + statusMessage missing or empty
+   A warning with nothing saying what to look at is a field the reader cannot act on
+
+❌ required=true + optional=true
+   A field is one or the other, and marking it both says nothing
+
+❌ clearable=true + clearLabel missing or empty
+   A button whose only content is a glyph is announced as nothing without a name
+
+## Example
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+
+<TextInput label="Work email" type="email" placeholder="name@example.com" helperText="We'll only email you about the launch." />
+```
+
+```tsx
+import { useState } from 'react'
+import { TextInput } from '@deriv-com/dds-marketing'
+
+// Controlled: TextInput reports the DOM event, so the value is read off it.
+// Unlike AmountInput and SearchInput, which declare an onChange that hands back the
+// value itself — the two shapes look the same at the call site and are not.
+const [value, setValue] = useState('')
+<TextInput label="Work email" type="email" placeholder="name@example.com" helperText="We'll only email you about the launch." value={value} onChange={(event) => setValue(event.target.value)} />
+```
+
+## In use
+
+### Three sizes, three jobs
+
+The small one suits a dense desktop row. The default sits in a section's form. The large one is for a hero or conversion band, where the field is the reason the section exists.
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+
+// sm — a field in a filter row, beside the copy
+<TextInput size="sm" label="Work email" type="email" placeholder="name@example.com" />
+
+// md — an inline signup in a section
+<TextInput size="md" label="Work email" type="email" placeholder="name@example.com" />
+
+// lg — the one field a hero asks for
+<TextInput size="lg" label="Work email" type="email" placeholder="name@example.com" />
+```
+
+### What a failure owes the reader
+
+The field is already red, so the message says what to change rather than that something is wrong. An error with nothing under it is a reader stuck at a form.
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+
+// The standing helper, before anything goes wrong
+<TextInput label="Work email" type="email" placeholder="name@example.com" helperText="We'll only email you about the launch." />
+
+// The message replaces it, and says what to do
+<TextInput label="Work email" type="email" status="error" statusMessage="Enter an address like name@example.com" />
+```
+
+### Asking for less, and marking it
+
+A marketing form is judged on how little it asks. Where a field cannot be skipped the mark says so before the reader reaches the button.
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+
+// Required — the mark sits beside the label
+<TextInput label="Full name" required placeholder="Amara Okafor" />
+
+// Optional, and unmarked — most fields here
+<TextInput label="Company" placeholder="Where you work" />
+```
+
+### Type picks the keypad, not the rules
+
+All four look identical here, and that is the point: the difference is the keypad a phone raises and the hint the browser gives. None of them validates anything.
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+
+// text — a name, with no keypad of its own
+<TextInput label="Full name" type="text" placeholder="Amara Okafor" />
+
+// email — brings the @ without a modifier
+<TextInput label="Work email" type="email" placeholder="name@example.com" />
+
+// tel — the numeric keypad, and no validation
+<TextInput label="Phone" type="tel" placeholder="+44 20 7946 0000" />
+
+// url — for a form that asks for a website
+<TextInput label="Website" type="url" placeholder="https://example.com" />
+```
+
+### The four verdicts a check can return
+
+None of these is a resting state. Each carries a message, because the colour is the part a colour-blind reader may miss and the shape beside it is the part that survives.
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+
+// error — the value has to change
+<TextInput label="Work email" type="email" placeholder="name@example.com" status="error" statusMessage="Enter an address like name@example.com" />
+
+// warning — usable, worth a second look
+<TextInput label="Work email" type="email" placeholder="name@example.com" status="warning" statusMessage="That looks like a personal address. A work one reaches you faster." />
+
+// success — a check ran and passed
+<TextInput label="Work email" type="email" placeholder="name@example.com" status="success" statusMessage="We can reach you here." />
+
+// pending — no spinner; the words are all
+<TextInput label="Work email" type="email" placeholder="name@example.com" status="pending" statusMessage="Checking that address…" />
+```
+
+### What can sit inside the box
+
+Ornaments and furniture, none of which is the label. A glyph names nothing and an affix is never submitted — the words above the field still say what it is for.
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+import { EnvelopeRegularIcon, LockRegularIcon } from '@deriv-com/quill-icons-web'
+
+// prefix — a head you should not have to type
+<TextInput label="Website" type="url" prefix="https://" placeholder="example.com" />
+
+// suffix — a tail every value here shares
+<TextInput label="Work email" type="text" suffix="@example.com" placeholder="amara" />
+
+// clearable — appears once there is a value
+<TextInput label="Work email" type="email" placeholder="name@example.com" clearable clearLabel="Clear work email" defaultValue="amara@example.com" />
+
+// leadingIcon and trailingIcon — ornaments, not controls
+<TextInput label="Work email" type="email" placeholder="name@example.com" leadingIcon={<EnvelopeRegularIcon />} trailingIcon={<LockRegularIcon />} />
+```
+
+### Marking what a form expects
+
+Mark the exception, not the rule. A form where every field carries a mark has said the same as one where none does, and spent a word on each to say it.
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+
+// requiredMark text — the default, needs no key
+<TextInput label="Full name" required requiredMark="text" placeholder="Amara Okafor" />
+
+// requiredMark asterisk — for a dense form
+<TextInput label="Full name" required requiredMark="asterisk" placeholder="Amara Okafor" />
+
+// optional — the one field that may be skipped
+<TextInput label="Company" optional placeholder="Where you work" />
+
+// labelTooltip — reachable by keyboard, not only pointer
+<TextInput label="Work email" type="email" placeholder="name@example.com" labelTooltip="We use this to send the launch note and nothing else." />
+```
+
+### inputMode picks the keypad
+
+A hint to a phone about which keys to raise. Not validation and not type: the value is still text, and what makes it acceptable is still checked after the reader submits.
+
+```tsx
+import { TextInput } from '@deriv-com/dds-marketing'
+
+// numeric — digits and nothing else
+<TextInput label="Postcode" inputMode="numeric" placeholder="90210" />
+
+// decimal — identical here; a phone differs
+<TextInput label="Budget" inputMode="decimal" placeholder="1500.00" />
+```