Checkout focus jumps away from the step being completed

Identify the transition, not just the final screen

Start with the reported checkout state and one triggering action. Record whether the buyer changed an address field, left that field, selected a shipping option or selected a payment choice. Those are different triggers even when they eventually produce the same screen. Note the browser, device, checkout URL and observation time so the maintainer can locate the affected version.

Record focus immediately before the action, immediately after it and after the update has settled. Also record any scroll movement separately. A page moving up or down is not enough to establish that keyboard focus moved. If the destination cannot be identified, write unknown rather than naming the control nearest the visible viewport. Keep customer values out of screenshots and notes; field labels and non-sensitive state descriptions are enough to identify the transition.

Judge the sequence by the work still required

WCAG 2.2 success criterion 2.4.3 concerns focus order: when sequential navigation affects meaning or operation, the sequence must preserve both. That is a functional requirement, not a demand that every update send focus to one universal destination. The relevant question is whether the buyer can understand and continue the current task after the change.

Compare the new focus destination with the new content location. Note which required input remains, whether that input can still be reached in a meaningful sequence, and what the next Tab or Shift+Tab actually reaches. If the buyer has to traverse unrelated navigation to return to the unfinished step, describe that detour. If focus deliberately moves into the next necessary step and the buyer can continue coherently, record that too. An unexpected movement deserves inspection; surprise alone does not establish the cause or a complete conformance finding.

Give the implementer a before-and-after map

Ask the maintainer to connect the recorded trigger to the part of checkout that changed. Useful investigation questions are whether the previously focused control remained present, whether a different control replaced it and whether the update explicitly assigned a destination. These are questions for inspecting this installation, not diagnoses inferred from a screenshot. A theme, store extension or payment component should not be named as the cause until the observed update is traced to it.

Define the desired behavior in task terms: after this particular update, the buyer can locate the next required input and proceed in a meaningful sequence. Keeping focus on an unchanged control may satisfy that goal; when the control no longer exists, the implementer needs a suitable continuation. Do not prescribe moving focus to the top of the page after every recalculation or moving it to every new message. Either blanket rule can ignore the step the buyer is completing.

Close the reported transition with an observable result

After an authorized repair, observe the same action in the same checkout state and compare the new destination and subsequent keyboard sequence with the original map. Keep the result narrow: the recorded transition now allows continuation, still causes a detour or remains unverified. Stop before placing an order or submitting payment. An interaction check does not establish the payment result or the accessibility of every other checkout state.

For a Prism checkout consultation, describe the transition, the remaining task and the component owner if known. Use the checkout-review service to agree on the investigation or implementation requested, responsibilities, fees and terms. A focus repair does not establish provider eligibility, and this worksheet is not a WCAG certificate.

Focus-transition map

Complete one map for one observed state change. Use control labels rather than entered customer data. Read the before, after and next-step entries together: they show whether the update interrupts the unfinished task. Leave unobserved destinations unknown.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.