<textarea> Element

Technical Summary

Meaning, categories, and content model

Unlike a rich-text editor, a native textarea represents plain text. A visual line wrap and a newline inserted into the value submitted by a form are not necessarily the same thing.

Initial value, raw value, and current value

The element's contents represent its default value. When a user edits the control, its raw value changes, and the current API value is exposed through textarea.value. There is no value content attribute for setting a textarea's initial value in the way that input uses one.

<textarea id="note" name="note" rows="3">The initial value</textarea>

<script>
  const note = document.querySelector('#note');
  note.value;        // current value
  note.defaultValue; // reset baseline
</script>

User editing sets the dirty value flag. After that flag is set, changing the DOM child text does not necessarily update the current value in the same way. A form reset clears the flag and sets the raw value from the child text.

Mutability, readonly, and disabled

A textarea is mutable when it is neither disabled nor readonly. A mutable control lets the user edit its raw value, including inserting and removing LF line breaks.

readonly and disabled are not interchangeable presentation flags. Check editing, validation participation, and submission eligibility separately.

Important content attributes

Newline normalization and wrap

A textarea value has three relevant views. The raw value is not normalized. The API value normalizes line breaks to LF (U+000A). The form-submission value starts from the API value and can receive wrapping newlines under wrap="hard".

Wrap state	Visual wrapping	Submitted value
soft (default)	The rendering may wrap lines visually	Visual wrapping alone does not add submitted newlines
hard	The rendering may wrap at the cols width	The user agent adds wrapping newlines for submission

Therefore, the number of visual lines and the newline positions in a submitted string cannot be assumed to match. When a server processes line breaks, inspect the received value together with the wrap conditions.

Form submission and constraint validation

textarea is a form-associated submittable element. When it has a form owner, is not disabled, and meets conditions such as having a name, its form value contributes to the form's entry list.

<form action="/messages" method="post">
  <label for="body">Body</label>
  <textarea id="body" name="body" required minlength="10"></textarea>
  <button type="submit">Send</button>
</form>

When required is present, the textarea is mutable, and its value is empty, constraint validation reports a missing value. minlength and maxlength constrain value length, while readonly and disabled affect validation participation. Browser validation is not a substitute for server-side validation.

DOM Interface

The textarea element is exposed through HTMLTextAreaElement.

When user interaction changes the raw value, an input event is fired. Code that handles the event should still distinguish raw value, API value, and the value used for form submission.

Fact / Evidence

The main facts below are paired with their scope, verification state, and normative source. Browser and accessibility-tree observations are kept separate in the Implementation Evidence section.

Evidence

1. HTML Standard: The textarea element — meaning, categories, content model, attributes, values, reset, and DOM interface
2. HTML Standard: Form control infrastructure — form owners, disabled state, constraint validation, and shared submission model
3. HTML Accessibility API Mappings: textarea — textbox role, multiline state, accessible name, and state mappings
4. WPT: textarea element tests — tests related to textarea values, attributes, and form behavior
5. WPT: input events and textarea editing — an example covering editing actions and input events

Implementation Evidence

Browser behavior, WPT results, and accessibility observations are recorded separately from normative claims. Unrun items are not treated as reviewed.

Measured fixture / environment: The fixture contains an initial-value textarea, empty required textarea, minlength and maxlength, readonly, disabled, wrap="hard", an external form owner, and a reset button inside or alongside <form id="evidence-form" method="get">. DOM, ValidityState, and FormData were measured in Chrome 152.0.0.0 (HeadlessChrome / Windows NT 10.0) on 2026-09-13.

Use the WPT repository for test mappings and HTML-AAM for accessibility criteria.

Coverage / Open Issues

• ReviewedTextarea meaning, categories, content model, initial/current/default values, major attributes, and the HTMLTextAreaElement API overview
• ReviewedRequired, minlength, maxlength, readonly, disabled, form owner, and major form-submission boundaries
• ReviewedRaw value, API value, form value, LF normalization, and the basic relationship with wrap
• OpenAll branches of the form-submission algorithm, entry-list construction, dirname, encoding, and formdata event
• OpenThe wrap="hard" wrapping algorithm, newline and Unicode edge cases, and implementation differences in value length
• OpenImplementation evidence, multiple browsers, WPT execution, complete HTML-AAM mapping, assistive-technology observations, compatibility, historical changes, and Expert-gap Review

This is initial coverage. It does not claim that the entire textarea element has been verified, that every browser exposes the same value or presentation, or that assistive technologies produce the same result.

Related surface

For a beginner-friendly explanation of multiline input, labels, initial values, and form submission, see the textarea element page in Yugien. The shared form-submission model is covered by the form element in Atlas; label association by the label element; and boundaries with other form controls by the input, select, and button pages.