ACCESIBILIDAD ≠ OVERLAY · 45

Your details, once during the checkout

📅 20 November 2026   ·   ⏱ 6 min read

You enter your name, address and telephone number for a delivery. On the next screen the shop asks for the same information for the invoice. Each field means finding the control, recalling the value and checking the result. With a screen reader, dictation or an adapted keyboard, that repetition adds work to a task you already completed. Today’s article follows one checkout to identify repeated information and test whether shoppers can reuse it while retaining control over the final addresses.

01. Follow one order from the first field

Start as a first-time customer and record the details requested on each screen. Include contact, delivery, billing and order review. Look for repeated information even when labels differ. ‘Contact telephone’ and ‘Delivery telephone’ might refer to the same number in this order. Establish whether the second request has a specific purpose or comes from two modules that do not share data. First use identical delivery and billing addresses. Then try a case in which they differ. Together, these examples help distinguish unnecessary repetition from an option the person needs to complete the purchase. Record the route before changing the form so the team can compare the outcome afterwards.

02. Provide a clear way to reuse an address

An option such as ‘Use this address for billing’ lets the shopper choose information already entered. Another approach is to populate the fields and show how to change them. The option should identify which address it uses and which section it updates. Where several saved addresses exist, provide enough detail to recognise them without exposing another person’s information. Check the populated values individually. Region, country and postcode can have different internal representations in separate modules. Reuse needs to preserve the full meaning of the address and allow changes when an invoice requires different information. Include an address with a flat number and another with a second address line.

03. Keep a usable route to different details

Someone might receive a jacket at home and request an invoice for their business. After clearing the reuse option, the form should provide an understandable way to enter billing details. Inspect what happens to values that were already present. If retained, people need to understand which address they belong to. If cleared, verify that this follows an explicit choice. Select the option again and check whether it copies the current delivery details or an older version. This catches stale addresses after the shopper corrects an earlier step and returns to billing. Check both the visible values and the final summary because a correctly displayed field can still produce an outdated value later.

04. Check the change with keyboard and screen reader

Reach the option using Tab and listen to its name and state. Activate it with the keyboard and check whether the result is understandable. When fields disappear, focus needs a usable place to continue. Newly revealed fields should fit into a sensible navigation sequence. Listen to any announcement when the address updates. Avoid a chain of individual field messages that obscures the useful confirmation. Then read the order summary with the screen reader. Verify that both addresses can be identified and that the shopper can return to the appropriate section for editing. Previously confirmed contact details should remain available throughout that correction rather than requiring a complete restart.

05. Repeat after a validation error

Trigger a postcode error and submit the form. Correct that value and verify that the rest of the address remains available. Go back, change the street number and return to billing. Check whether the reuse option retains its selection and whether the resulting address contains the correction. Include a slow response or server rejection to see what information returns when an error is displayed. A team can mistake successful validation for successful preservation of state across screens. Record precisely when each value disappears. This helps locate whether the issue belongs to a field, the transition between steps or the service response, and makes a later fix easier to verify.

06. Examine browser autofill separately

Browsers can suggest stored personal details, and autocomplete attributes help identify the purpose of fields. Test this assistance separately because reusing data within an order also depends on the form’s own logic. Complete one journey with saved browser details and another in a test session without them. In both, enter a delivery address and check whether it can be used for billing without typing it again. Verify that delivery and billing groups are identified appropriately so the browser does not mix their values. Include a telephone number with an international prefix. Check the final summary after autofill as carefully as after manually entered details, especially when the shop offers several country formats.

07. Review the shop integration

A shop may combine its main checkout, a billing extension and a Divi customisation. Inspect the published result on desktop and mobile. Find which component copies the address and which preserves the selection between steps. If guest and account purchases are available, test both. A saved account address needs a recognisable and selectable presentation. For a guest, information from the current order should remain available as the person advances. Keep a straightforward example to repeat after updates to the checkout extension. Pay particular attention when an update changes field names, adds an order summary or introduces a separate invoice step. Compare the final values as well as the number of fields presented.

08. Try the guided journey with Blind Reader

Blind Reader offers voice navigation and guided shopping in WooCommerce, PrestaShop and Odoo. In Chrome or Edge, consult the help for commands available on the current checkout step. Enter delivery details, move forward and check whether the reuse option can be found and activated. The guided journey helps reveal the work each screen requires. Preservation and copying of values must also be checked in the shop itself. Repeat with a keyboard and screen reader to verify labels, the option’s state and the addresses in the summary. Record the observed behaviour without assuming that every integration has the same configuration or that every voice command is available on each screen.

09. Record the repeated requests and their purpose

WCAG 2.2 criterion 3.3.7 addresses information requested again within the same process. It covers automatic population or selecting available information, with exceptions for essential re-entry, security and information that is no longer valid. For your example order, record each repetition, the reuse mechanism and the outcome. Keep the shop address, guest or account route, browser and selected options. Another team member should be able to reproduce the purchase and confirm which values were retained. Finish by checking the order prepared for submission, its final addresses and the ability to edit them before confirming. This makes the record useful after a template change or checkout extension update.

W3C · WCAG 2.2 · 3.3.7

🧑‍🦯 Blind Reader
Intent narrator ready.

Accessibility guide

This is a functional summary, not a literal reading.

Go to primary goal Jumps to the main action area (form, list or contact).

Page type: article. The main goal seems to be: to inform you.

There are 16 sections you can jump to.

Before continuing:

  • Handle cookies/consent Reason: Detecté un aviso relacionado con cookies/consentimiento. — Recommended route: Contenido principal

Go by goals

Choose what you want to do. I will explain it, then ask before jumping.

  • Handle cookies/consent Important: this may block navigation.
  • Go to article content
  • Go to comments
  • Go to end of article
  • Back to News / Blog
  • Previous post
  • Go to Home
  • Go to About
  • Go to Products
  • Go to BlindReader
  • Go to Withdrawal Button
  • Go to Intent Flow
  • Go to Services
  • Go to Blog
  • Go to Contact
  • Go to Español
  • Go to Català
  • Go to Polski
  • Go to Română
  • Go to Italiano
  • Go to Français
  • Go to Svenska
  • Go to Deutsch
  • Go to Nederlands
  • Go to Português
Goal options
Confirmation mode

Choose how often I should ask before jumping.



Learning scope (only for “first time”)

Site: remember this goal across the whole site. Page: remember per URL.


Guided navigation

The guide announces one section at a time.

How it works: Start guide announces the first key section and scrolls to it. Next moves to the following section. To move focus to the section, use Go to current section. Stop exits.

Status: Guide inactive

Go to current section This link updates as the guide advances.

This article has approximately 1163 words.

Moves focus to the start of the content, skipping menus and secondary elements.

About Blind Reader

Blind Reader is an accessibility assistant that analyzes each page and narrates its purpose, key sections and recommended actions — designed for screen reader users.

Compatible page builders: Works with any WordPress theme or builder: Divi, Elementor, Gutenberg, WPBakery, Avada and others. It reads the real content of the page, not the builder markup.

Does it interfere with your content? It does not change your texts or your design. It only adds an accessible panel and fixes technical accessibility attributes (for example, names of buttons without text) so that screen readers announce them correctly.

How does it work? It analyzes the page structure (headings, links, forms, landmarks) and generates a functional summary. The guide and goals help navigate without having to scan the whole page.

Keyboard shortcut: Press Alt + G to jump directly to the first goal.