Missing Form Labels: Accessibility Requirements

What This Violation Means

Form labels are text descriptions that identify what information belongs in each form field (like 'Email Address', 'Phone Number', or 'Credit Card Number'). For accessibility, these labels must be programmatically associated with their form inputs using the <label> element and matching for/id attributes. This allows screen readers to announce the label when users focus on the input field, and it makes labels clickable to focus the associated input.

Why Demand Letters Cite This Violation

Real-World Example from Actual Demand Letters

What the Law Says

Code Examples: Incorrect vs. Correct

<input type="text" placeholder="Email">
(Placeholder is NOT a label - disappears when user types)

<div>First Name</div>
<input type="text">
(Visual label not programmatically associated)

<input type="text" name="email">
(No label at all - screen reader says "edit text")

<input type="checkbox" id="terms">
I agree to terms
(Text exists but not in <label>, can't click to check box)

<label for="email">Email Address</label>
<input type="text" id="email" name="email">
(Properly associated - clicking label focuses input)

<label>
  First Name
  <input type="text" name="fname">
</label>
(Label wraps input - also valid association)

<input type="text" aria-label="Search query" name="q">
(For cases where visible label isn't desired)

<label for="terms">
  <input type="checkbox" id="terms">
  I agree to the terms and conditions
</label>
(Clickable label for checkbox)

How to Fix This Violation

DIY Approach

Professional Remediation

We audit all forms using both automated tools and manual screen reader testing. We identify missing labels, improperly associated labels, and ambiguous labels. For complex forms, we implement proper fieldset/legend grouping for radio buttons and checkboxes, add helpful instructions using aria-describedby, and ensure error messages are associated with their fields. For multi-step forms, we implement proper focus management and progress indicators that work with screen readers. Most forms take 30-90 minutes to remediate properly, depending on complexity. We test with NVDA, JAWS, and VoiceOver to ensure cross-platform compatibility.

Cost to Fix

Our Experience Fixing This Violation