Your destination for everything in the adult industry.
ATN — All Things NSFW. Explore. Create. Build.

Explain required form fields before submission.

A form should explain what information is needed before someone encounters a validation error. Review the required and optional fields, their visible labels, and any format rules together. This guide focuses on instructions before entry; error recovery and browser autofill remain separate checks that should agree with those instructions.

1. Confirm what the task actually requires

List each field, its purpose, whether it is required, and any conditional rule. Ask whether the task can be completed without optional information and whether the interface makes that choice clear. Keep the content requirements aligned with the validation behavior instead of labeling a field optional while rejecting a blank value.

W3C’s explanation of WCAG 3.3.2, Level A, says the criterion covers optional as well as required input. An optional field still needs an understandable purpose. Review the complete form rather than limiting the check to the fields marked mandatory.

Sources: [1]

2. Use visible labels and explain markers

Give each field a label that a reader can understand before entering information. If the design uses a marker for required fields, explain its meaning near the start and keep the treatment consistent. Do not expect an unexplained asterisk or a color change to carry the whole instruction.

W3C distinguishes visible labels or instructions from correct programmatic associations and accessible names, which are addressed by other criteria. Check both aspects rather than treating an invisible name as a substitute for useful visible guidance. Keep the label available while the reader reviews a completed field.

Sources: [1]

3. Provide necessary formats and examples early

Identify fields whose accepted format is narrower than a reader might expect. Give a short, relevant example or instruction before submission and check that the example itself is accepted by the form. Avoid exposing real personal information in examples or adding rules that the service does not actually require.

WAI recommends explaining required or optional input, formats, and other relevant instructions. It also describes the limitation of placeholders that disappear during entry. Keep essential format guidance available when someone returns to review or correct the value.

Sources: [2]

4. Associate field-specific help with its control

Place a hint where its relationship to the field is visually clear, then inspect the programmatic relationship. WAI describes aria-describedby as one way to associate additional instructions with a form control. Use the appropriate native labels and grouping alongside any needed description.

Test the actual browser and assistive-technology combinations in scope. Record whether the relevant label and hint are available at the point of entry without assuming that their proximity in a screenshot establishes the relationship. Keep long background explanations outside a short field hint when they interrupt the task.

Sources: [2]

5. Try empty, partial, and corrected entries

Use harmless sample data in the approved test environment. Try an empty submission, a partially completed form, an optional field left blank, and a value corrected after an error. Compare every outcome with the instructions given before entry. An unexpected rejection may reveal an undocumented rule or a mismatch in validation.

Review desktop and mobile layouts, including wrapping around long labels and hints. Record the form version, conditions tested, actual outcomes, and remaining questions. Confirm that error messages explain the same requirement already presented to the reader. This component review does not establish full WCAG conformance or authorize a real customer submission.

PUT IT INTO PRACTICE

Your quick checklist

  • Each field has a defined purpose and requirement.
  • Visible labels and required markers are understandable.
  • Necessary formats and examples are available before errors.
  • Field-specific hints have appropriate associations.
  • Empty, partial, optional, and corrected states agree with the instructions.

Sources & scope

W3C supports the labels/instructions scope and WAI implementation examples. The inventory and submission scenarios are ATN editorial guidance. No form was submitted or assistive technology tested for this article; complete conformance requires broader review.

  1. W3C WCAG 2.2: Labels or instructions (opens in a new tab)Source checked October 10, 2026
  2. W3C WAI: Form instructions (opens in a new tab)Source checked October 10, 2026

Published October 10, 2026. No affiliate links or paid placements in this guide.

ALL THINGS NSFW