Define the minimum useful record
Start with the response itself, the attribution the contributor wants displayed and a clear permission question appropriate to the intended use. A public name and a private contact address have different purposes. Do not assume everything collected should appear in a widget. Explain required fields and leave unnecessary demographic or business details out.
Check display behavior separately
Boast documents text, media, identity and consent fields, but a collected value and a displayed value are separate decisions. A reviewer should know which fields remain internal and which can be included in a public presentation. Use fictional entries when checking a form layout so real customer information is not exposed during a preview or configuration review.
Use labels people can understand
A field name should describe what to enter without relying on placeholder text alone. Group related questions and make error messages specific. A person using a keyboard or assistive technology needs the same context as someone looking at the visual layout. W3C’s linked guidance is a useful reference; our checklist is not an accessibility certification.
Test omission and correction
Try the cases of an optional company name left blank, an invalid email format and a contributor changing their displayed name. Confirm that the page explains what needs correction without losing a long response. These are suggested acceptance cases, not merchant test results. Do not add extra required fields merely because the software offers them; each creates another burden and another piece of data to maintain.
An original decision example
Illustrative field review: collect a private reply address for clarification, a chosen public name for attribution and an optional organization. Verify that the reply address never appears in the intended public component. Treat those as three separate purposes instead of labeling every field customer information and displaying them together.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Boast form-field descriptions — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- Boast consent states and agreed terms — Merchant documentation · boast.io · Merchant-controlled · checked 2026-09-24
- W3C WAI form-label guidance — Standards and certification reference · w3.org · Publisher independence not verified · checked 2026-09-24