Gravity Forms' “Same as previous” address option needs two checks: the right values must reach the entry, and users must understand what changed. A checkbox that copies an address visually can still create confusion for keyboard or screen-reader users. Test both selecting and clearing it on the published form.
Identify the source and destination fields
Record the form ID and both Address field IDs. Give the fields clear labels such as delivery address and billing address. Confirm which field the copy option references, rather than assuming it means the immediately preceding visual section after a form redesign.
The Address field documentation describes the copy-values option and its label. Use wording that describes the real relationship. “Billing address is the same as delivery address” is more informative than a vague instruction when other address fields appear nearby.
Reproduce with synthetic addresses
Use a staging form with outbound payments and customer messaging disabled through the site's approved test configuration. Enter a recognizable synthetic source address and a different destination address. Select the copy option, then inspect which fields change and whether the destination remains editable.
Clear the option again. Verify the resulting values rather than assuming previous values will always be restored. The acceptable behavior must be clear to the user and appropriate to the form's purpose. Do not silently submit an unexpected billing address simply because validation passed.
Labels: Relationship is explicit. Keyboard: Select and clear work. Announcement: Change is understandable. Entry: Expected address persists. Explanatory checklist, not a customer test result.
Test the announcement, not just keyboard focus
Gravity Forms' changelog lists a 3.1.3.1 fix for screen readers not being notified when users select or clear this option. Verify the installed release and rerun the interaction on a supported browser and screen-reader combination. A release note does not certify your customized form.
Navigate to the checkbox using the keyboard, listen to its name and state, select it, and continue through the form. Confirm that the change is understandable without seeing the screen. Clear it and verify the announcement and focus location again. Custom JavaScript, hidden sections or replacement field markup can alter the experience.
Compare the submitted address with downstream mapping
Run four cases: copy off, copy on, source edited after copying, and copy cleared before submission. For multi-page forms, add a previous-page visit before the final submission. Compare the resulting entry with any shipping, invoice or CRM address mapping.
Record country and state values as well as street text. A field label shown to the visitor is not necessarily the stored choice value expected by an integration. Preserve the mapping used by the installed version rather than substituting labels blindly.
If submission fails only when copied fields are hidden, inspect the required-field validation rules. Do not remove required-address checks globally to make one branch pass.
Deliver the field IDs, tested interaction paths, saved values and accessibility observations without real customer addresses. HandL WP can repair the form interaction and check that its stored entry still supports the business process.
References reviewed October 12, 2026. Examples are explanatory, not customer test results.