## Anatomy
The Textarea consists of four primary elements that work together to allow users to type multiple lines of text.
1. Label
2. Help text
3. Field
4. Resize element
## Options
Textarea supports label, description text, counter, required, placeholder, and user resizing configurations to accommodate various multi-line text input scenarios.
### Label
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
A Textarea should almost always have a label, as it provides essential information about what to do with the Textarea.
### Description text
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
Description text provides information to help the user avoid errors.
### Counter
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
A counter can be displayed if there is a max length.
### Required
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
A visual indicator applied to the label.
### Placeholder text
While generally not recommended to use, the Textarea can utilize placeholder text if needed. Don't use placeholder as a replacement for the label.
### User resizing
```tsx lines expandable theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
By default, a user can resize the Textarea in any direction, as is the standard for normal Textareas. This can also be turned off if there are problems with allowing a user to resize, such as in a tight layout.
## Behavior
Textarea responds to user interaction with distinct visual states, height control, and overflow handling.
### Visual States
#### Default
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
#### Disabled
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
#### Readonly
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
Readonly prevents edits to the Textarea, but still allows a user to copy text and focus the element, unlike with disabled styling.
#### Error
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return (
);
}
export default App;
```
The error message provided would replace any help text that might exist below the label.
### Height (Rows)
```tsx lines theme={null}
import { Textarea, Flex } from "@servicetitan/anvil2";
function App() {
return (
);
}
export default App;
```
The height of the Textarea is controlled by the rows property native to the Textarea, and is by default 3 rows tall. See Overflow handling for additional row options.
### Overflow
The Textarea overflows like a typical html textarea. When the rows of text exceed the Textarea's height or row count, it will scroll.
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return (
);
}
export default App;
```
A Textarea with 3 rows and no additional properties. A scrollbar appears with 4 or more row items.
## Usage Guidelines
Use the Textarea when a user needs to add a longer, freeform amount of text, typically spanning over multiple lines. They are usually used as part of a [Form](/docs/web/patterns/forms).
## Content
Content within Textarea should clearly communicate the expected input through labels and descriptions.
Most of the content guidelines from [Forms](/docs/web/patterns/forms) applies to Textareas.
#### Use a label for all Textareas
A label is a short, meaningful description that clearly indicates what the user is expected to enter. Labels should be 1 to 3 words and written in title case. Labels should primarily be nouns. Avoid using labels as CTAs. A label is not inline help and shouldn't be used to provide instruction.
#### Avoid using placeholder text
Placeholder text has several accessibility issues:
* Text has low contrast which makes the text hard to read
* Text disappears as soon as the user starts typing
* Can't accommodate additional context due to limited space
* Unreliable for screen readers
* Use inline help to provide hints, formatting, and requirements
#### Show descriptions, formatting, and requirements
Description text should explain a feature or the outcome of the actions the user is about to take.
The description should adapt to the situation and context. The guidance could be focused on what is needed, or it could describe how to enter it.
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return (
);
}
export default App;
```
**Do**
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return ;
}
export default App;
```
**Don't**
### Keep more info short, simple, and scannable
More info should be short and easily scannable, no longer than a single phrase or short sentence.
Avoid repeating the UI text. Use sentence case, and only include period if more than one sentence is used.
For more complex or important information, consider another method of presentation, e.g., description or a link to the knowledge base.
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return (
);
}
export default App;
```
**Do**
```tsx lines theme={null}
import { Textarea } from "@servicetitan/anvil2";
function App() {
return (
);
}
export default App;
```
**Don't**
## Keyboard Interaction
Users can navigate Textarea using standard keyboard controls.
| Key | Interaction |
| --- | -------------------- |
| Tab | Focuses the Textarea |
### Accessibility
* Placeholder text is not a substitute for a label.
* When the label is not directly used for whatever reason, an annotated label should still be provided.
* If the label exists, but is an element separate from the Textarea, these should be linked through aria-labelledby. [Refer to W3C's on how to implement this](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA7).
* If no label exists at all on the page, provide an annotated text label, which would utilize an aria-label. [Refer to W3C's on how to implement this](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA8).
For more guidance on form field labels and context, see [input field context association best practices](/docs/accessibility/labels-and-ctas#input-field-context-association).
