WCAG 4.1.2 · Level A

Form elements must have labels

Some form fields have no label, so screen reader users don't know what to enter.

What this rule checks

Ensure every form element has a label.

Why it matters

WCAG 1.3.1, 3.3.2 and 4.1.2 require form fields to have labels. Newsletter sign-up and search fields are common offenders.

How to fix it

  1. Give each field a <label for="field-id"> element, or at minimum an aria-label.
  2. Placeholder text alone does not count as a label.

How to check the fix

  • Re-scan and confirm the label rule no longer fails.
  • Click each label and check it focuses its field.

How FixReports finds it

Our scan runs the axe-core rule label in a real Chrome browser on every page it tests, and reports each failing element with its page, its markup and, where it applies, a screenshot.

An automated test confirms that this specific problem is present. It can't tell whether the rest of the page is accessible: some barriers only show up when a person checks the page.

Scan your website today

Find it. Fix it. Verify it.

What kind of website is this?

Your answer picks the right checks, like the shopping journey for online stores. We still check the site's own evidence and show both.

What kind of website is this?

Free scan. No credit card required.