Contact form
Contact form is a Forms block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
A marketing or support form that tells people who reads it, when they hear back, and what to fix when something is off
Anatomy
A quiet grey panel with the overline, heading, one line, a three-node “what happens next” rail and the people who answer · 44px fields with the red required mark, a message that grows to ten lines with attachment tiles and a count from 80% · errors after you leave a field you typed in or on Send, with a summary of field chips that tick green and drop out · Send holds its width, shows a spinner and a fill, then the column becomes the confirmation and the rail ticks Received
In the Orvain Library
Get Contact form 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 Forms
What’s inside
04parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- A quiet grey panelwith the overline, heading, one line, a three-node “what happens next” rail and the people who answer
- 44px fieldswith the red required mark, a message that grows to ten lines with attachment tiles and a count from 80%
- Errors after you leave a field you typed in or on Send, with a summary of field chips that tick green and drop out
- Send holds its widthshows a spinner and a fill, then the column becomes the confirmation and the rail ticks Received
Responsive behaviour
832 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 Forms earns its place
Reach for Forms
- A contact or support request short enough to answer in one sitting
- An application long enough that one page would hide its own end, where a later section depends on earlier answers
- Settings a person edits and saves, read out of order by somebody hunting one control
- Any flow where a rejected answer has to be reported without losing the accepted ones
Reach for something else
- One value changes and applies at once: a switch or an inline field that saves itself, with no Submit to press
- There is a single question: a prompt with two buttons, or one field in a dialog, costs far less than a form does
- Steps are being added for their own sake: if nothing in the last section depends on the first, one column and a scroll is faster than Back and Next
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 “Contact form” block to this page: a quiet grey panel with the overline, heading, one line, a three-node “what happens next” rail and the people who answer, 44px fields with the red required mark, a message that grows to ten lines with attachment tiles and a count from 80%, errors after you leave a field you typed in or on Send, with a summary of field chips that tick green and drop out, Send holds its width, shows a spinner and a fill, then the column becomes the confirmation and the rail ticks Received.
Questions about Contact form.
What is the Contact form block?
Contact form is a Forms block from Orvain UI, built for React and Vue with a matching Figma frame. Best for a marketing or support form that tells people who reads it, when they hear back, and what to fix when something is off.
What is the Contact form block made of?
4 parts: a quiet grey panel with the overline, heading, one line, a three-node “what happens next” rail and the people who answer; 44px fields with the red required mark, a message that grows to ten lines with attachment tiles and a count from 80%; errors after you leave a field you typed in or on Send, with a summary of field chips that tick green and drop out; and send holds its width, shows a spinner and a fill, then the column becomes the confirmation and the rail ticks Received. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Contact form block responsive?
Yes. It is drawn at 832px 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 Contact form 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 Contact form 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 Contact form block to this page.”
When should I not use a Forms block?
One value changes and applies at once: a switch or an inline field that saves itself, with no Submit to press.
More Forms blocks
All FormsPremium 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 MCPContact form
Contact form is a Forms block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
A marketing or support form that tells people who reads it, when they hear back, and what to fix when something is off
Anatomy
A quiet grey panel with the overline, heading, one line, a three-node “what happens next” rail and the people who answer · 44px fields with the red required mark, a message that grows to ten lines with attachment tiles and a count from 80% · errors after you leave a field you typed in or on Send, with a summary of field chips that tick green and drop out · Send holds its width, shows a spinner and a fill, then the column becomes the confirmation and the rail ticks Received
In the Orvain Library
Get Contact form 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 Forms
What’s inside
04parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- A quiet grey panelwith the overline, heading, one line, a three-node “what happens next” rail and the people who answer
- 44px fieldswith the red required mark, a message that grows to ten lines with attachment tiles and a count from 80%
- Errors after you leave a field you typed in or on Send, with a summary of field chips that tick green and drop out
- Send holds its widthshows a spinner and a fill, then the column becomes the confirmation and the rail ticks Received
Responsive behaviour
832 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 Forms earns its place
Reach for Forms
- A contact or support request short enough to answer in one sitting
- An application long enough that one page would hide its own end, where a later section depends on earlier answers
- Settings a person edits and saves, read out of order by somebody hunting one control
- Any flow where a rejected answer has to be reported without losing the accepted ones
Reach for something else
- One value changes and applies at once: a switch or an inline field that saves itself, with no Submit to press
- There is a single question: a prompt with two buttons, or one field in a dialog, costs far less than a form does
- Steps are being added for their own sake: if nothing in the last section depends on the first, one column and a scroll is faster than Back and Next
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 “Contact form” block to this page: a quiet grey panel with the overline, heading, one line, a three-node “what happens next” rail and the people who answer, 44px fields with the red required mark, a message that grows to ten lines with attachment tiles and a count from 80%, errors after you leave a field you typed in or on Send, with a summary of field chips that tick green and drop out, Send holds its width, shows a spinner and a fill, then the column becomes the confirmation and the rail ticks Received.
Questions about Contact form.
What is the Contact form block?
Contact form is a Forms block from Orvain UI, built for React and Vue with a matching Figma frame. Best for a marketing or support form that tells people who reads it, when they hear back, and what to fix when something is off.
What is the Contact form block made of?
4 parts: a quiet grey panel with the overline, heading, one line, a three-node “what happens next” rail and the people who answer; 44px fields with the red required mark, a message that grows to ten lines with attachment tiles and a count from 80%; errors after you leave a field you typed in or on Send, with a summary of field chips that tick green and drop out; and send holds its width, shows a spinner and a fill, then the column becomes the confirmation and the rail ticks Received. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Contact form block responsive?
Yes. It is drawn at 832px 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 Contact form 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 Contact form 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 Contact form block to this page.”
When should I not use a Forms block?
One value changes and applies at once: a switch or an inline field that saves itself, with no Submit to press.
More Forms blocks
All FormsPremium 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.
