Textareas — Accessibility Specification

WCAG 2.1 AA • AODA compliant • Updated 2025-10-04


What is this component?

What is this component? A textarea (<textarea>) captures multi‑line text. It exposes native semantics, keyboard behavior, and value.

Where used? Comments, descriptions, messages, addresses—any long‑form user input.

Accessibility Requirements

RequirementWCAG CriteriaDescription
Programmatic label1.3.1, 3.3.2Associate with <label for>/id or aria-labelledby.
Helpful instructions3.3.2Use aria-describedby for hints like character limits.
Error identification3.3.1, 3.3.3Show and announce errors; provide suggestions.
Keyboard2.1.1Reachable by Tab; Enter inserts newline; no traps.
Name, Role, Value4.1.2Exposes role “textbox (multiline)”, accessible name, and current value.

ARIA Roles and Attributes

ARIA Role/AttributeUsed OnPurpose & Usage
<textarea>Native multilinePreferred control with built‑in semantics.
aria-describedbyTextarea with hints/errorsAssociates guidance and validation messages.
aria-invalid="true"Invalid inputSet on validation failure.

Implementation Guidelines




Max 500 characters. Be specific and concise.

DO’s

Don’ts

Common Pitfalls

Testing Checklist

Test ItemWCAG CriteriaPass Criteria
Label/Hints announced1.3.1, 3.3.2Screen reader announces label and hint text.
Error handling3.3.1, 3.3.3Error is visible and announced; suggestions provided.
Keyboard operability2.1.1Reachable, editable; no traps.