Introduction

A control called “Search” appears on one page, while a recurring version of the same function is called “Find” on another. A save action keeps its software-exposed name but changes to an unrelated icon. These differences can make a familiar action look like a new decision, even where the underlying result has not changed.

W3C WAI’s Understanding explanation for WCAG 2.2 Success Criterion 3.2.4, Consistent Identification, addresses components with the same functionality within a set of web pages. Its emphasis is recognition of recurring functions. The page explains that consistent does not always mean identical, and that context-appropriate differences can preserve the relationship. This article uses that informative guidance for procurement questions, not to certify a vending machine or determine a jurisdiction’s legal requirements.

Three real WEIMI public listings form the retail shortlist. No labels, computed names, icon alternatives or responsive interfaces were tested on those machines. The proposed review applies to the confirmed supplied customer interface and any agreed connected page set. Appropriate evaluators must establish scope and evidence for the actual release.

Quick Answer

Ask the provider to group recurring components by the result they produce, define the relevant page set, and compare how customers identify them. Record visible labels, software-exposed names, text alternatives and icons where those mechanisms apply. A screenshot from a single page cannot establish consistency across recurring instances.

Do not require one universal string for every control that reaches a similar destination. The Understanding page distinguishes repeated instances of a component from unrelated links that happen to let users contact the same organisation. It also distinguishes same results from different results behind similar artwork. Start with functionality and recurrence rather than a word-matching exercise.

Keep context in the assessment. A destination identified as “Page 4” can become “Previous page” when viewed from page 5. A responsive search control can use text in one presentation and a named icon in another. Those examples show why recognition evidence is more useful than insisting on identical visual presentation everywhere.

Comparison Table

This is a public-listing procurement shortlist, not an independently tested accessibility ranking. Equipment format does not establish a repeated control, page-set boundary or consistent identification. Ask the supplier to confirm the software journey before using these rows as acceptance tasks.

Who Should Buy This

Use this brief when different teams supply customer screens, a component library changes, or branding work replaces familiar action icons. It is useful where purchase acceptance currently checks only that controls work. Functionality can continue working while its identification becomes unfamiliar across repeated uses.

Include the commercial buyer, interface owner, copy owner and appropriate evaluator. For connected steps, identify who supplies each recurring component and who can change its label, icon or name. Review responsibility with the configured route, not merely the cabinet manufacturer’s name.

The intent differs from label-in-name matching. A control can contain its visible text in its accessible name and still be identified differently from repeated controls with the same function. It also differs from consistent help placement and navigation ordering. These issues can overlap in a project, but each needs its own observed evidence.

How We Evaluate Smart Vending Machines

Our method uses the W3C Understanding explanation read on 10 October 2026, alongside same-date public product evidence. No independent machine tests or user studies were performed. The steps below are a proposed procurement process, and “best” denotes conditional retail fit rather than verified interface superiority.

Establish the result before forming a group

The source defines same functionality as the same result when used. Ask the provider to describe the action and resulting state or destination. Two similar printer icons may produce a receipt and an invoice, which the source treats as different functionality. Do not assume sameness from appearance or a shared short verb.

Identify recurring instances in the agreed set

Record which components repeat and on which pages or states they appear. The source discusses recurring navigation links, search controls, account controls and footer links as examples. Its explanation also addresses repeated components within a page. Use that distinction to avoid grouping every unrelated link solely because it produces a broadly similar outcome.

Compare the means of identification

For each recurring group, collect the visible presentation and applicable software-exposed identification. The source names visible labels, accessible names, text alternatives and icons as possible mechanisms without requiring one particular mechanism. Ask the evaluator whether users can recognise the same functionality, including any changes justified by the current context.

Retain the assessed differences

Where wording or presentation varies, record the context and reasoning instead of hiding the difference in a general approval statement. A language version, responsive view or connected purchase step may need separate scope analysis. Keep the release and provider with the comparison so that later changes can be assessed against the same basis.

Key Buying Factors

Define the page set explicitly

The source describes a set as pages with a common purpose created by the same author, group or organisation. Its examples show that a checkout process with a different template can be distinct from product pages, and it notes that different language versions are different sets. Do not treat every domain, screen or provider in the project as one set without evaluation.

Consistent identification can reflect context

The explanation encourages identical identification where it helps recognition, but does not demand it in every case. Page destinations are one example: naming a specific next page changes as the sequence progresses. Request a function-and-context record that shows why wording varies and how the repeated action remains recognisable.

Visible sameness can hide naming differences

One published failure example uses two visible “Search” labels with different accessible names, “Search” and “Find”. A visual-only check would miss the inconsistent announcement. This article did not inspect actual computed names; request suitable evidence from the delivered environment and treat screenshots as only one part of it.

