Can shoppers inspect a product detail without using two fingers to zoom?

Separate custom magnification from browser behavior

Ask the theme owner whether the pinch action is interpreted by the store’s image viewer or by the browser. This guide concerns author-created media interactions. Browser page zoom should remain available, but it may not expose the same image-inspection controls or source detail as a custom viewer.

W3C’s pointer-gesture guidance describes single-pointer alternatives to multipoint actions, with browser-controlled behavior outside that requirement’s scope. Do not declare every native phone pinch a theme defect. Identify the custom action and what the shopper must accomplish without it.

Define the detail and its reachable route

In this fictional jacket gallery, a custom pinch enlarges the zipper pull, but the shopper cannot trigger that enlargement with one tap. After zooming, the pull is outside the visible center. Adding a plus button alone would leave the shopper unable to inspect it. The review needs magnification, movement to the detail and reset, not merely an icon.

Request equivalent inspection, not invented sharpness

Ask the maintainer to provide operable controls or an approved detailed-view route that lets a single pointer reach the needed information. If custom panning also requires dragging, review its non-dragging alternative separately. Keyboard support is another necessary interaction check; it should not be assumed from the presence of tap buttons.

Use controls that remain reachable at the enlarged state. Do not imply that a higher zoom level reveals verified construction absent from the original photo. A trustworthy macro reference may be needed when the zipper itself has insufficient detail.

Complete the one-pointer inspection exercise

On the intended touch device, keep to one finger and inspect the zipper pull, a detail near another edge and the complete jacket. Record which control produced each result. Repeat the keyboard route and normal browser zoom after any repair. Confirm that the custom viewer does not consume page gestures in a way that blocks the surrounding purchase task.

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 reviewed macro assets from sufficient references. It does not install magnification controls or validate your external viewer. Retain a separate focus-return test for entering and leaving the enlargement; this exercise concerns operation inside it.

Use three independent rows in the manual record: enlarge the approved view; reach the off-center zipper pull without a pinch or drag; return to the overview. Record the actual control or alternate detail view, its observed result and pending action. A working Zoom in button with an unreachable edge is a partial failure, not a completed inspection. A reachable but blurred pull can be an evidence-resolution problem even when the controls operate correctly.

For this exercise the reviewer uses the supported single-pointer route, then separately checks the keyboard route and touch assistive technology. Browser-provided page gestures are a separate scope. W3C’s pointer-gesture guidance explains the author-controlled multipoint/path-based requirement; dragging alternatives require their own review. This small task list is not a complete WCAG conformance assessment.

Use page zoom and purchase-form reflow for the surrounding page, and comparison-divider routes for changing how much of two images is revealed. Do not combine those outcomes into one “zoom works” checkbox.

The downloadable gallery worksheet currently contains two fictional, pending sample rows, for dialog focus return and mobile source selection. Copy its nine-column format and add rows for this article’s actual test steps; neither existing row records these checks for your store. Keep observed results and pending actions distinct. Downloading it does not run a test.