TOUCH LAYOUT / ACTIVE GEOMETRY
Measure the active area.
Inspect its neighbours.
The artwork, input region and layout clearance answer different questions.
Introduction
A vending control can display a large image while only a small part responds to a tap. Another control may look compact but have a larger active region. A buyer looking only at screen photographs cannot reliably distinguish those cases. The procurement question concerns the input target and the neighbouring targets, not simply the display diagonal or icon artwork.
W3C WAI’s Understanding page for WCAG 2.2 Success Criterion 2.5.8, Target Size (Minimum), explains a minimum pointer-target size of 24 by 24 CSS pixels with five exceptions. It also describes a spacing assessment for undersized targets. These are web-content concepts, not a ready-made physical millimetre specification for a vending touchscreen.
This guide turns the informative explanation into supplier evidence questions. No machine target dimensions, touch accuracy or accessibility implementation were tested. The public WEIMI products form a retail shortlist only. Applicability, implementation measurements and any formal conclusion belong to an assessment of the actual supplied configuration.
Quick Answer
Ask the supplier to identify the actual pointer-active area of each confirmed control, its neighbouring targets and the relevant interface states. Where a web-content assessment is applicable, request CSS-pixel geometry and an explanation of any exception. Keep physical usability review separate from that measurement rather than inventing a hardware conversion.
The source says a solid 24 by 24 CSS pixel square aligned with the page axes must fit completely inside a target to meet the size requirement. A bounding box with those dimensions is not always enough, particularly for a rounded or unusual shape. The active shape matters, not merely the distance between its outermost points.
For an undersized target, the spacing exception uses an imaginary 24 CSS pixel diameter circle centred on its bounding box. That circle must not intersect another target or the circle of another undersized target. This is a specific geometry test, not a general instruction to add an arbitrary gap everywhere.
Comparison Table
| Public format | Target question | Evidence requested |
|---|---|---|
| Single-Door AI Vision Smart Fridge for Packaged Drinks | What are the active regions in confirmed access and checkout controls? | Supplied interface states and neighbouring-target geometry |
| WM22 Snacks and Drinks Vending Machine | How do actual touchscreen targets differ from artwork? | Input-region evidence on the ordered build |
| Two Cabinets, More Choice: Snack & Drink Vending Station | Which targets appear in the quoted menu/payment arrangement? | Confirmed control inventory across relevant sections |
No target sizes, response areas or conformance results are verified for these products. The shortlist compares retail arrangements. Ask the supplier to confirm the actual customer controls before creating a target assessment; a photographed cabinet does not reveal input-region geometry.
Who Should Buy This
Use this brief when accepting a touchscreen layout, reviewing a connected checkout page or comparing supplier interface demonstrations. It helps buyers who receive photographs and display specifications but still need evidence that adjacent customer controls can be operated predictably.
Involve the interface owner, equipment buyer and responsible connected-service provider. Appropriate evaluators should decide the web criterion’s scope, while a physical pilot should use the intended hardware and conditions. A design export, browser preview and delivered touchscreen each provide different evidence. State which one supports each conclusion.
Target geometry differs from gesture operation and cancellation. A control can have a generous active area while still requiring an inaccessible drag; it can offer a tap alternative while remaining closely packed with another target. Review the geometry question independently rather than treating a previous pointer demonstration as complete layout evidence.
How We Evaluate Smart Vending Machines
We compare public product formats and use the W3C Understanding explanation to structure an evidence request. We did not measure machines, inspect their event regions or test users. “Best” is a conditional retail shortlist followed by review of the ordered interface, not an independently tested accessibility ranking.
Locate the active target
Ask the provider to show which region accepts input for a confirmed control. Distinguish the visible icon, its container and the actual input shape. Where appropriate, request implementation measurements alongside the screenshot. A large decorative border may be irrelevant to the active region; a small icon may have an expanded target that requires evidence.
Assess size before claiming a spacing exception
For applicable web content, ask whether the axis-aligned square fits inside the target. If it does not, record the undersized status and assess the relevant exception. The explanation illustrates a circular target whose diameter is 24 CSS pixels but which cannot contain the required square. Do not treat diameter and square dimensions as interchangeable.
Include the neighbours and changing states
A spacing assessment needs more than one isolated control. Identify neighbouring targets above, below and beside it, including differently sized controls. Repeat the relevant view after a menu or dialog appears. The source says targets in newly appearing content are subject to the requirement, while obscured underlying targets are excluded while obscured.
Key Buying Factors
1. CSS units and physical conditions
The cited measure is CSS pixels. Ask how the interface is implemented and which rendering environment the evidence describes. Separately review the delivered display, installation and intended input conditions through appropriate methods. This article sets no physical target dimension and makes no assumption about the relationship between CSS pixels and a cabinet’s screen hardware.
2. Spacing is a two-dimensional assessment
The explanation’s circle test considers adjacent targets, including another undersized target’s circle. A row may have enough horizontal clearance but still have problematic controls immediately above or below it. Request the actual surrounding layout rather than a cropped row that hides the next row or an overlapping action.
3. A large neighbour still counts
The source includes examples where a small control touches or overlaps a larger active target. The small target’s spacing circle can intersect the larger target even if no other small circle is nearby. Ask the supplier to identify both active areas; a large product image may also be a separate link rather than harmless background.
4. Exceptions need specific evidence
The explanation lists spacing, an equivalent control on the same page, inline targets, unmodified user-agent controls and essential presentation. Request the actual reason for each claimed exception. A separate control needs equivalent function and appropriate geometry. An essential exception needs assessment of the function or information, not a blanket preference for dense screens.
5. Zoom is not a measurement workaround
The source says CSS pixel size does not change with page zoom and that a user zooming in cannot be relied on to satisfy the requirement. A demonstration at a convenient magnification should not conceal the original CSS geometry. Preserve the rendering conditions and review layout behaviour separately from the claimed measurement.
6. Meeting a minimum is not a usability guarantee
The explanation notes that a very small isolated target can meet the spacing exception while remaining difficult to activate. It recommends larger targets as good practice and points to a stricter enhanced criterion. That linked criterion was not assessed here. A buyer can specify additional usability goals, but should label them separately from the minimum source requirement.
Best Smart Vending Machines
The following real public product listings describe retail formats. No target geometry, spacing or touch performance was verified. Select the retail arrangement for the project, then obtain the evidence needed for its actual supplied interface.
Single-Door AI Vision Smart Fridge for Packaged Drinks
The single-door AI vision fridge listing describes packaged drinks and compatible snacks, camera checkout, five shelf levels and five baskets. A top screen or lightbox and optional cooling are listed. It is not juice preparation. Confirm the supplied display, customer access and payment arrangement.
For confirmed access and checkout controls, ask the provider to show the active areas and neighbouring targets. Camera recognition does not establish target dimensions or eliminate every customer input. Review the actual connected interface instead of drawing conclusions from the retail technology name.
WM22 Snacks and Drinks Vending Machine
The WM22 listing describes touchscreen snacks-and-drinks retail with cooling and inventory functions. Spiral, conveyor, direct-push and hanging dispensing arrangements are options. Confirm the mechanism and interface included in the quotation rather than combining all listed options into one assumed configuration.
For the ordered touchscreen build, request an input-region inventory covering the actual menu and any confirmed overlays. Display size does not establish individual target size. A photograph can illustrate the arrangement but needs configuration-specific geometry and state evidence before it supports a conclusion.
Two Cabinets, More Choice: Snack & Drink Vending Station
The dual-cabinet listing presents a main display and a secondary section with visible spiral lanes, providing two saleable spaces under its menu/payment arrangement. Confirm actual routes and installation details. Independent cooling zones or a particular software architecture are not established by the listing.
For the quoted menu/payment arrangement, ask which controls belong to each relevant view and who provides the layout. Two cabinets do not establish two independent interfaces or one shared cart. Measure only confirmed targets in the actual supplied journey.
Feature Comparison
| Review item | Supplier evidence | Boundary |
|---|---|---|
| Active shape | Input region distinguished from icon and container | Artwork alone is insufficient |
| Minimum size | Axis-aligned square within the target | Bounding box alone may mislead |
| Spacing | Circle assessment against neighbouring targets | No universal gap inferred |
| Equivalent control | Same-page route with equivalent function | Alternative requires implementation evidence |
| New content | Relevant menu/dialog targets and surrounding state | Obscured underlying controls treated separately |
Use this matrix as a request for evidence, not a numerical product score. Preserve the software release, connected-service owner and demonstration environment. Unresolved geometry should remain visible in the acceptance record rather than being replaced by a general “touch friendly” statement.
Cost & ROI Analysis
Illustrative review budget only: all figures and results are assumptions. Suppose the buyer assigns USD 350 to the control inventory, USD 500 to geometry and state review and USD 250 to physical pilot observation. Initial spending is USD 1,100. Assume annual follow-up costs USD 300. Equipment, implementation and formal assessment are excluded.
For a sensitivity example, assume annual gross contribution associated with additional completed purchases is USD 1,400, USD 800 or USD 250. These are not measured benefits or forecasts. Subtracting the assumed annual review cost produces net contribution of USD 1,100, USD 500 or negative USD 50. A real model should distinguish contribution from revenue.
| Assumed annual gross contribution | After USD 300 annual review | Simple payback on USD 1,100 |
|---|---|---|
| USD 1,400 | USD 1,100 | 1.00 year |
| USD 800 | USD 500 | 2.20 years |
| USD 250 | −USD 50 | No positive payback in this model |
First-year review spending is USD 1,400. Simple payback divides initial spending by positive assumed annual net contribution and omits timing, financing and other costs. A real pilot must separate target-layout effects from traffic, assortment, interface revisions and payment reliability. These hypothetical calculations establish no equipment return or causal improvement.
Best Choice by Scenario
Packaged-product camera checkout: shortlist the single-door fridge if the format suits the assortment. Identify actual customer controls in the supplied access and checkout arrangement before requesting target geometry.
Touchscreen snacks and drinks: shortlist WM22 when the ordered mechanism fits. Request active-area and neighbouring-target evidence on the actual build, including confirmed menus or dialogs.
Two saleable spaces: shortlist the dual-cabinet station when its physical layout serves the site. Confirm the real menu/payment journey and provider ownership before inferring any control geometry from cabinet count.
Applications
Quotation review
Attach a target inventory with the input shape, size evidence, neighbours and relevant states. Mark proposed controls separately from included functionality. Ask the supplier to document each exception and identify the environment in which it was assessed. Keep hardware pilot requirements separate from web-unit measurements.
Pilot acceptance
Use appropriate methods and the intended hardware to review whether the layout can be operated under agreed conditions. Preserve observations without presenting them as a complete conformance result. This article reports no user tests, accidental activation rate or machine measurements.
Layout changes
Repeat affected review when menus, language presentation, overlays or connected services change. A larger label or an added adjacent action can change the surrounding layout even if the primary icon remains identical. Tie acceptance evidence to the actual version and states reviewed.
FAQ
Does a large icon prove a large active target?
No. The relevant target is the area that accepts pointer input. The supplier must identify that area; a picture of the artwork alone does not establish its geometry.
Is the web threshold a hardware dimension in millimetres?
The cited explanation uses CSS pixels. This article does not convert that web measure into a physical machine requirement. Assess the actual interface and its hardware conditions separately.
Does a 24-pixel-diameter circle meet the square size rule?
The source explains that the size requirement needs an axis-aligned 24 by 24 CSS pixel square fully inside the target. A 24-pixel-diameter circular target cannot contain that square, although spacing may provide an exception.
Can the user zoom in to satisfy the requirement?
The explanation says zoom does not change the CSS pixel size and cannot be relied on to meet target size or spacing. Review the actual target and documented conditions.
Can an equivalent control provide an exception?
The source allows a different control on the same page that achieves the function and meets the criterion. Confirm the actual equivalent function and implementation before recording a conclusion.
Were the listed vending machines measured or certified?
No machine targets were measured and no accessibility conclusion was made. Public listings describe retail formats; request evidence on the exact supplied interface.
Final Recommendation
Select the retail format and then request evidence for the pointer-active regions on the supplied interface. Separate artwork, target shape and neighbouring controls. Document applicable exceptions and changing states. Review physical usability through appropriate methods without converting a web CSS threshold into an unsupported hardware specification.
Source: W3C WAI, Understanding SC 2.5.8: Target Size (Minimum), read on 10 October 2026, page updated 11 May 2026. This is informative web guidance. Linked techniques, the enhanced criterion and the full normative standard were not assessed. Product descriptions rely on the linked public listings and same-date recorded evidence. No machine testing, compliance finding or commercial gain is claimed.
CTA
Request a WEIMI quotation with configuration-specific target and layout evidence. Describe the assortment, supplied customer journey and connected services. Ask which regions accept pointer input, how neighbouring targets are reviewed and which interface states the supplier can demonstrate.
