# Form Instruction Accessibility Check

Review labels, requirements, examples, input formats, help, errors, recovery, timing, privacy context, confirmation, and completion instructions in forms.

## Usage note

Test the complete rendered form using keyboard navigation, relevant assistive technology, zoom, and realistic validation states. This content checklist supports but does not replace technical accessibility testing, privacy review, security review, or applicable legal assessment. Use non-production data and never expose real personal information during testing or screenshots.

## How to use this template

1. Inventory form purpose, audience, fields, requirements, sensitive data, time limits, and final consequence.
2. Review labels, groups, examples, formats, help, and required-state communication before input.
3. trigger every validation, server, permission, and timeout error and inspect recovery.
4. Test keyboard order, focus, announcements, zoom, mobile layout, review, submission, and confirmation.
5. Resolve content and implementation defects, then verify the complete live journey with safe data.

## Blank template

### Form context

- **Form and version:** [URL/build]
- **User task:** [What submission accomplishes]
- **Audience and access needs:** [Relevant range]
- **Sensitive fields:** [Personal, financial, health, other]
- **Required/optional convention:** [How communicated]
- **Time limit and save behavior:** [Details]
- **Final consequence:** [Account, payment, request, publication, other]
- **Test environment:** [Browser, device, assistive technology]

### Field or state record

- **Field/group:** [Name]
- **Visible label and accessible name:** [Exact]
- **Requirement and format:** [Rule]
- **Example or help:** [Exact]
- **Current error:** [Exact message]
- **Recovery instruction:** [How to fix]
- **Focus/announcement:** [Observed result]
- **Value preserved:** [Yes/no]
- **Privacy context:** [Why requested and link]
- **Revision/owner:** [Content or implementation action]

### Completion checks

- [ ] Labels persist and are programmatically associated.
- [ ] Required status and formats appear before submission.
- [ ] Errors identify problem and recovery without color alone.
- [ ] Valid entries and focus are preserved.
- [ ] Timeout and server states explain submission status.
- [ ] Final action names the real consequence.
- [ ] Confirmation provides status and next step.
- [ ] Keyboard, zoom, assistive technology, and mobile states are tested.