Test with the keyboard and viewport in use
Mobile forms need readable labels, comfortable controls and layouts that remain usable when the keyboard opens. Use suitable input types and autocomplete where appropriate, but keep labels visible after typing. Avoid assumptions about names, phone lengths and addresses that exclude legitimate users. Test on actual interaction paths rather than only shrinking a desktop screenshot.
Worked example
Illustrative scenario; not a claim of measured client results.
A contact form may look fine until the keyboard covers the submit button or an error message shifts the page unexpectedly. Complete the fields, move between them, correct an error and submit in an authorized test flow. Check that sticky banners do not cover controls and that a long project description remains editable.
Checks, limitations and next decisions
If mobile completion is low, compare device-specific errors and observe the form directly before removing fields indiscriminately. A broken validation rule may matter more than the number of questions. Verify loading behavior on a constrained connection and preserve entered data after failure. The goal is a dependable route to a useful enquiry, not simply a visually compact form.
A practical starting point
Work through these checks in order. Use the results to decide what needs to change in your own workflow.
- Use appropriate input types and visible labels.
- Check spacing, zoom and focus behavior.
- Complete the form on a real mobile device under imperfect connectivity.
A mistake to avoid
Do not assume a responsive layout guarantees a usable form.
How to check progress
Measure mobile completion and inspect where validation or layout problems occur.
Your action checklist
Use this checklist while reviewing your own setup. Checkmarks are temporary and stay in this open page.
For the wider decision process, read Reducing friction in a project enquiry form.
Further reading
Official background resources for this topic. The workflow above is general guidance, not a guarantee of a particular result.
AI-assisted editorial content. Examples are illustrative, not client case studies. Read our editorial policy or report a correction.
