Aria Required Checker

Paste your page HTML and find bad aria-required tokens, asterisk-only required fields and missing HTML required.

What this tool gives you

token audit
asterisk labels
native required
visual-only fails

Check required fields

Paste your page HTML. Analysis runs locally in your browser — nothing is sent anywhere.

Asterisks and required classes need required plus aria-required="true" — never a made-up token.

What this checker looks for

WCAG 3.3.2 fails when a required field is visible but never marked. Unknown aria-required tokens are treated as off.

Valid tokens

aria-required must be true or false — yes/1 do nothing.

Visual cues

Asterisk labels and required classes need required or aria-required=true.

Native required

aria-required=true without HTML required will not block submit.

Hidden skipped

hidden, submit, button, reset and image inputs are ignored.

Lead forms

Quote requests and checkouts bounce when required is sighted-only.

0–100 score

Track required-field hygiene across templates, not just the homepage.

How to mark a required field

Three rules cover almost every silent required asterisk in the wild.

1

Set HTML required

Put required on the control. The browser then blocks empty submit.

2

Set aria-required true

true on the same control. yes, 1 or required are ignored by AT.

3

Match the asterisk

Name * is sighted-only until the control is marked required too.

Why answer engines care about required fields

Named required fields are a cheap-to-parse signal that the form can complete, not a silent trap.

SignalWhat engines inferWhy it helps
aria-required=trueThe field must be filled.Extractors can quote Email is required, not a red star.
HTML requiredThe browser blocks empty submit.Lower bounce on AI-referred lead forms.
No asterisk-only failsVisual and AT states match.AT users hear the same constraint sighted users see.
WCAG 3.3.2 passInstructions are programmatically determined.Citable, trustworthy pages get quoted more often.
Valid tokensThe page uses the platform API.true/false beat custom yes/1 flags.

Related GEO pages

Required fields pair with invalid-state wiring and autocomplete so the form is completable.

Aria required FAQs

What values does aria-required accept?

Only true and false. Tokens like yes, 1 or required are ignored, so AT never flags the field. Pair true with the HTML required attribute.

Is a red asterisk enough?

No. Sighted users see Name *. Screen readers need required or aria-required=true on the control itself. The checker fails asterisk labels with neither.

Does aria-required=true without HTML required fail?

It warns. AT hears the field is required, but the browser will still submit empty. Add the native required attribute so validation matches the announcement.