Free tool · WCAG 1.3.1 / 3.3.2 / 1.3.5

Can every visitor tell what each field wants?

Unlabelled fields, placeholders that vanish while typing, required marks shown only as a red asterisk — these quietly block screen-reader, voice-control and low-vision visitors at the exact moment they try to contact you or pay you. Enter the fields of one form below and this checker runs 8 plain-English checks, then builds a corrected label plan: label wording, required wording and the right autocomplete token for each field.

Runs entirely in your browser. The fields you enter are never uploaded, stored or tracked. This checker reviews the label plan you describe — it cannot crawl your site, read your code or submit your form.

Try an example:
—

Describe your fields and the score updates as you type. 90–100 is a label plan that works for assistive technology, 60–89 needs a fix listed below, under 60 means the form is guessing-game for real visitors.

Corrected label plan

—

One line per field: the label wording to show, the word required where the field is required, and the autocomplete token to set in code. Your field order is never changed.

How to read the result

The rule is simple: every field keeps a visible name that never disappears, says whether it is required in words, and — when it asks for the visitor's own data — carries the autocomplete token that lets their tools fill it in. Our ADA website compliance checklist puts form labels in context with the other first-line checks, and the Heading Structure Checker covers the outline visitors navigate by.

The label mistakes that fail most often

  • Placeholder as the only label. It disappears the moment typing starts — the visitor cannot re-check what the field wanted.
  • Asterisk with no explanation. A red star means nothing to a screen reader unless the word required is in the label or the code.
  • Colour-only errors. A red border with no text fails colour-blind visitors and everyone who cannot tell which field turned red.
  • No autocomplete. Making a visitor with a motor difficulty type a full address by hand, when their browser already knows it, is a barrier — not a style choice.

What this checker cannot do

  • It cannot crawl or submit your form — it only sees the label plan you enter here.
  • It cannot verify that a label is tied to its field in code (the for/id link) — only a scan or code review sees that.
  • It cannot test keyboard order, focus visibility or what a screen reader actually announces on your live page.
  • A passing score is not a certification of compliance with the ADA, WCAG or Section 508.

Get every provable barrier found for you

The Full Report scans your site against WCAG 2.2 AA and returns a dated PDF: every barrier found, ranked by severity, each tied to its WCAG rule with a plain-English fix. $15 one-time. The Watch Plan ($18/month) re-checks monthly so a form redesign does not quietly strip your labels again.

One-time payment · No recurring charges · 30-day refund policy · Full refund if the report fails to generate

Questions

Why do form labels matter for accessibility?

A visible label tied to the field in code is how a screen reader announces what to type, how a voice-control user targets the field by name, and how everyone re-checks a long form before submitting. Form labels are covered by WCAG 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value). A placeholder that disappears while typing is not a label.

Is a placeholder enough as a label?

No. A placeholder vanishes as soon as typing starts, is often too light to read, and is not reliably announced as the field's name. Use a placeholder only as a short example of the expected format — for example a date pattern — inside a field that already has a real, visible label.

How should required fields be marked?

Say it in words: put the word required in the label text, or explain before the form that an asterisk means required and mark each required label with that asterisk plus the word in code. Colour alone, or an unexplained asterisk, leaves screen-reader and colour-blind users guessing — WCAG 1.4.1 (Use of Color) and 3.3.2 cover this.

What is autocomplete for, in accessibility terms?

Fields that collect the visitor's own data — name, email, phone, address, card number — should carry the matching autocomplete token so browsers and assistive tools can fill them accurately. That is WCAG 1.3.5 (Identify Input Purpose). It cuts errors and effort most for people with motor or memory difficulties.

How should error messages work?

When a submit fails, name the field and the problem in text, next to the field, and move focus to a short summary. A red border alone is not an error message: WCAG 3.3.1 (Error Identification) requires the error to be described in text, and 1.4.1 forbids colour as the only signal.

If my form passes here, is my website accessible?

Not necessarily. This checker reviews the label plan you enter for one form. It cannot submit your form, read your code, or test keyboard order, focus visibility and contrast on the live page. A passing score is not a certification of compliance with the ADA, WCAG or Section 508.