Teaching · Special Education

Give every field a label that stays put.

Log each field with its label, instructions and required marker. The review lists the fields to fix with the WCAG criterion behind each problem.

Review a formWhat you get
$12one-time · every device you sign in on
Buy · $12

Included with Caveat Classroom and Whole-school licenses. Or get it in the Special Education toolkit, $99 for 100 items.

The form review

One record per form. The example is made up.

Loading the form. If nothing appears, turn on JavaScript.

What you get

Teaching · Special Education$12 · included with Classroom and Whole-school licenses

What you finish with
A field-by-field fix list with WCAG criteria, and the form-wide changes to make.
Who it is for
Accessibility leads, web and communications staff, teachers building online forms and instructional technology staff.
Format
Browser checklist. One saved record per form; printed for whoever builds the form or as a blank form; CSV of the fields; export and import a file.
Access
$12 one-time, yours on every device you sign in on; the tool opens once you are signed in with it. Included with Caveat Classroom and Whole-school licenses. Also in the Special Education toolkit ($99) and the Teaching Suite pass ($199), and 1 more bundle. Everything you type stays in this browser; nothing is sent to Caveat.
Where it lives
The Special Education space in Caveat Teaching.
Support
Questions about an order, access or a correction: team@caveatacademic.com.
you@example.comParent email (required)a label that stays when you type
Drawn for this page. A placeholder disappears as soon as someone starts typing; a label stays, and a screen reader can announce it.

How to use it

  1. Start a record with a short form code.
  2. Add each field in the order it appears.
  3. Use the browser inspector or a screen reader to see whether each label is connected.
  4. Mark how required fields are shown.
  5. Send the printed fix list to whoever builds the form, then review again.

Review a form

What the criteria ask for

Labels

Every field needs a visible label that is also connected to it in the code, so a screen reader announces it (WCAG 1.3.1, 4.1.2). Placeholder text vanishes when typing starts and is often too faint to read; it does not count as a label.

Required fields

Show that a field is required in text, or with an asterisk explained at the top of the form. Color alone fails WCAG 1.4.1, and an unmarked required field fails 3.3.2 when the error only appears after submitting.

Autocomplete

Fields that ask for the user’s own name, email, phone or address should support autocomplete (WCAG 1.3.5), which saves typing for everyone and effort for people with motor or memory difficulties.

Sources

  1. W3C. Web Content Accessibility Guidelines (WCAG) 2.2: 1.3.1, 1.3.5, 1.4.1, 3.3.2 and 4.1.2.
  2. W3C Web Accessibility Initiative. Forms Tutorial: labeling controls, grouping controls, form instructions.
  3. U.S. Department of Justice. Accessibility of Web Information and Services of State and Local Government Entities, 28 CFR Part 35, Subpart H (2024).
  4. WebAIM. Creating Accessible Forms.

The example form is made up. Support: team@caveatacademic.com.