Scenario · Content and search
Add or change a form
“We need a form on this page.” Or: “Add a field to the contact form.”
A form is the one part of a medical practice's site that directly makes money, and the one whose failure is completely silent — the people who'd report a broken form are exactly the people who couldn't reach anyone through it. This actually submits the form end to end rather than just confirming it renders, which is the only way to catch a form that looks perfect and silently rejects every entry; confirming the notification actually lands in the right inbox is still a manual check afterward.
What to ask for
See it work
A real run of Form submittability:
Form submittability · form-submittability — https://toolkit-tests.pages.dev/forms/overlay-submit.html (devices: desktop,iphone-17)
FAIL — https://toolkit-tests.pages.dev/forms/overlay-submit.html
✗ the submit button is covered by a fixed element (div.banner) — clicks land on the overlay, the form cannot be sent
• field textarea [message] is covered by a fixed div.banner — a visitor may not be able to click it
• field button is covered by a fixed div.banner — a visitor may not be able to click it
report: ./out/form-submittability-form-submittability.html
text: ./out/form-submittability-form-submittability.txtThe captured report, exactly as a run hands it to a client —open the full report ↗
A form is the only component on a medical practice site that directly makes money, and the only one whose failure is completely silent — nobody reports a form that stops submitting, because the people who would report it are the ones who could not reach you.
- Establish what the form must capture and where it sends. Fields, required-ness, destination inbox, and whether a submission should count as a conversion. The destination is the part most often left unstated and the part that fails.
- Snapshot the page.
- [manual] Build or edit the form in the CMS. Add the fields, set the notification recipients, and wire the confirmation the visitor sees. Keep the field count as low as the request allows — every extra required field costs completions. Publish and purge.
- Actually submit it. The submittability check exercises the form end to end rather than confirming it renders. A form that looks right and rejects every submission is the failure mode this catches, and it is invisible to every other check on this list. Use a test address the practice recognises, never a real prospect’s details.
- Confirm the submission arrived, by hand. Check the destination inbox. The check proves the form accepted the submission; only the inbox proves the notification was delivered.
- Check the conversion fires. The analytics and tag audit confirms whether a submission is being recorded as a conversion. A working form that reports nothing makes the practice’s own numbers wrong, and it looks fine from every direction.
- Verify presentation. Link and image check on the page, before/after comparison, and screenshots across devices — forms are a common mobile casualty, with fields running off the viewport or a submit button pushed out of reach.
Test with a real submission, and say so
Step 4 puts a real entry into the practice’s own lead flow. That is the point — a form is not verified by inspection — but it means using an address everyone recognises as a test, and telling whoever watches that inbox that it is coming. A test lead mistaken for a real one wastes a callback.
What this does not cover
Where the submissions go. It proves a form can be submitted and that a conversion fires; it cannot confirm the notification reaches the right inbox, that the practice is answering it, or that the data is handled lawfully. A form carrying patient information has consent and privacy obligations that no check here evaluates, and those are the ones with real exposure.