Search field
Search field is a Inputs block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Narrowing a list you are already looking at
Anatomy
Magnifier in the lead · a clear once there is something to clear · Filter in its own divided segment with a count · the people under it, narrowing as you type with the match in bold, a count in the footer and a highlight that slides
- Priya Ramanpriya@orvain.devDesign
- Tom Okafortom@orvain.devEngineering
- Sofia Almeidasofia@orvain.devInvited
- Daniel Weissdaniel@orvain.devEngineering
- Mei Linmei@orvain.devSales
- Jonas Bergjonas@orvain.devInvited
In the Orvain Library
Get Search field for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Inputs
What’s inside
04parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- Magnifier in the lead
- A clear once there is something to clear
- Filter in its own divided segmentwith a count
- The people under itnarrowing as you type with the match in bold, a count in the footer and a highlight that slides
Responsive behaviour
420 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Inputs earns its place
Reach for Inputs
- Any short value on one line: a name, an email, an amount, a search term
- A value with a fixed prefix or unit the person picks instead of typing
- Password creation, where the rules must stay visible while they are being broken
- A generated value the person only needs to copy out
Reach for something else
- More than a line or two of prose: a text area that grows lets people see what they wrote
- A value from a known list: a select or combobox, since free text people must spell exactly is a validation problem you created
- A date or a time: a picker that understands months beats a field that has to parse them
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Search field” block to this page: magnifier in the lead, a clear once there is something to clear, Filter in its own divided segment with a count, the people under it, narrowing as you type with the match in bold, a count in the footer and a highlight that slides.
Questions about Search field.
What is the Search field block?
Search field is a Inputs block from Orvain UI, built for React and Vue with a matching Figma frame. Best for narrowing a list you are already looking at.
What is the Search field block made of?
4 parts: magnifier in the lead; a clear once there is something to clear; filter in its own divided segment with a count; and the people under it, narrowing as you type with the match in bold, a count in the footer and a highlight that slides. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Search field block responsive?
Yes. It is drawn at 420px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Search field block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Search field block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Search field block to this page.”
When should I not use a Inputs block?
More than a line or two of prose: a text area that grows lets people see what they wrote.
More Inputs blocks
All InputsPremium components,
free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Orvain MCPSearch field
Search field is a Inputs block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Narrowing a list you are already looking at
Anatomy
Magnifier in the lead · a clear once there is something to clear · Filter in its own divided segment with a count · the people under it, narrowing as you type with the match in bold, a count in the footer and a highlight that slides
- Priya Ramanpriya@orvain.devDesign
- Tom Okafortom@orvain.devEngineering
- Sofia Almeidasofia@orvain.devInvited
- Daniel Weissdaniel@orvain.devEngineering
- Mei Linmei@orvain.devSales
- Jonas Bergjonas@orvain.devInvited
In the Orvain Library
Get Search field for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Inputs
What’s inside
04parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- Magnifier in the lead
- A clear once there is something to clear
- Filter in its own divided segmentwith a count
- The people under itnarrowing as you type with the match in bold, a count in the footer and a highlight that slides
Responsive behaviour
420 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Inputs earns its place
Reach for Inputs
- Any short value on one line: a name, an email, an amount, a search term
- A value with a fixed prefix or unit the person picks instead of typing
- Password creation, where the rules must stay visible while they are being broken
- A generated value the person only needs to copy out
Reach for something else
- More than a line or two of prose: a text area that grows lets people see what they wrote
- A value from a known list: a select or combobox, since free text people must spell exactly is a validation problem you created
- A date or a time: a picker that understands months beats a field that has to parse them
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Search field” block to this page: magnifier in the lead, a clear once there is something to clear, Filter in its own divided segment with a count, the people under it, narrowing as you type with the match in bold, a count in the footer and a highlight that slides.
Questions about Search field.
What is the Search field block?
Search field is a Inputs block from Orvain UI, built for React and Vue with a matching Figma frame. Best for narrowing a list you are already looking at.
What is the Search field block made of?
4 parts: magnifier in the lead; a clear once there is something to clear; filter in its own divided segment with a count; and the people under it, narrowing as you type with the match in bold, a count in the footer and a highlight that slides. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Search field block responsive?
Yes. It is drawn at 420px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Search field block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Search field block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Search field block to this page.”
When should I not use a Inputs block?
More than a line or two of prose: a text area that grows lets people see what they wrote.
More Inputs blocks
All InputsPremium components, free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
