Introduction

An interface shows a useful explanation when the pointer reaches an information icon. The user moves toward the explanation to read the final line, and it closes. Another version stays open but covers the action beneath it; moving away to clear the popup also moves the user’s place in the interface. Both experiences require a different procurement observation from whether the popup appears.

W3C WAI’s Understanding explanation for WCAG 2.2 Success Criterion 1.4.13, Content on Hover or Focus, addresses additional content that becomes visible and hidden with receiving and removing pointer hover or keyboard focus. It describes three conditions: dismissible, hoverable and persistent. The scope includes custom tooltips, submenus and other nonmodal popups of that kind, with specified exceptions and boundaries.

This article uses those web-content concepts to specify evidence for a quoted interface. It does not certify an entire vending machine, imply that a touchscreen has pointer hover, or establish a universal legal obligation. The public WEIMI pages below verify physical-format candidates; their installed popup behavior, input support and customer software remain untested here.

Quick Answer

Follow the temporary content from its trigger to its end. For author-controlled additional content in scope, demonstrate an appropriate way to dismiss it without moving hover or keyboard focus, move the pointer from the trigger onto the additional content where hover triggers it, and observe that it remains visible under the specified persistence conditions. Record applicable exemptions rather than assuming every popup has identical requirements.

Treat touch, pointer and keyboard journeys separately. A tap-activated dialog does not automatically belong to this hover/focus criterion, and a pointer tooltip does not establish a usable touch route. Identify how the actual ordered interface presents the same information to its intended users before accepting a general “tooltip support” statement.

Comparison Table

This is a manufacturer-listing procurement shortlist, not an independent test or ranking of tooltip performance. The pages do not establish that these products implement custom hover content, support keyboard input or satisfy the proposed requirements. Those are questions for a configuration-specific demonstration.

Who Should Buy This

Use this framework when a proposed web interface or operator portal includes temporary explanations, submenu content or other nonmodal additions tied to hover or focus. It is particularly relevant if the addition overlaps existing content or is large enough that a user must move the pointer to inspect it. A short explanation can still require control over its appearance.

It also helps buyers separating a customer touchscreen from a companion browser journey. The machine may use taps while staff view a pointer-driven portal on a workstation. Do not transfer a result from one environment to the other. Record which interface, input method, software version and content the acceptance exercise covers.

If the project has no content triggered in the criterion’s way, do not invent a popup feature to make the checklist relevant. A clearly activated persistent information panel may be a more predictable design option. The source recommends considering more predictable ways to add content, but it does not require a specific alternative layout for every project.

How We Evaluate Smart Vending Machines

We reviewed three WEIMI public product pages on 10 October 2026 and read W3C’s SC 1.4.13 explanation and failure technique F95. We did not run pointer or keyboard trials on the installed machines, inspect their software, or measure user outcomes. The article offers a supplier evidence plan supported by public sources rather than reporting completed equipment tests.

Start with a trigger inventory. Ask the supplier to classify each relevant addition as author-controlled or user-agent-controlled, modal or nonmodal, and hover/focus-triggered or explicitly activated. Record which original content it covers. This scope record prevents a dismissal requirement from being applied indiscriminately to every message and dialog.

For a custom hover-triggered addition, open it and move the pointer toward and onto the content. Observe whether it disappears or is replaced by a neighboring trigger. F95 describes both the simple disappearing popup and chart popups replaced while moving toward them. Keep the intended content visible along the actual travel path rather than testing only a stationary pointer.

For the applicable dismissal condition, use the offered mechanism while retaining the trigger’s hover or focus. Then observe persistence without dismissing or removing the trigger. Where keyboard focus is supported and relevant, test its route separately. Record the displayed information, whether it remains valid and the actual event that hides it.

Key Buying Factors

Dismissal without relocation. The source explains why moving the pointer or focus merely to clear content can disrupt the original task, especially under magnification. Escape is an example mechanism, not the only possible one. Ask the supplier to demonstrate the offered method while the user’s trigger position remains unchanged.

Dismissal exemptions. The dismissible condition has exemptions for additional content communicating an input error or not obscuring or replacing other content. These do not erase every other applicable condition. Record the actual error function or lack of meaningful overlap before relying on an exemption. A popup that covers its own trigger or a nearby action cannot be described as harmless whitespace without evidence.

