LAYERED INTERFACES / CURRENT INTERACTION
A layer appears.
Keep the interaction visible.
Follow the focused component through the supplied journey and its changing layers.
Introduction
A banner or side panel can occupy part of a customer screen without stopping navigation behind it. If keyboard focus moves to a control covered by that layer, a sighted customer relying on keyboard input may lose the visible point of interaction. The supplier demonstration needs to follow focus through the layered state, not merely show that the panel opens.
W3C WAI’s Understanding page for WCAG 2.2 Success Criterion 2.4.11, Focus Not Obscured (Minimum), explains that a component receiving keyboard focus is not entirely hidden by author-created content. The minimum permits partial obscuring, while separate notes address user-movable and user-opened content. These distinctions make the evidence request more precise.
This guide uses informative web guidance to frame procurement questions. No WEIMI machine was tested for keyboard support, focus movement or overlays. The public listings below establish retail formats. Confirm the supplied interface architecture, input arrangement and applicability before recording any acceptance or accessibility conclusion.
Quick Answer
Ask the provider to demonstrate the confirmed keyboard journey with each relevant layer present and show the component that receives focus. Classify whether a layer is automatic, pre-positioned, user-opened or user-movable. Preserve those distinctions in the evidence rather than treating every overlay as the same case.
The explanation gives sticky headers, sticky footers and non-modal dialogs as typical overlapping content. It evaluates the component, rather than an external focus outline, for this criterion. A visible fragment of an outline does not necessarily establish that the component itself is visible; a partly visible component does not establish every other focus or contrast requirement.
For user-opened persistent content, request the actual way to reveal the focused component without advancing focus. The source discusses dismissal or scrolling routes under that note. Do not apply it indiscriminately to automatic warnings or pre-positioned sticky content, which must not prevent immediate visibility of the component receiving focus.
Comparison Table
| Public format | Layered-state question | Evidence requested |
|---|---|---|
| Single-Door AI Vision Smart Fridge for Packaged Drinks | Which confirmed access/checkout layers overlap customer controls? | Supported input arrangement and focus sequence |
| WM22 Snacks and Drinks Vending Machine | Where does focus move with the supplied touchscreen panels open? | Actual overlay states and visible component evidence |
| Two Cabinets, More Choice: Snack & Drink Vending Station | Which provider controls layers in the quoted menu/payment journey? | Confirmed layer inventory and responsible owner |
This is a shortlist based on public product listings. It does not establish a physical keyboard, a chat panel, a sticky banner or accessibility conformance on any machine. The questions apply only after the supplier confirms the relevant interface features and supported environment.
Who Should Buy This
Use this brief when accepting a layered interface, integrating a customer service panel or approving a release that adds persistent screen content. It is relevant where the ordered customer journey includes a keyboard interface or another supported input arrangement that operates through it.
Include the equipment buyer, interface owner and provider of any connected pages. If the project has accessibility requirements, involve appropriate evaluators and intended users. Ask which hardware and software configuration supports the demonstration. A browser preview can illustrate a problem but does not prove keyboard operation on a delivered cabinet.
This review is about visibility of the component that receives focus. It differs from providing a keyboard exit from a dialog, defining a focus outline or ensuring tap-target geometry. Those matters may interact, but a working close button does not show what happens when focus moves behind a panel that remains open.
How We Evaluate Smart Vending Machines
We compare public equipment formats and use the W3C Understanding explanation to define a supplier evidence request. No machine interface, keyboard or assistive technology testing was performed. “Best” means conditional retail fit followed by review of the supplied implementation, not a tested accessibility ranking.
Inventory the layer and its trigger
Record only confirmed layers, their provider and how they appear. Separate a fixed header from a user-opened panel and an automatic notification. Note whether the user can reposition a region. The source assigns different boundaries to these patterns, so a generic “overlay supported” statement leaves important evidence unresolved.
Trace the receiving component
Ask the provider to navigate through the relevant state and identify each component that receives focus. Observe its position in the viewport and whether author-created content hides it completely. The requirement is about the focused component; an external indicator belongs to a related but distinct review.
Preserve the tested conditions
Record software release, viewport, layout state and supported input arrangement. Include relevant responsive states and connected-provider content where supplied. Do not turn a single uncluttered screenshot into evidence for a journey with panels, notifications or changing layout. This is a proposed review method rather than a report of tests performed.
Key Buying Factors
1. Minimum versus preferred visibility
The cited minimum allows the receiving component to be partly obscured. The explanation recommends reducing the degree and frequency of overlap and refers to an enhanced criterion for no obscuring. That linked criterion was not assessed here. A buyer may request full visibility as an additional project goal, but should not describe it as the exact minimum requirement.
2. Component and indicator are different evidence
The source explains that the component does not include an external focus indicator for the entirely-hidden assessment, unless focus is indicated inside or by a change to the component itself. It also notes related focus visibility and contrast issues. Keep those observations separate rather than declaring the entire interface satisfactory from one visible outline.
3. Automatic and fixed layers
A system warning or pre-positioned sticky layer does not become user-opened content merely because the customer performed an earlier purchase action. Ask the provider to classify the trigger and show immediate visibility when focus arrives. The source’s user-opened note is limited to content the user actively discloses.
4. Reveal without advancing focus
For a confirmed user-opened persistent panel, ask whether the current focused component can be revealed without moving to another focus stop. The explanation gives examples involving Escape, scrolling and overlay switching. These are examples of possible mechanisms, not a requirement that every product use one particular key or proof that any listed machine supports it.
5. Initial position of movable regions
The explanation assesses the initial positions of user-movable content for this criterion. Record those positions and distinguish them from a panel moved later by the user. A buyer may still review likely practical arrangements, but should identify that additional work separately from the stated conformance boundary.
6. A modal label is not enough
The source describes a properly constructed modal as taking focus when it appears and maintaining interaction inside until dismissal. A dialog-like overlay that does not take focus or allows navigation behind it can still obscure receiving components. Request behaviour evidence rather than accepting a screenshot labelled “modal”.
Best Smart Vending Machines
These three real public-listed products describe retail arrangements. Their keyboard support, layers and focus behaviour are unverified. Use the physical format to shortlist equipment, then require evidence for the interface actually included in the quotation.
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 packaged-product retail rather than juice preparation. Confirm the supplied display, access and payment setup.
For confirmed access and checkout pages, ask which layers appear and which provider controls their focus behaviour. Camera checkout does not establish keyboard support or component visibility. Review the actual connected sequence and supported input environment.
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 mechanisms are options. Confirm the ordered dispensing configuration and interface rather than assuming every listed option is present.
For the supplied touchscreen software, request evidence with confirmed panels and notifications present. A touchscreen specification does not establish a keyboard interface, nor does screen size prove that focused controls remain visible. The supplier should identify the exact demonstration build.
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 the menu/payment arrangement. Confirm routes and installation details. Independent cooling zones and a specific software architecture were not established.
For the quoted menu/payment arrangement, identify relevant layered views and their owners. Two cabinets do not establish separate focus journeys or one shared software system. Evaluate only the actual confirmed interface without inventing a shared cart or customer panel.
Feature Comparison
| Review item | Evidence requested | Boundary |
|---|---|---|
| Receiving component | Focus sequence and component visibility | External outline is a separate observation |
| Fixed/automatic layer | Immediate visibility with layer present | User-opened note is not a blanket exception |
| User-opened panel | Reveal route without advancing focus | Actual supported mechanism required |
| Movable content | Initial supplied position | Later user placement has a different scope |
| Modal behaviour | Focus taken and maintained until dismissal | Dialog appearance alone is insufficient |
This matrix is an evidence request, not a product score. Ask the supplier to mark unresolved requirements explicitly and identify the provider responsible for each layer. Preserve the software and input environment so a later release can be compared with the same scope.
Cost & ROI Analysis
Hypothetical review budget; all figures and outcomes are assumptions. Suppose a buyer allocates USD 300 to the layer inventory, USD 500 to integrated focus demonstrations and USD 250 to pilot observation. Initial spending is USD 1,050. Assume USD 250 in annual follow-up. Equipment, implementation and formal assessment are excluded.
For sensitivity analysis, assume annual gross contribution associated with additional completed purchases is USD 1,200, USD 700 or USD 200. These are not measured gains or forecasts. After the assumed USD 250 annual review cost, net contribution would be USD 950, USD 450 or negative USD 50. A real model should distinguish contribution from sales revenue.
| Assumed annual gross contribution | After USD 250 annual review | Simple payback on USD 1,050 |
|---|---|---|
| USD 1,200 | USD 950 | 1.11 years |
| USD 700 | USD 450 | 2.33 years |
| USD 200 | −USD 50 | No positive payback in this model |
First-year review spending is USD 1,300. Simple payback divides initial spending by positive assumed annual net contribution and omits timing, financing and other costs. A real pilot must distinguish visibility effects from traffic, assortment, payment reliability and unrelated software changes. The arithmetic establishes no causal benefit or equipment return.
Best Choice by Scenario
Packaged-product access: shortlist the single-door fridge when the retail format fits. Request layered-state evidence only for confirmed connected steps and supported input arrangements.
Touchscreen snacks and drinks: shortlist WM22 when the ordered mechanism suits the assortment. Ask which layers exist in the supplied build and how receiving components remain visible in the actual supported journey.
Two saleable sections: shortlist the dual-cabinet station when its layout fits the site. Define the real menu/payment interface and provider ownership before inferring focus behaviour from cabinet count.
Applications
Quotation attachment
Attach a layer inventory with triggers, persistence, initial positions and provider ownership. Specify the supported keyboard arrangement where relevant. Ask for actual focus-sequence evidence and mark proposed controls separately from included features. Keep additional full-visibility goals separate from the minimum criterion.
Pilot observation
Use agreed demonstration scenarios and appropriate participants on the intended hardware. Observe the receiving component rather than only the opened layer. Preserve the tested state and reveal mechanism. This article reports no user sessions, completion rate or machine-testing result.
Release review
Repeat affected demonstrations after changes to banners, navigation, notifications or connected services. A panel can keep its visual design while changing how it persists or how focus moves behind it. Tie acceptance to the demonstrated version and behaviour rather than an old screenshot.
FAQ
Does the minimum criterion forbid every partial overlap?
No. The cited explanation allows partial obscuring under the minimum criterion. It recommends reducing overlap and points to a separate enhanced criterion, which was not assessed here.
Is this only a test of the focus outline?
No. The explanation evaluates the focused component itself rather than an external focus indicator. Indicator visibility and contrast can involve other criteria and should be reviewed separately.
Does opening a panel automatically excuse hidden focus?
No. The user-opened-content note requires that the focused component can be revealed without advancing keyboard focus. Automatically appearing or pre-positioned content has a different boundary.
Are all user-moved panel positions assessed?
The explanation says only the initial positions of user-movable content are considered for this criterion. A buyer can specify additional practical review separately.
Can a modal avoid obscuring underlying focused controls?
The source describes a properly constructed modal as taking and maintaining focus within its visible content until dismissal. A dialog-like overlay without appropriate focus behaviour can still create risk. No machine modal was tested.
Do these products have verified keyboard support?
No. The public retail listings do not establish keyboard support or overlay behaviour. Ask the supplier to identify the actual supported input arrangement and demonstrate the ordered configuration.
Final Recommendation
Select the retail equipment format, then request a demonstration of the actual layered interface. Identify the receiving component, classify the layer and document the applicable visibility or reveal evidence. Keep component obscuring, indicator styling and keyboard exit as separate decisions. Record unresolved requirements before accepting the supplied version.
Source: W3C WAI, Understanding SC 2.4.11: Focus Not Obscured (Minimum), read on 10 October 2026, page updated 15 June 2026. This is informative web guidance. Linked techniques, the enhanced criterion and full normative standard were not assessed. Product descriptions rely on linked public listings and same-date recorded evidence. No machine testing, compliance determination or commercial gain is claimed.
CTA
Request a WEIMI quotation with configuration-specific layered-interface evidence. Describe the assortment, customer journey and supported input arrangement. Ask which panels or notifications appear, where focus moves and which provider can demonstrate the actual visibility behaviour.