Matching names can hide icon differences

Another published failure example changes a save icon from a floppy disk to a checkmark while retaining the name “Save”. The source describes a recognition problem for people relying on visual identification. Avoid accepting a shared name as proof that all customers encounter a consistent identity.

One image can serve different functions

The source explains that a checkmark can mean approved, completed or included depending on context, and that different text alternatives can be needed. Do not impose “check mark” everywhere as a naming policy. The function matters more than describing the shape, and different results should be assessed separately.

Responsive differences need evidence

The source’s responsive example uses the visible word “Search” on a large viewport and a magnifying-glass icon with the accessible name “Search” on a small viewport. It illustrates consistent recognition despite different presentation. It does not prove that a vending product has responsive software or that any icon substitution is automatically acceptable.

Best Smart Vending Machines

Choose the physical retail arrangement around actual packs, storage and site constraints. Then commission the identification review for the quoted software. These three products are genuine public-listed candidates; none has been independently tested for repeated-control consistency.

Feature Comparison

This matrix requests evidence rather than claiming features are included. Complete it for the actual configured interface. A supplier’s brand guide may support artwork decisions, but it does not establish the result produced by a control or what supported software announces.

Cost & ROI Analysis

These USD figures are hypothetical review assumptions, not prices or measured savings. Assume $1,200 initially: $400 to inventory recurring functions, $500 to review their identification and $300 to document decisions. Assume $300 each year for relevant release checks. First-year expenditure would be $1,500.

Annual net value is gross avoided support or correction work minus annual review cost. Simple recovery divides initial expenditure by positive net value. The negative case has no positive recovery calculation. The model excludes finance, discounting, tax and inflation and does not forecast vending transactions or customer conversion.

Use documented rework and support records to replace the gross assumption. Do not attribute all customer confusion to inconsistent identification or count one correction as both engineering savings and avoided support. If no relevant records exist, retain the model as a budgeting scenario rather than presenting it as an operational result.

Keep equipment economics separate. Obtain actual hardware, freight, installation, payment, software, stock, energy and service quotations. A favourable interface-review scenario cannot establish machine profitability or justify treating unverified software changes as included in the order.

Best Choice by Scenario

Branding replaces a familiar action icon

Compare the result and repeat instances before approving the new artwork. For a WM22 project, review the ordered touchscreen release rather than relying on a large display image. Preserve naming evidence alongside visual identification so that one channel is not changed without considering the other.

A connected purchase route adds recurring controls

Define the appropriate set and provider scope before comparing components. An AI-fridge project may use a confirmed connected access or checkout arrangement, but the listing does not establish that route’s repeated functions. Ask the provider to identify them rather than inventing interface states for the cabinet.

Two selling areas form one retail destination

The dual-cabinet station is a conditional option for a compatible mixed assortment. Confirm how its actual menu addresses each selling space, then assess recurring functionality in the agreed software scope. Do not infer common names, shared sessions or identical operations from the two-cabinet appearance.

Applications

Use the brief during component-library changes, copy review and provider acceptance. A function inventory allows artwork and language teams to discuss the same recurring operation instead of comparing isolated screenshots. Record the result as well as the name so that a renamed function does not quietly become a different action.

For release regression, revisit affected recurring groups after an icon, label or connected view changes. Preserve context-appropriate exceptions with the evaluator’s reasoning. A passing comparison from another release is evidence of that release only, not proof that a later component remains recognisable.

When investigating a reported difficulty, separate a customer’s description from a verified cause. A customer asking “is this the same action?” can guide review, but does not alone establish a naming failure. Reproduce the relevant route and assess the actual identification before assigning corrective work.

FAQ

Final Recommendation

Shortlist the cabinet format that fits the merchandise and service plan, then require evidence for recurring functions in the supplied interface. Begin with the result and page set, compare the relevant identification mechanisms, and retain reasoning for legitimate contextual differences. A universal string rule would miss both scope and recognition.

The W3C explanation is a research reference, not proof of machine conformance, supported assistive software or commercial performance. No customer case or measured result is claimed here. Accept what was evaluated for the agreed release and leave unresolved provider evidence visible in the purchasing record.

Source: W3C Understanding SC 3.2.4 Consistent Identification, updated 6 September 2026; read 10 October 2026. Product links use public listing evidence checked on the same date. Linked techniques and separate conformance requirements were not independently evaluated.

CTA

Send WEIMI your destination, quantity, intended products, package dimensions and site requirements. Include the customer interface scope, preferred payments and the recurring functions you need reviewed. Request an itemised quotation with the final hardware and software responsibilities.

Agree the available identification evidence before treating control names, icon behaviour or connected-interface evaluation as included in the purchase.