Contact form launch checklist

Follow an enquiry from keyboard to inbox.

Start before the submit button

Every field needs a clear visible label. Ask only for information needed to respond. Explain required fields before the visitor makes a mistake, and make the error message identify the affected field. A placeholder that disappears when typing is not a durable label.

Test the complete delivery path

Send a clearly labeled test enquiry using a mailbox you control. Confirm the destination received it and that reply handling works. Check that the success message appears only after a confirmed acceptance. A friendly screen does not prove delivery; record both observations.

Check slow and failed requests

Try a disconnected connection or a controlled failed endpoint in a test environment. Preserve the visitor’s entered text and explain how to retry. Prevent accidental double submission without trapping the visitor. Avoid placing an advertisement beside the submit button, where it can be mistaken for a form control.

Try correcting an error with the keyboard

Leave a required field empty and submit using the keyboard. Check that the message names the field and explains how to correct it. The visitor should be able to reach the field from the error or through sensible focus handling, while previously entered values remain available. Do not rely on a red border alone. After correcting the field, confirm that the error clears and the form can be submitted.

Review the human workflow

Choose who monitors the inbox, what information should never be submitted, and how long enquiries are kept. Test keyboard navigation and a phone-sized screen. If using a third-party form service, include it in your actual privacy disclosures. Recheck delivery after changing DNS, mailboxes, spam settings or the form provider.