technology, smartphone, phone, cell phone, mobile, touchscreen, hands, girl, woman, people, cell phone, cell phone, cell phone, cell phone, cell phone, touchscreen, touchscreen, touchscreen, touchscreen, touchscreen
Photo by kaboompics on Pixabay

Checkout Usability

Part of Mobile checkout

Choosing mobile-friendly address inputs

Address inputs should help a buyer enter a deliverable address with minimal correction.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Checkout Strategy.

undefined

Choose between a whole-address field and separate fields based on whether checkout needs flexible free-text entry or separately collected address components. An address lookup is another option, but keep manual entry available so buyers are not required to select a suggestion. The UK Design System pattern explains when to use multiple text fields, an address lookup or a single text field (DWP Design System).

Let the address fit the person

Show persistent labels for name, street, suburb, state or territory, postcode and country as relevant. For Australian checkout, keep those address parts distinct where needed; do not use one example address as a rigid validation rule for every destination. On mobile, take care with label and input placement (Smashing Magazine).

Use a <textarea> with autocomplete="street-address" for one whole address. For separate street, suburb, state or territory and postcode fields, use type="text" inputs; set inputmode="numeric" on the postcode field to request a numeric virtual keyboard, not to validate the value. Aim for a minimum 44px touch target for fields and controls (Ivy Forms).

Use the autocomplete values name, street-address, postal-code and country where they match the field’s purpose. For separate street lines, use address-line1 and address-line2 (GOV.UK Design System). For the suburb or town and city field, use address-level2 (MDN). For a postcode field, identify the address type with a prefix such as autocomplete="shipping postal-code" or autocomplete="billing postal-code".

If you offer address lookup suggestions, let the buyer edit a suggestion and show the full resulting address before payment. Keep manual entry available alongside lookup, and ask for apartment details or delivery instructions when they matter. If you offer a separate Address line 2 field, make it optional (GOV.UK Design System).

W3C WCAG 2.2 Success Criterion 1.3.5, Identify Input Purpose (Level AA), says the purpose of each input field collecting information about the user must be programmatically determinable when the technology supports it. Autocomplete identifies purpose more precisely than a broad input type, but it does not replace meaningful labels or accurate validation.

Best Practices for Mobile Address Inputs in Australia

  • Use persistent labelsShow clear labels for name, street, suburb, state or territory, postcode, and country. Avoid placeholder-only text.
  • Optimise keyboard inputApply `inputmode="numeric"` to postcode fields to trigger a numeric keypad on mobile devices.
  • Keep manual entry availableEven with address lookup, allow users to edit suggestions and enter addresses manually.

Test correction on a phone

Try a long street name, a unit number, an address without an obvious suburb match and an invalid postcode. Check that an error appears near the affected field and that the buyer can move to the next field without losing entered text. On a phone, check that the postcode field requests a numeric keyboard and that fields and controls are easy to tap.

Compare the final shipping summary with the entered address; a shortened form that silently changes a unit number can cause a costly delivery problem. Measure correction rates, support contacts and time to complete.

Key Metrics for Evaluating Address Input Usability

Correction Rate
Measure how often users need to correct their address after submission.
Support Contact Volume
Track increase in support requests related to incorrect or missing address details.
Time to Complete Checkout
Monitor average time taken to enter an address on mobile devices.
Postcode Keyboard Trigger
Verify that postcode field automatically opens numeric keyboard on mobile.

More from Checkout Usability