adzup✦GOOD THINGS START WITH CURIOSITY.
STRATEGY × CREATIVE × TECHNOLOGYSay hello on WhatsApp ↗

Test the keyboard, not just the layout: a mobile enquiry-form review.

A focused QA plan for mobile keyboards, autofill, validation and recovery before sending more paid traffic to your enquiry form.

Read as text ↗
Make yourself comfortable
0% read
In this article
THE STARTING POINT

A focused QA plan for mobile keyboards, autofill, validation and recovery before sending more paid traffic to your enquiry form.

01 / THE FIELD NOTES

Open the form on a real phone.

A mobile page can look excellent in a presentation while the actual enquiry feels awkward. The keyboard covers the next control, saved contact details fill the wrong field, or one rejected value erases the rest of the message. These are interaction faults, so a screenshot of the page at a narrow width is not enough to accept the work.

This review uses existing web.dev forms documentation checked on 19 November 2026; it is not a newly announced browser feature. Set one concrete task before testing: a prospective customer should be able to send a simple, relevant enquiry and understand whether it was received. Use synthetic information during QA. Do not turn a usability exercise into a collection of real customers' contact details or sensitive requirements.

02 / THE FIELD NOTES

Make the field match the information requested.

web.dev explains that an input's type can affect both its interface and validation, while inputmode changes the on-screen keyboard without changing the input's underlying behaviour. That distinction matters when a form looks right but rejects reasonable entries. Ask the developer to justify the field behaviour, not merely demonstrate that a numeric keyboard appears.

Illustrative example: a quotation form asks for a telephone number. A visitor may include a country code or spacing, so treating the answer as a mathematical quantity creates unnecessary constraints. Test the intended formats and make any genuine limitation clear before submission. For every field, check the visible label, the keyboard shown, the ability to paste and what happens when the visitor moves to the next control. Keep decorative placeholder text separate from essential instructions.

03 / THE FIELD NOTES

Check autofill as its own journey.

web.dev's autofill guidance describes the role of meaningful field identifiers and appropriate autocomplete values in helping browsers supply saved information. Ask the team to configure these deliberately for the details the form actually needs. A form that works when every character is typed manually can still fail when a browser fills several fields at once.

Run a second test using a controlled browser profile with synthetic saved details. Confirm that the right information lands in the right control, remains readable with the site's styling and is included when submitted. Then repeat without saved details. Browser behaviour varies, so record the devices and browsers tested rather than announcing universal support after a single demonstration. Do not disable helpful browser behaviour simply to preserve the visual appearance of an empty form.

04 / THE FIELD NOTES

Give errors a recovery route.

web.dev's validation guidance recommends communicating requirements and using suitable browser validation features; it also states that server-side validation is still necessary. For a buyer, the acceptance question is whether an ordinary mistake can be corrected without starting over. Test an omitted required field, an incorrectly formatted answer and a temporary delivery failure as separate conditions.

Ask the team to show what the visitor sees, which control needs attention and whether previously entered information remains available safely. A confirmation should follow successful receipt, not just a button click. Where a form provider handles submission, include its returned state in the QA plan. Avoid copying raw field contents into analytics events or error logs to explain a usability issue; field names, failure categories and synthetic test references are usually a better starting point.

05 / THE FIELD NOTES

Turn the findings into one measurable improvement.

Write each issue as an observable task failure: the phone field rejects an intended format, the keyboard hides the error, or autofill leaves a required control incomplete. Give the developer a reproduction path and expected behaviour. This is more actionable than requesting a more premium form, and it lets the business confirm the repair without approving another full redesign.

After a change, repeat the same tasks on the agreed devices and check receipt in the destination system using synthetic submissions. If you also analyse real form progression, define the events, consent requirements and reporting limitations first. Compare confirmed submissions separately from form opens and button clicks. A small traffic sample or a change in audience can distort the apparent improvement, so report what the evidence supports rather than claiming the keyboard adjustment caused a lead increase.

  • Test manual entry, autofill and correction as separate paths.
  • Record device, browser, expected behaviour and a reproducible failure.
  • Verify successful receipt and safe recovery before increasing traffic.
FROM READING TO A REAL PROJECT

What would this
look like for you?

Turn your service story into a website with a clear, usable enquiry journey. Explore our lead-generation websites service, or tell us what you are working on so we can discuss the scope.

Explore Lead-generation websites ↗

Put the thinking into practice.

Sources & further reading

Platform references support the factual background. The planning recommendations are AdzUp’s editorial interpretation.

A useful read.
A clearer next move?

Keep exploring, or bring your questions to AdzUp.

← Back to the reading room

From “interesting”
to “let’s do this.”

Bring your questions. We’ll start with your business, your audience and the next move you want to make.

Put the thinking to work ↗