Pointer travel. If hover can reveal the additional content, the pointer must be able to move onto it without making it disappear. F95 highlights that a magnified view may not initially contain the whole popup. A large pointer can also cover part of the explanation. This is about retaining content during movement, not automatically turning every tooltip into an interactive menu.

Persistence with defined endings. The source allows the addition to end when the hover/focus trigger is removed, the user dismisses it, or its information is no longer valid. An arbitrary reading timeout is not the same as invalid information. Document the hiding event and avoid making an unsupported claim that a fixed number of seconds is sufficient for all users.

Author and browser boundaries. The criterion has an exception where the visual presentation is controlled by the user agent and not modified by the author, such as a native title-attribute tooltip. A custom styled popup is a different case. The explanation also places modal dialogs outside this criterion, and a hidden component itself becoming visible on focus is not additional content in its sense.

Information access across inputs. The explanation refers to keyboard accessibility for content revealed by pointer hover. That wider check should remain visible in the project scope rather than being inferred from successful pointer travel. For touch-only deployment, identify the actual information-access route without claiming that a tap test establishes hover conformance.

Best Smart Vending Machines

These three real listings are candidates for matching physical formats. Their software input paths and temporary-content behavior require separate confirmation. No product is a tested winner for dismissible, hoverable or persistent content.

Feature Comparison

Use the matrix for each offered temporary addition. Preserve unresolved conditions in the quote. A passing observation for one tooltip does not establish every submenu, neighboring trigger or responsive presentation in the interface.

Cost & ROI Analysis

Ask for incremental quote items covering trigger classification, interaction adjustment, content review and regression checks. An alternative persistent presentation may have a different scope from custom tooltip work. Public product pages do not establish a standard implementation fee or included software support.

Hypothetical calculation only: assume initial interaction review and correction costs US$1,340, with US$260 in annual checks. First-year incremental cost is US$1,600. Suppose separately that a pilot measures annual avoided support and rework effort worth US$1,100, US$1,900 or US$2,700. These are illustrative assumptions, not WEIMI pricing, measured savings or sales forecasts.

ROI is net benefit divided by the assumed first-year cost. The model excludes equipment, payment charges and revenue effects. Replace assumptions with measured pilot effort and avoid counting one support event under several interface changes. Retest when popup placement, content length or neighboring triggers change.

Best Choice by Scenario

For camera-checkout packaged retail, investigate the fridge format and confirm the actual digital instruction path. For touchscreen snack-and-drink selection, investigate WM22 and distinguish tap content from any quoted hover/focus journey. For two selling areas, investigate the dual-cabinet format and inspect additions that explain physical references.

When temporary-content behavior is decisive, choose based on a demonstrated interaction in the intended environment. Screen size and cabinet count do not settle the issue. If no candidate offers the necessary evidence, leave the requirement open and request a scoped software proposal before selecting on that basis.

Applications

An operator portal may reveal short explanations on focus or hover. A companion product journey may use custom popups beside a selection. A two-area interface may show an extra cabinet explanation. These are hypothetical procurement applications, not customer case studies or evidence that the listed machines implement such features.

A pilot can identify a small set of representative triggers, including additions near other triggers and content long enough to require pointer travel. Record scope, overlap, dismissal, persistence and the supported input path. Use approved demonstrations and avoid turning a browser-native tooltip or modal task into a misleading failure report under this specific criterion.

FAQ

Final Recommendation

Specify the entire lifetime of the offered additional content. Classify its trigger and owner, inspect overlap, demonstrate appropriate dismissal, move the pointer into hover-triggered content and record the event that ends its visibility. Preserve exemptions and boundaries so the acceptance result remains precise.

Use the WEIMI public listings to investigate matching formats, then ask for the actual software demonstration. None has a verified temporary-content advantage in this article. Keep pointer, keyboard and touch observations separate and assign regression responsibility when wording or placement changes.

Sources checked 10 October 2026: W3C Understanding SC 1.4.13; F95, hover content not hoverable; and the three manufacturer pages linked above. Understanding guidance is informative and techniques are examples. This is procurement guidance, not legal advice, independent testing or whole-machine certification.

CTA

Request a WEIMI quotation with additional-content behavior defined. Include the equipment format, intended input devices, representative explanations and customer or operator interface scope. Ask for a trigger-based demonstration and a priced regression plan before treating popup capabilities as included.