UX Patterns Guide
Back to compare picker

Email address entry vs Text input vs Inline validation vs Error summary

Prefer email address entry when the value will be used to send receipts, notifications, account recovery links, sign-in identifiers, invitations, or verification messages.

Email address entry live exampleText input live exampleInline validation live exampleError summary live example

Decision dimensions

Dimension Email address entryText inputInline validationError summary
UI or UX UI + UX - Contactable email address capture fieldUI + UX - Single-line freeform data-entry controlUI + UX - Field-level validation feedbackUI + UX - Form recovery summary
UI guidance Render email entry as a labelled single-line field with purpose text, type email, autocomplete email, spellcheck disabled, enough visible width for review, field-specific errors, and optional typo warning and review states.Render a persistent label, appropriately sized single-line input, optional hint, visible focus state, and nearby error text that is programmatically associated with the field.Render a labeled field with hint text, field-adjacent error text, invalid styling, preserved value, and corrected state.Render a top-of-form summary block with heading, linked error list, and matching field-level error messages.
UX guidance Use email address entry when the product must contact the user, identify an account, send a receipt, invite someone, or confirm access to a mailbox.Use text input for short freeform answers that users can type or paste and that cannot be accurately represented as a fixed option choice.Help users correct a specific field without losing or re-entering the value they already typed.Help users recover from one or more submitted-form errors without scanning the entire page.
Good UI A receipt form asks for Email address, says We will only use this to send your receipt, uses type email and autocomplete email, and shows a review row before submit.A reference-name field has a visible label, hint, medium width, focus ring, and error message beneath the hint when submitted empty.Error text appears next to the field with readable spacing, persistent label, hint text, and the invalid value still visible.Top-of-form summary with a clear heading, linked error list, and matching inline field messages.
Bad UI A form uses a plain text field named Contact and later rejects it as not email-shaped after submit.The only instruction is placeholder text that disappears when the user starts typing.Only a red border with no message.Red banner saying fix errors with no links.
Good UX A user pastes alex+receipts@example.co.uk, sees it preserved exactly, reviews it on the check page, and changes it only if needed.A user types or pastes a short reference, submits it, and the interface confirms the stored value without changing their wording.Validation appears after blur or submit when it helps correction.After failed submit, focus or reading order makes the summary discoverable before users scan the form.
Bad UX A user with a long work address cannot see enough of it to spot a typo before the service sends a reset link.Validation fires on the first focus event and blocks typing before the user has had a chance to answer.Showing errors before users type.Only showing errors below the fold.
Best fit The product must capture an email address for contact, receipt, notification, invitation, account identifier, recovery, or verification.The answer is short and user-authored.A single field has a specific correctable problem.Form submission can produce one or more errors.
Avoid when The value is a username, label, reference, organization name, or other short text that may not be an email address.The answer is a paragraph, comment, address block, or explanation requiring multiple lines.The main recovery task is finding several errors across a submitted page.A single local field issue can be corrected before submit without page-level orientation.
Required state Initial state with label, purpose hint, type email, autocomplete email, spellcheck false, and adequate width.Empty untouched state with persistent label and optional hint.Neutral field with label, hint, and no error.Neutral form before submit with no summary.
Accessibility burden Use a visible label that names the value as an email address and a hint that explains why it is requested.Associate every text input with a visible label or equivalent accessible name that matches the visible question.Expose invalid state on the input and connect error text to the field description where possible.Use a heading and alert behavior that makes the summary discoverable.
Common misuse Using a plain text input without email autocomplete or email keyboard support.Using placeholder text as the only label or instruction.Showing field errors before users have interacted with the control.Showing a red banner or toast with no links to the invalid answers.

Email address entry

UI or UX
UI + UX - Contactable email address capture field
UI guidance
Render email entry as a labelled single-line field with purpose text, type email, autocomplete email, spellcheck disabled, enough visible width for review, field-specific errors, and optional typo warning and review states.
UX guidance
Use email address entry when the product must contact the user, identify an account, send a receipt, invite someone, or confirm access to a mailbox.
Good UI
A receipt form asks for Email address, says We will only use this to send your receipt, uses type email and autocomplete email, and shows a review row before submit.
Bad UI
A form uses a plain text field named Contact and later rejects it as not email-shaped after submit.
Good UX
A user pastes alex+receipts@example.co.uk, sees it preserved exactly, reviews it on the check page, and changes it only if needed.
Bad UX
A user with a long work address cannot see enough of it to spot a typo before the service sends a reset link.
Best fit
The product must capture an email address for contact, receipt, notification, invitation, account identifier, recovery, or verification.
Avoid when
The value is a username, label, reference, organization name, or other short text that may not be an email address.
Required state
Initial state with label, purpose hint, type email, autocomplete email, spellcheck false, and adequate width.
Accessibility burden
Use a visible label that names the value as an email address and a hint that explains why it is requested.
Common misuse
Using a plain text input without email autocomplete or email keyboard support.

