Audit the real form journey, not just its layout
Inventory every mobile form that matters: contact, booking, quote, newsletter, account creation, shipping and payment. Record the entry URL, required fields, third-party embeds, success state and whether a completed submission actually reaches the CRM or order system. Test on at least one current iPhone/Safari combination and one Android/Chrome combination with realistic saved profiles.
Do not assume a desktop developer-tools mobile viewport reproduces mobile keyboard behavior, password managers or wallet handoffs. Test with and without stored address data, with a long name, international phone number, apartment or unit, and postal code. Include slow connections and an interrupted submission. Capture screen recordings without exposing real customer data.
Use semantic fields that browsers recognize
Give each field a persistent label, suitable name and correct input type. Use autocomplete tokens such as name, email, tel, organization, street-address, address-line1, address-line2, address-level1, postal-code and country when appropriate. Use billing and shipping prefixes where both address types exist. The browser needs consistent semantics more than clever visual styling.
Google's web.dev form guidance explains that autocomplete attributes help browsers map saved data to the right fields. For an email field, type=email can assist with mobile keyboard selection, while autocomplete=email helps saved-address suggestions. For a postal code, do not force a numeric-only field: Canadian and UK codes contain letters. Avoid disabling paste or autofill to enforce formatting.
Inspect the validation and correction path
Submit the form with a missing required field, malformed email, extra-long name and invalid postal code. Check whether errors appear beside the right control, whether focus moves to the first actionable error and whether previously entered values survive. A generic red banner at the top is insufficient when the problematic field is several screens below.
Test the recovery path after a server timeout, expired session or payment rejection. Users should be able to correct one field without restarting the form. Prevent accidental duplicate orders or leads by handling repeated taps and idempotent submissions. Distinguish front-end validation from the server's authoritative validation, and never reveal sensitive payment data in logs.
Test payment and embedded handoffs
For ecommerce, inspect whether address and payment fields live in a hosted provider iframe, redirect or wallet sheet. The merchant's form semantics may not control provider fields; test the complete handoff instead of assuming one autocomplete change fixes the whole flow. Confirm that order totals, currency and shipping remain consistent after returning from a failed payment.
For lead generation, test CRM-connected embeds with mobile keyboard open and closed. Look for a sticky CTA covering the last field, a consent checkbox hidden under the keyboard, or a submit button that becomes unreachable. If a third-party form cannot be fixed directly, document the vendor issue and a fallback route rather than accepting silent submission loss.
Measure friction without collecting private input
Instrument form start, field-level validation failure counts, submit attempt, successful completion and server-side acceptance using privacy-conscious event names. Do not send typed names, emails, phone numbers or address values to analytics. Segment by device, browser and form version only where sample size supports interpretation.
Example: 500 mobile form starts, 300 submit attempts and 210 confirmed CRM records. The difference between attempts and accepted records deserves investigation before a design redesign. Pair session-level evidence with server logs and CRM reconciliation; client-side events can fire even when the backend rejects the submission.
Release checklist and decision rule
Create a matrix for device, browser, form type, saved-profile state, keyboard behavior, autocomplete mapping, error recovery, payment or CRM handoff and successful receipt. Require all high-value forms to pass the critical paths before release. Retest after payment provider, form library or design-system upgrades.
Read this alongside the website form-validation recovery and multi-step form audit articles. Use the Conversion Rate Calculator to estimate the business effect of recovered completions, but attribute improvements cautiously if other campaign or traffic changes occurred. The deliverable is a reproducible defect list, not a subjective opinion that the form feels easier.