Can shoppers close my enlarged product photo and continue where they left off?

Follow the shopper rather than the cursor

Begin on a saved draft product with several views. Put the mouse aside, reach an enlargement control with Tab and activate it. Record the first focused item, its visible indicator and what happens on the next few Tab presses. Ask whether the shopper can identify the current view and find a way to leave without restarting the page.

W3C’s modal dialog pattern describes focus inside the dialog, an Escape exit and a usual return to the invoking control. Your theme maintainer should check actual behavior against the chosen pattern. Adding a dialog attribute alone does not create that behavior.

For a modal viewer, test both Tab and Shift+Tab at its boundaries, not just the first forward move. Check the actual focused element and its visible indicator; a border drawn around a thumbnail may be selection rather than keyboard focus. Record the exact opener and the first/last reachable controls so a maintainer can reproduce the route.

Capture a specific return failure

In this fictional example, a backpack shopper opens the interior-pocket photo from the third thumbnail. Closing the viewer sends focus to the page header, while the selected thumbnail remains the interior view. The picture itself is correct. Replacing it would not repair the lost place in the buying journey.

Give the theme maintainer a bounded repair

Ask the maintainer to preserve the invoking control, choose a sensible initial focus, support a visible close action and restore a logical place after dismissal. For a genuinely modal viewer, background controls should not remain part of the active keyboard route. If the opener is removed during a variant update, agree a documented fallback instead of returning focus to a missing element.

Include the theme version and browser in the report. Repeat the route from a second thumbnail and through the visible close button as well as Escape. Keep this repair separate from pinch magnification and thumbnail naming; those are different shopper tasks.

The W3C pattern also permits another logical return point when the completed workflow justifies it, even if the opener still exists. For a simple product-photo inspection, returning to its invoking thumbnail will usually preserve context. Document any chosen exception and test that it does not strand the shopper. Preserve the selected product/view separately from focus.

Retest the full inspection journey

The acceptance exercise is concrete: open the interior view, inspect it, close it and reach the next product view without visiting unrelated navigation. Also verify that the selected product and any entered quantity survive the interruption. A single successful mouse click is insufficient evidence for this keyboard route.

Use the gallery interaction review as a manual review record. Sample rows are fictional. It does not connect to, import into or modify an external store or production machine.

CartVisual can help prepare reference-led interior or detail imagery for human review. Its files do not install a viewer, manage focus or certify your external store. Record the interaction fix with the theme owner separately from asset approval.

Record opener → initial focus → last forward/reverse focus → closing action → actual return. Run Escape and the visible close action as separate cases. A removed opener is another case, not proof that a header jump is appropriate. Check option state if the viewer can survive a variant update, and keep touch discovery as a separate route.

The shared gallery CSV currently contains only two fictional pending examples: keyboard-dialog return and mobile-source selection. It is a reusable column template, not coverage of every test here. Copy a row, replace its page/variant/view and test_condition with your actual case, and use observed_result for the actual focus sequence and closing action. Keep review_status pending until the actual check is performed.