A form can look correct while the browser pastes one address into two different jobs. Decide whether the fields describe the customer, the delivery recipient or the invoice contact before commissioning another form redesign. Clear purposes matter more than switching autofill off everywhere.
Who should use this acceptance brief
Retailers and service firms with repeated contact fields. Use this as a scoped commissioning task for a website supplier. Where system evidence is required, a teaching file is not a substitute.
Source-bound platform fact
Autocomplete tokens can name a section, a shipping or billing group and a field purpose. They are browser hints, not a promise that every device will populate a field. MDN: autocomplete · Checked 16 October 2026.
Filled teaching example
Synthetic example, not a client case. Inputs, expected decisions and counterexamples follow; no live platform integration is claimed.
On narrow screens, scroll to read the complete table.
| Input / case | Check basis | Expected decision |
|---|---|---|
| shipping postal-code | billing postal-code | distinct groups |
| section-a shipping postal-code | section-b shipping postal-code | distinct recipients |
| same purpose |
Run the acceptance exercise
- List each repeated field and its real recipient.
- Map address and contact purposes, then use two deliberately different test profiles.
- Test saved-profile fill, manual correction and submission in each supported mobile browser.
Interpret the result and retain evidence
The first case keeps delivery and billing distinguishable. The second separates two delivery recipients. The third is deliberately not a separation mechanism: repeating the same tokens may reuse a value. A passed offline token comparison proves naming only; inspect the actual submitted payload with synthetic details before acceptance.
Limits before implementation
Exclude payment-card data, password-manager guarantees and automatic address validation. Store the browser/version and a redacted field map, not a customer address book.
Replay the finite example
Save both files in one folder and run with Node22.13 or newer. These finite checks are not a live service or certification. Filled inputs and expected outputs · Inspectable functions
node decision-check.mjs contact-autofill-tokens.json