Keyboard focus disappears against the checkout background

Establish that the control has focus

Use the real checkout state associated with the report and note the browser, device and any active appearance setting. Move through the controls with the keyboard. Record the last position you could identify, the next control you expected to reach and the first point where the visible cue disappears. Keep the mouse out of the interaction while making that observation so a pointer highlight does not substitute for the keyboard cue.

A missing ring does not by itself tell you whether focus stayed on the intended control, moved to a different control or left the expected sequence. If the destination is unclear, mark it unconfirmed and ask the maintainer to identify the focused element. Do not press Enter on an unidentified control to discover what it does. Stop before order placement or payment submission. This page concerns visibility once focus is located; an unrelated focus destination needs its own transition investigation.

Compare the indicator with the state around it

For a confirmed focused control, describe the visible treatment rather than assuming every interface uses an outline. Record any border, underline, background change or other cue that identifies the current keyboard position. Then note the surrounding background and whether the control is selected, showing an error or in another observed state. A permanent selected appearance is not sufficient evidence that a buyer can tell which control currently has keyboard focus.

Inspect the states that actually occur in the reported workflow. If an indicator is visible against one background but disappears after a payment option expands, record those observations separately. If it exists but is covered or cut off, describe that visible obstruction rather than claiming the indicator was never drawn. A screenshot can capture the appearance; the preceding keyboard steps establish how that state was reached. Remove entered customer information before sharing evidence.

Observe persistence as well as initial appearance

WCAG 2.2 success criterion 2.4.7 requires a mode of keyboard operation with a visible focus indicator. W3C’s understanding page also says that indicator must not be time limited. A cue appearing briefly on arrival therefore does not resolve the question of where a buyer can see their position while they remain on the control.

Pause with focus on the affected control and record whether the cue remains, fades or disappears during a checkout update. Record only the duration actually observed; there is no invented waiting period that proves every state works. If the cue vanishes, first establish whether focus remained on that same control. A timed disappearance with unchanged focus is a different repair question from an update that moved focus elsewhere.

Do not assign a numerical contrast pass from a visual impression or borrow a text-contrast threshold to grade the indicator. This record names an observed visibility problem. Any broader assessment needs the criteria and measurements appropriate to its agreed scope.

Specify a visual repair that preserves operation

Give the designer and maintainer the control label, observed state, background and duration together. The requested result is that the current keyboard location stays visible while the buyer remains there, including the state where it was lost. Identify who owns the component before choosing the change; a screenshot alone does not establish whether the merchant’s theme or another component controls its appearance.

After the authorized change, revisit the affected control and state, confirm the position is visible and observe whether it remains identifiable during the same pause or update. Preserve the existing control behavior, payment choices and required notices. There is no need to collect a payment to establish whether a focus cue is visible.

Bring the specific visual observation to a Prism checkout consultation and describe the assessment or repair you need. Scope, responsibilities, fees and terms are agreed before work. A repaired indicator does not certify the whole checkout or establish provider eligibility.

Focus visibility record

Use one record for each affected control and actual visual state. Enter labels and observations, not customer values. If focus itself is unconfirmed, resolve that before attributing the problem to styling. Compare the same state after an authorized repair.

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.