Skip to content

shadcn.io is an independent project built on shadcn/ui

Textarea with Helper Text for Solid

A textarea labeled Bio, with helper text under it that says the text is displayed on your public profile.

UI library: Ark UI

The label Bio sits above the textarea. The placeholder is Tell us about yourself. Under the field, the helper reads This will be displayed on your public profile.

Use it when the label does not say where the text goes or who will read it. An instruction people need first belongs between the label and the field. One line belongs in an Input. In Solid, Ark UI does not write the helper.

Preview

Preview width

Installation

MCP · Pro
Make your AI a shadcn expert
Your agent installs components, builds pages and restyles your app from one prompt, in Claude Code, Cursor or VS Code.
Part of Pro

Anatomy

Textarea anatomy: textarea, caret, placeholder, resize handle

Usage

<Field class="max-w-md">
    <FieldLabel>Bio</FieldLabel>
    <Textarea class="bg-background" placeholder="Tell us about yourself" />
    <FieldDescription>
      This will be displayed on your public profile.
    </FieldDescription>
  </Field>

FAQ

When should I add helper text to textarea fields?

When the label doesn't settle the question people will have: where the text appears, who reads it, what to include. Skip it for self-evident fields such as Message or Comment.

Should helper text go above or below the textarea?

Below, as here, for short context people can read after the field. Put it between the label and the field, as the Textarea with Description example does, when it's an instruction people need before they start typing.

Why use text-muted-foreground for helper text?

FieldDescription sets the muted color and a smaller size, so the helper reads as secondary to the label and the field. The token keeps enough contrast in both themes.

How long should helper text be?

One sentence, like the one here. Longer guidance belongs on a help page linked from the description.

Can helper text change based on user input?

Yes, it renders whatever you give it: a count, a hint that updates as people type. When the text describes an error, show a FieldError and mark the Field invalid instead, so the error is styled and announced as one.

How do I make helper text accessible for screen readers?

Give the FieldDescription an id and set the Textarea's aria-describedby to it, so screen readers read the helper when the field gets focus, after its label. Or use FieldHelper in its place: the Field links it to the Textarea for you.

API Reference

Field

No extra props in this demo. The rest is on the Field page.

Textarea

Sets placeholder="Tell us about yourself". The rest is on the Textarea page.