Can shoppers read the product feature hidden behind a tiny hotspot?

Name the information behind the marker

For each hotspot, record the visible product part, the approved explanation and whether activation opens a panel or follows a link. “More” is not a useful merchant handoff when several dots do different things. Ask which question the shopper is answering, such as where a removable tray sits or how a latch is released.

W3C’s image-map tutorial distinguishes the image’s context from each hotspot’s action or destination, and discusses redundant text links for mobile coordinate problems. These principles guide a review; the theme owner should inspect the actual implementation rather than assume it uses an HTML image map.

Capture the information loss

In this fictional coffee-grinder page, a dot over the collection cup reveals “Lift the cup after grinding.” At narrow width, the marker drifts onto the base and the text disappears as the shopper moves toward it. The product photo is accurate, but the instructions depend on a fragile coordinate and a temporary interaction.

Ask for stable actions and explanations

Give the maintainer the feature map and request an operable named control for each action. Provide the same necessary information through a reachable feature list or ordinary description. If a popover remains, check keyboard and tap behavior as well as hover. W3C’s hover guidance describes predictable dismissal, persistence and pointer access for applicable temporary content.

Have the owner verify that marker placement still points to the correct part after responsive cropping. A detached callout can imply the wrong component even when its words are accurate. Do not move a marker onto an invented mechanism to fit the composition.

For the fictional cup callout, first identify whether it is temporary hover/focus content, a click-open panel or a modal dialog. For content covered by W3C’s hover/focus criterion, record whether the pointer can enter the added text without losing it, whether it remains while the relevant hover/focus persists, and whether it can be dismissed without relocating the pointer or keyboard focus when the dismissal requirement applies. Escape is one possible mechanism, not a universal prescription for every panel. W3C identifies exceptions to dismissal and excludes modal dialogs from this criterion.

Write two rows for the same approved instruction: “collection-cup marker → cup-removal explanation” and “visible feature-list entry → same explanation.” Compare the actual wording, selected variant and destination after responsive cropping. A label for the adjustment ring must not open the cup instruction. Use the gallery control-name review for a control that changes views rather than opens feature guidance.

Test the answer without the image coordinate

Ask a reviewer to find the cup-removal instruction without using the hotspot, then inspect the marker route separately. Compare both answers and destinations. Check narrow layout, keyboard focus and the selected variant; a feature absent from that variant should not remain confidently described.

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 detail photos and draft feature wording for review. It does not add hotspot controls or verify physical operation. Store interaction changes and instruction approval remain separate responsibilities.

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.