Glove material and thickness must be included in interface tests

What it is

Representative glove-condition testing means using the glove materials, thicknesses, sizes, layering, wear condition, and contamination state actually authorized on site as the design input and acceptance-test conditions, rather than validating with bare hands or a single lab-standard glove. This leaf answers a methodological question — how to systematically build glove variables into a test plan — distinct from the specific degradation mechanisms covered elsewhere in the group (reduced sensitivity, total capacitive failure, the relative advantage of physical keys).

Why it happens

A glove's effect on touch performance results from several interacting variables: material determines electrical coupling strength and surface friction, thickness and layering (a thin liner glove under a winter protective glove) jointly shape the finger's effective profile and tactile transmission path, fit determines how precisely a fingertip lands on a control, and wear gradually shifts the material's original dielectric and friction properties away from its as-new state. These factors also interact with ambient temperature, humidity, and contamination rather than acting independently — the same glove might barely work dry, fail completely once wet, or conversely become "easier to trigger" once a water film accidentally improves the conduction path, at the cost of a higher false-touch rate. Testing under only one "average" or "typical" glove condition hides exactly the small number of combinations that fail completely or produce very high false-touch rates — and those combinations often correspond to the site's most hazardous work scenarios, such as winter outdoor repair requiring a cold-weather glove layered under a protective glove, because extreme weather and high-risk work frequently coincide.

Studying it

Starting from the site's actual issued PPE list and real usage frequency, build a stratified test matrix covering device/firmware version, glove condition (new/worn, dry/wet/contaminated), and representative tasks, and report each combination's pass or fail explicitly, rather than blending all combinations into one overall average. Samples must span different hand sizes and actual fit (whether the glove fills out fully or has slack), since fit for the same glove model varies by hand shape and materially affects tactile transmission and electrical coupling. Exhaustively testing every possible glove combination is usually impractical; instead select representative boundary conditions by failure mechanism and risk level, prioritizing the worst credible combination — thickest, poorest coupling, most worn, most contaminated — over random sampling.

Where it stops holding

A glove model that was never approved or included in the test matrix carries no obligation to have been declared compatible in advance, but the design cannot pass the cost of "glove incompatible" onto forcing personnel to remove required PPE just to get the task done — if that happens, it signals a gap in the test matrix that needs to be filled. A glove supplier changing material formulation, even under the same product name, can invalidate an existing compatibility result — "same model name" cannot be assumed to mean "same measured behavior." Passing one test also does not prove the device works across every field posture and every contamination combination; the boundary conditions actually covered by testing need to be stated explicitly in the acceptance record, not summarized as a blanket "passed glove compatibility testing."

Applying it

• Build and maintain a PPE–device model–firmware version compatibility matrix, and bring supplier changes and product revisions under change control, triggering re-validation instead of assuming compatibility still holds.
• Prioritize testing the worst credible combination for high-risk tasks — thickest glove, poorest-coupling material, worn and contaminated — over spreading test effort evenly across every theoretically possible combination.
• How to check: publish an explicit statement of supported scope (specific glove materials, thickness limits, and use conditions) with a corresponding fallback procedure, and periodically re-audit that statement against field-sampled glove specimens, rather than treating a lab test result as a one-time, permanently valid conclusion.

Related

• Same group: Y8.05.1 Thick gloves substantially reduce touchscreen sensitivity · Y8.05.2 Capacitive screens may fail completely with gloves · Y8.05.3 Physical keys are more reliable than touchscreens with gloves
• Nearby: Y7.06 Human-factors verification and validation · Y8.01 Field environmental constraints
• Search terms: glove compatibility testing · PPE usability · test matrix