Introduction

A product label fits at the default font size. A user increases the space between letters and words, and the last part of the label slips behind a fixed panel. The font did not grow, yet the content became unavailable. Text spacing is a separate procurement question from a larger-text control or a high-contrast colour theme.

W3C WAI’s Understanding explanation for WCAG 2.2 Success Criterion 1.4.12, Text Spacing, addresses markup content that supports the specified text style properties. It requires no loss of content or functionality when all applicable spacing properties are set to the specified metrics and no other style property is changed. The explanation explicitly says these values are not mandatory default styling, and the content need not provide its own adjustment mechanism.

This article uses the public web guidance to define a configuration-specific evidence request. It does not certify an entire vending machine or establish a universal legal obligation. The WEIMI pages below verify candidate equipment formats, but they do not establish the deployed interface technology, spacing adaptability or a built-in typography control.

Quick Answer

Keep font size unchanged and demonstrate the applicable spacing overrides together. The specified metrics are line height of at least 1.5 times font size, spacing following paragraphs of at least 2 times font size, letter spacing of at least 0.12 times font size and word spacing of at least 0.16 times font size. Inspect complete content and required actions after applying the applicable properties without changing other styles.

Confirm first that the technology and language/script combination are in scope. An override tool that fails to apply a property is not itself proof that the content failed. Record both whether the settings actually took effect and whether the resulting content remained available. Do not replace this exercise with a screenshot of enlarged text.

Comparison Table

This is a public-listing purchasing shortlist, not an independent test or measured accessibility ranking. No cited product page establishes that its interface uses adaptable markup, offers a text-spacing control or passes the proposed exercise. Those claims require separate demonstration.

Who Should Buy This

Use this procedure when approving a markup-based interface or companion web journey that supports the relevant text style properties. Product cards, menus, instructions and short action labels can all encounter layout constraints. Long descriptions may wrap differently while short navigation labels exceed fixed widths. The buying team should identify the content and software boundary before asking for an override test.

It also helps buyers who have already tested text enlargement. A successful enlargement route does not establish spacing adaptability at unchanged font size. Conversely, a spacing result does not prove that users can double the text size. Keep the observations separate so each requirement has evidence rather than one general “readable interface” sign-off.

For multilingual projects, determine which properties are used by each language and script. The criterion includes an exception for properties not used in a particular combination. That is a targeted scope decision, not permission to omit all checks for a non-English interface. Request language-specific review where needed and avoid assuming that English test content represents every ordered translation.

How We Evaluate Smart Vending Machines

We reviewed the three WEIMI manufacturer pages on 10 October 2026 and read W3C’s Text Spacing explanation and C36. We did not run spacing overrides on the installed machines, inspect their software code or measure customer outcomes. Our method provides a supplier demonstration plan based on public evidence, rather than a completed product test.

Record the software version, interface technology, language/script, layout variation and representative content. Ask the supplier to identify an authorised demonstration environment and a suitable way to apply the relevant properties. C36 begins its test at 100% zoom. Keep font size and unrelated styling unchanged to avoid confusing the result with another adaptation.

Confirm the override took effect. Then inspect the full product label, instructions, notices, input text where applicable and action labels. Follow the relevant task to identify controls that become obscured or separated from their content. Save both the applied values and the observed availability; a screenshot alone may not show whether an override was applied correctly.

C36 notes that multiple layouts, such as responsive variations, should each be tested. Repeat the evidence exercise in the layouts included in the specification. At the end restore the normal demonstration presentation. Keep any unavailable testing scope open in the procurement record instead of reporting an unobserved result as passed.

Key Buying Factors

Adaptability, not a prescribed default. The Understanding explanation says authors need not set their content to these metrics or supply their own mechanism. The requirement concerns surviving a user override without lost content or functionality. A supplier should not answer this request merely by changing the default design to a preferred line-height value.

All applicable properties together. A line-spacing test alone misses the additional width created by word and letter spacing and the vertical space after paragraphs. Record the combined applicable values. If authored spacing already exceeds a baseline, assess the actual effect instead of assuming the settings always increase every value.

Container capacity. C36 explains that text containers need room for expansion or the ability to expand. For horizontally read text, paragraphs may need more vertical room; other writing directions can require different expansion. Its example of avoiding a fixed paragraph height is one approach, not evidence that every fixed-size container necessarily fails.

