Form builder software: a practical trial checklist

List the possible branches before configuring them. Submit a response through each route, then go back and change the answer that controls a branch. Inspect whether an answer to a now-hidden question remains in the submission. Repeat with an empty required field, a long response and an attachment at the configured limit. For scored surveys or calculated fields, retain the expected calculation and compare it with the exported value. Record the form version used so later edits do not make the trial impossible to reproduce.

Use the keyboard to reach every field, select an option, correct an error and submit. Confirm that labels and instructions remain visible when the form is embedded on the intended page. Ask a reviewer using assistive technology to assess the real task. The W3C forms tutorial covers labels, grouping, instructions, validation and feedback; use these topics to structure the review. A template description or a vendor accessibility statement does not replace testing the configuration your visitors will actually encounter.

Give each fictional response an identifier. Verify the confirmation, notification and destination record against that identifier. Pause a trial integration, submit a response and inspect how the failure is shown, who can see it and how the response is retried. Check for duplicate records after retrying. Repeat with the ordinary staff role instead of an administrator. Ask which features require another service or a higher plan. Keep a successful submission and a recovered failure as separate trial records.

Define which staff should see responses, attachments and shared reports, then test those paths with the corresponding accounts. Use only fictional data. Export a sample with multiple-choice answers, Unicode text, an attachment and a submission timestamp. Read it in an independent spreadsheet and confirm whether column names, timezone, field identifiers and attachment links are understandable. Ask what happens after a field is renamed or deleted. Include response limits, storage, collaborator roles and integrations in the written quote for your expected workload.