18 items4 sectionsFor Designers, frontend developers, conversion optimizers

Form Accessibility Checklist

Forms are where accessibility and conversion overlap most. The same patterns that screen readers need (clear labels, persistent error text, autofill hints) also drive higher form-completion rates for sighted users. This checklist covers both — pass WCAG and convert better.

References: WCAG 2.2 SC 1.3.1, 1.3.5, 2.4.6, 3.3.1, 3.3.2, 3.3.3, 3.3.7, 4.1.2

014 items

Labels

  1. 01
    Every input has a visible, persistent label (not placeholder-only)

    WCAG 3.3.2

  2. 02
    Label associated with input via for/id (not adjacent visual proximity)

    WCAG 1.3.1

  3. 03
    Required fields marked with both visual indicator AND text ("required")

    WCAG 3.3.2

  4. 04
    Optional fields explicitly marked when most fields are required (or vice versa)

024 items

Input Behavior

  1. 05
    Autocomplete attribute set per WCAG 1.3.5 (email, tel, name, etc.)

    WCAG 1.3.5

  2. 06
    Input type matches data (type="email", inputmode="numeric")
  3. 07
    Spellcheck disabled on usernames, codes, IDs
  4. 08
    Password fields have show/hide toggle, accessible label

035 items

Error Handling

  1. 09
    Errors appear near the field that caused them (not only at form top)

    WCAG 3.3.1

  2. 10
    Error text describes WHY + HOW to fix ("Email must contain @")

    WCAG 3.3.3

  3. 11
    Errors announced to screen reader via aria-live or role="alert"

    WCAG 4.1.3

  4. 12
    Error icon + color + text — not color alone

    WCAG 1.4.1

  5. 13
    Submit button stays enabled (don't disable based on perceived validity — let user try)

045 items

Focus & Navigation

  1. 14
    Tab order follows visual order through every field
  2. 15
    Focus indicator visible on every interactive element
  3. 16
    Skip-link to first form field if form is below masthead nav
  4. 17
    After submit error, focus moves to first invalid field (or to error summary)
  5. 18
    Time-sensitive forms (sessions) warn before timeout, allow extension

    WCAG 2.2.1

AccessAudit AI for iPhone

Run this on your phone.

Point your iPhone camera at any color pair to see its WCAG contrast ratio and whether it passes, in real time, on the device.

More for AccessAudit AI users