Full content behind an ellipsis. The Understanding explanation allows a resulting ellipsis when full content is still available through a mechanism such as focus, activation or an appropriate linked page. Demonstrate that route. An ellipsis that simply removes the end of a product name without a way to obtain it does not establish retained content.

Technology boundaries. The source identifies applicability to markup technologies that support the specified properties and distinguishes images of text, canvas text and embedded captions from text expected to adapt. It also says the criterion does not require the platform itself to provide a user adjustment method. Record the boundary carefully without using it as an excuse to make unsupported whole-interface claims.

Tool versus content failure. A bookmarklet, stylesheet, extension or application may fail to set a property correctly. The explanation says that is not a content failure by itself, provided the content is not actively and purposely preventing the properties from being added. Obtain evidence of application and observation before assigning responsibility.

Best Smart Vending Machines

These three real listings can start a format-based procurement discussion. Their typography suitability depends on the separately quoted software. “Best” describes candidates for matching scenarios, not a measured winner for user-defined spacing.

Feature Comparison

Keep the evidence tied to the quoted content and configuration. A responsive claim cannot replace checks of actual presentations. A change to product names, instruction length or layout constraints can affect spacing behavior even when the hardware stays identical.

Cost & ROI Analysis

Obtain incremental quotes for technology scoping, representative-content review, override testing, layout correction and future regression checks. The public listings do not establish a universal charge for typography work. Keep machine purchase and other software integration costs separate so that the buyer can review the specific scope.

Hypothetical illustration, not pricing or measured savings: assume initial review and layout work costs US$1,260 and annual regression checks cost US$340. First-year incremental cost is US$1,600. Suppose a pilot separately records annual avoided support or rework effort worth US$1,000, US$1,800 or US$2,600. These values are calculation assumptions only.

The model subtracts cost from benefit and divides the net by US$1,600. It excludes equipment, payment fees and revenue changes. Replace assumptions with measured pilot effort and do not count the same avoided support time under both spacing and another interface improvement. Frequent content or language changes may require ongoing review beyond the first year.

Best Choice by Scenario

For packaged-product camera checkout, investigate the fridge format and determine whether the customer text is an applicable screen or companion journey. For touchscreen snack-and-drink selection, investigate WM22 with the ordered delivery arrangement and language content. For two selling areas, investigate the dual-cabinet format and preserve the displayed physical references in the task.

When user spacing adaptability is decisive, prefer a proposal that demonstrates the actual override, full-content availability and functional path in scope. A larger screen or longer default line spacing is not automatically a superior solution. If none provides evidence, retain the requirement as unresolved and request a scoped review before selecting on this basis.

Applications

A service with detailed product wording may need descriptions that expand when spacing changes. A companion web journey may need complete labels across responsive presentations. A multilingual rollout may need a property-by-property scope decision for each script. These are hypothetical applications, not reported customer installations or proof of installed WEIMI software capabilities.

A pilot can use an approved content set and a short task script: apply the relevant combined override, read the whole label, obtain any truncated full content, inspect instructions and complete the required action. Record a failure separately from a tool that did not apply the settings. Restore the presentation after recording the result.

FAQ

Final Recommendation

Specify a spacing-adaptability observation rather than a default styling preference. Establish the technology and language scope, apply the relevant metrics together, confirm they took effect and inspect complete content and task functionality. Keep full-content access and responsive variations in the record.

Use the three WEIMI public formats as equipment candidates, then obtain the exact software evidence. None has a verified spacing advantage here. Agree who retests after wording or layout changes, and preserve unresolved boundaries in the quotation. A successful override test is a scoped observation, not a machine-wide accessibility certificate.

Sources checked 10 October 2026: W3C Understanding SC 1.4.12; C36, allowing text spacing override; and the three manufacturer pages linked above. Understanding guidance is informative and techniques are examples. This article offers procurement guidance, not legal advice, independent testing or verified conformance.

CTA

Request a WEIMI quotation with adaptable text in scope. Include the equipment format, intended language/script, representative content and interface environment. Ask for an agreed spacing-override demonstration and a priced content-regression responsibility before treating typography adaptability as included.