Transparency carries a pass-through meaning, not just a visual style

What it is

A glass door looks passable because it is see-through; a brick wall does not, because it hides what is behind. Once translucency in a UI leaves that transparency affordance, it becomes merely a tasteful grey — people still poke what it covers, or they refuse to walk through a ghost panel that has no collider. Alpha here is an action prediction, not a swatch.

Why it happens

In the statistics of the real world, opaque ≈ volumetric, blocking, able to take weight; transparent ≈ maybe passable, maybe only a film. That mapping is imported into virtual environments. Designers often pick twenty percent opacity so the view is not blocked; users read “this is not solid”. Whether to walk around or through, whether to hit this or the button behind it, follows the semantics, not the depth buffer. If a translucent panel actually catches rays and hands, meaning and collision disagree and people probe. If a solid button is drawn translucent, people assume the press went through to whatever is behind. A heavy frame, a contact shadow, or a thick material can still read as “a solid plate with a window” even when the middle is clear — affordance is a bundle, and α is only one strand.

Studying it

A collision-expectation task: show objects at different α, ask whether a hand will be stopped or will pass, then let people reach and record hesitation and path changes. Aesthetic ratings are not a substitute; taste and meaning can split completely.

Independent variables: α, presence of a collider, presence of sound or a specular cue that says “solid”. Dependent variables: accuracy of the pass-through prediction, first-contact strategy (go around / go through), number of probes.

Action-possibility judgements from affordance research, and XR walkthroughs of go-through versus collide, sit on this path.

Where it stops holding

Game energy shields, ghosts, and scan volumes have already conventionalised “translucent = passable or hazardous volume”; users read the genre, not the α. A screen-space health bar with no physical metaphor is not treated as a volume, so transparency falls back to style. Children and people new to XR read more like real glass. Add a heavy frame and a contact shadow and even a clear middle may read as a windowed solid. Accessibility: encoding “not hittable / passable” in α alone fails for low vision and needs a second channel.

Applying it

• Reserve translucency for volumes that really can be walked through, seen through, and that do not eat input; make controls that must catch input opaque.
• Ghost previews of objects about to be placed stay translucent; on commit they turn opaque so meaning follows state.
• If a translucent panel must be hittable, say “this layer is solid” with a frame, cursor snap, or sound, so the hit does not fall through.
• How to check: have someone wear the headset for ten seconds and ask whether a hand can pass here and which layer a press acts on. Every mismatch with collision or ray tests is the semantics lying.

Related

• Same group: N3.06.1 A semi-transparent panel mixes with the background · N3.06.2 Occlusion is the strongest depth cue and must not be violated · N3.06.3 Transparency must adapt to background complexity · N3.06.4 Cast and contact shadows declare depth better than transparency · N3.06.6 Stacked semi-transparent panels multiply opacity · N3.06.7 On optical see-through, black equals transparent; a dark UI cannot hide reality
• Nearby: N3.03 Depth Conflict · N2.09 Direct Grab and Virtual Touch
• Search terms: transparency affordance · see-through · collision expectation