Text input

UI or UX
UI + UX - Single-line freeform data-entry control
UI guidance
Render a persistent label, appropriately sized single-line input, optional hint, visible focus state, and nearby error text that is programmatically associated with the field.
UX guidance
Use text input for short freeform answers that users can type or paste and that cannot be accurately represented as a fixed option choice.
Good UI
A reference-name field has a visible label, hint, medium width, focus ring, and error message beneath the hint when submitted empty.
Bad UI
The only instruction is placeholder text that disappears when the user starts typing.
Good UX
A user types or pastes a short reference, submits it, and the interface confirms the stored value without changing their wording.
Bad UX
Validation fires on the first focus event and blocks typing before the user has had a chance to answer.
Best fit
The answer is short and user-authored.
Avoid when
The answer is a paragraph, comment, address block, or explanation requiring multiple lines.
Required state
Empty untouched state with persistent label and optional hint.
Accessibility burden
Associate every text input with a visible label or equivalent accessible name that matches the visible question.
Common misuse
Using placeholder text as the only label or instruction.

Inline validation

UI or UX
UI + UX - Field-level validation feedback
UI guidance
Render a labeled field with hint text, field-adjacent error text, invalid styling, preserved value, and corrected state.
UX guidance
Help users correct a specific field without losing or re-entering the value they already typed.
Good UI
Error text appears next to the field with readable spacing, persistent label, hint text, and the invalid value still visible.
Bad UI
Only a red border with no message.
Good UX
Validation appears after blur or submit when it helps correction.
Bad UX
Showing errors before users type.
Best fit
A single field has a specific correctable problem.
Avoid when
The main recovery task is finding several errors across a submitted page.
Required state
Neutral field with label, hint, and no error.
Accessibility burden
Expose invalid state on the input and connect error text to the field description where possible.
Common misuse
Showing field errors before users have interacted with the control.

Error summary

UI or UX
UI + UX - Form recovery summary
UI guidance
Render a top-of-form summary block with heading, linked error list, and matching field-level error messages.
UX guidance
Help users recover from one or more submitted-form errors without scanning the entire page.
Good UI
Top-of-form summary with a clear heading, linked error list, and matching inline field messages.
Bad UI
Red banner saying fix errors with no links.
Good UX
After failed submit, focus or reading order makes the summary discoverable before users scan the form.
Bad UX
Only showing errors below the fold.
Best fit
Form submission can produce one or more errors.
Avoid when
A single local field issue can be corrected before submit without page-level orientation.
Required state
Neutral form before submit with no summary.
Accessibility burden
Use a heading and alert behavior that makes the summary discoverable.
Common misuse
Showing a red banner or toast with no links to the invalid answers.
Decision rules
  • Prefer email address entry when the value will be used to send receipts, notifications, account recovery links, sign-in identifiers, invitations, or verification messages.
  • Prefer text input when the value is an ordinary label, username, reference, organization name, or note that should not be parsed, autofilled, or validated as an email address.
  • Prefer inline validation inside email address entry for missing value, malformed address, repeated whitespace, unsupported multiple-address entry, provider typo warning, or unreachable confirmation state tied to this one field.
  • Prefer error summary when a submitted account, checkout, or contact form has several errors and users need a top-of-form list that links back to the email field.
  • Use type email, autocomplete email, spellcheck false, visible label, and enough width for users to review most addresses, while still validating on the server.
  • Allow paste and browser autofill; do not split the local part and domain into separate fields or block plus tags, subdomains, long addresses, or uncommon domains merely because they look unfamiliar.
  • Warn on likely provider typos such as homtail.com or gmial.com, but let users keep the value because uncommon domains can be genuine.
  • Confirm the entered address back to users on a review page or local summary when email is used for receipts, notifications, recovery, or account access.
  • Use an email confirmation loop only when access to that mailbox is essential, such as account activation or password reset; avoid it for low-consequence contact fields.
  • Do not ask users to repeat the email address unless research for this service shows it reduces errors; review and change usually create less friction.
Inspect live examples
Email address entryText inputInline validationError summary
Failure modes
  • A form uses a plain text input and mobile users do not get the email keyboard or email autofill.
  • The field blocks paste or plus-addressing, so users cannot use their real address or password-manager-stored identity.
  • A regex rejects a valid long or uncommon domain address that the service could have delivered to.
  • The form silently corrects gmial.com to gmail.com and sends sensitive mail to the wrong address.
  • A product requires email confirmation for a low-risk receipt and causes avoidable abandonment.
  • A top-of-page error says invalid value without linking back to the email field or preserving the typed address.