Atlas · DS062 · Aesthetic: Transparency

Glassmorphism

Translucent planes with blur and luminous borders.

• Status in 2026: Active. In current use.
• Trend 2027 to 2030: Steady (an editorial projection, not a forecast).
• The term: Community or market label, or a descriptive term.

Definition

Translucent planes with blur and luminous borders.

Traits

• frosted glass
• blur
• layers

Typical settings: Landing pages, Overlays, Widgets.

When to use it, and when not

Consider it when the task and motivation match: users of dashboards and media apps. Typical settings: landing pages, overlays, widgets.

Be careful when the risk below would hurt the main task: contrast and rendering cost.

UX risk and how to reduce it

Risk: Contrast and rendering cost.

Mitigation and accessibility: Use opaque bases behind text.

How to check: Test a prototype against a plain baseline on a real task: completion, time, errors, comprehension, accessibility and preference, segmented by context rather than by stereotype.

Evidence

Indirect: the sources support underlying principles, not a preference for this style.

The sources below support the principles that apply to this term. None of them shows that this style works better or is preferred.

• W3C Web Accessibility Initiative 2023 (Standard or guideline): Accessibility requirements.
• Apple 2025 (Standard or guideline): Liquid Glass and materials.

Heuristic scales

Relative editorial judgements from 1 to 5. They are not results of a study and not a measure of quality.

Visual complexity heuristic

3 / 5 (1 is few visual elements, 5 is many layered elements)

Expressiveness heuristic

4 / 5 (1 is restrained, neutral, 5 is highly expressive)

Information density heuristic

3 / 5 (1 is sparse, 5 is dense)

In our library

The library ships design-style recipes for this term. Each is a set of tokens, not a different component set.

• CodeAtlas: Solid surfaces, plain paper, neutral shadows, 8px corners. The package default.
  designStyle("default")
• CodeAtlas Liquid: Liquid glass surfaces, brand mesh, glow and hue-tinted shadows. The former default.
  designStyle("liquid")
• Glassmorphism: Translucent blurred layers over a colorful backdrop, thin rims, soft shadows.
  designStyle("glassmorphism")

Prompt for your AI

Paste this into a coding agent. It carries the trade-offs, and asks for a baseline to compare against.

Design this interface in the "Glassmorphism" direction (aesthetic, transparency): Translucent planes with blur and luminous borders.
Visual and interaction traits to use: frosted glass, blur, layers.
Main UX risk: Contrast and rendering cost. Mitigate it: Use opaque bases behind text.
Keep it accessible to WCAG 2.2 AA: contrast, visible focus, keyboard operation, 24 px minimum targets, reflow at 320 CSS px and reduced motion.
Keep the content, hierarchy and behavior the same as a plain baseline so the two can be compared. Do not claim the style performs better; the choice should be validated with users.
In @codeatlasdev/ui start from the design-style recipes `designStyle("default")`, `designStyle("liquid")`, `designStyle("glassmorphism")` and override only tokens (`--ca-*`).