Text associated with an input that communicates its purpose. Implement with <label for> or ARIA labelling.
Form labels are the most fundamental accessibility feature for form fields, yet they're consistently overlooked or implemented incorrectly. A proper label creates a clear, programmatic relationship between a form field and its description, allowing screen readers to announce what information is expected and helping all users understand the purpose of each field.
The relationship between labels and form fields is so important that it's a Level A WCAG requirement – the most basic level of accessibility compliance. Without proper labels, form fields become mysterious boxes that users must guess the purpose of, creating barriers for everyone but especially for users with cognitive disabilities or those using assistive technology.
Good labels are more than just visible text – they're semantic relationships that make forms understandable and usable for all users.
Explicit Labels (Preferred): ```html ```
Implicit Labels (Also Valid): ```html ```
ARIA Labels (When HTML Labels Aren't Possible): ```html ```
Complex Labels with ARIA: ```html
Labels with Additional Context: ```html
Placeholder as Label: Using placeholder text as the only way to identify form fields. Placeholder text disappears when users start typing and isn't accessible to screen readers.
Missing Labels: Form fields with no labels at all, leaving users to guess what information is expected.
Incorrect Label Association: Labels that don't properly reference their form fields, breaking the semantic relationship.
Visual-Only Labels: Labels that are only visible but not programmatically associated with form fields.
Redundant or Confusing Labels: Labels that don't clearly describe what information is expected or that provide conflicting information.
Labels for Decorative Elements: Adding labels to form fields that are purely decorative or not meant for user input.
Error Messages as Labels: When form fields have errors, the error message should be associated with the field using aria-describedby:
```html
Required Field Indicators: Required fields should be clearly marked:
```html ```
Field Groups: Related form fields should be grouped with fieldset and legend:
```html
```WebAbility automatically manages form labels and error associations, ensuring that all form fields are properly labeled and accessible to assistive technology users.
Join over 1 million websites using WebAbility to ensure digital accessibility compliance and provide equal access to all users.
Form label associated to inputs via label for/id, aria-label, or aria-labelledby so assistive technologies announce purpose.
ARIA role for dual-state controls. Support keyboard activation and clear checked/unchecked indication.
Input widget combining text field with popup list. Requires complex ARIA states and keyboard navigation patterns.
ARIA landmark role for form regions. Use when form lacks a native form element or needs additional identification.
ARIA role for selectable items within listbox, combobox, or similar selection widgets.
This glossary is continuously improved and maintained by WebAbility to advance accessible design and development.Contact us to suggest improvements or report issues.