Skip to content
On this page Definition

Atlas · DS026 · Aesthetic: Sci-Fi

Cyberpunk

Dystopian technological city turned into a neon, high-contrast UI.

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

Definition

Dystopian technological city turned into a neon, high-contrast UI.

Traits

  • magenta
  • cyan
  • HUD

Typical settings: Games, Events, Storytelling.

When to use it, and when not

Consider it when the task and motivation match: sci-fi and gaming enthusiasts. Typical settings: games, events, storytelling.

Be careful when the risk below would hurt the main task: overly noisy hierarchy.

UX risk and how to reduce it

Risk: Overly noisy hierarchy.

Mitigation and accessibility: Keep a sober reading mode.

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.

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
5 / 5 (1 is few visual elements, 5 is many layered elements)
Expressiveness heuristic
5 / 5 (1 is restrained, neutral, 5 is highly expressive)
Information density heuristic
4 / 5 (1 is sparse, 5 is dense)

In our library

No design-style recipe in @codeatlasdev/ui implements this term yet. You can still build it from the --ca-* tokens: see Theming.

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 "Cyberpunk" direction (aesthetic, sci-fi): Dystopian technological city turned into a neon, high-contrast UI.
Visual and interaction traits to use: magenta, cyan, HUD.
Main UX risk: Overly noisy hierarchy. Mitigate it: Keep a sober reading mode.
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.

References

  1. Tuch, Presslaber, Stöcklin, Opwis, Bargas-Avila (2012). The role of visual complexity and prototypicality regarding first impression of websites: Working towards understanding aesthetic judgments. International Journal of Human-Computer Studies.Supported

    Supports: Two lab experiments with screenshots of real websites (119 in the first) found that visual complexity and prototypicality affected aesthetic ratings at presentation times of 50 ms and, in the second study, down to 17 ms.

    Does not support: That people understand a value proposition in that time, or that any named style is preferred. The measure is a rating of aesthetics, not comprehension or task success.

    Checked 2026-10-25.

  2. W3C Web Accessibility Initiative (2023). Understanding Success Criterion 2.3.3: Animation from Interactions. W3C WAI, WCAG 2.2 Understanding (Level AAA).Standard or guideline

    Supports: Non-essential motion triggered by interaction, such as parallax scrolling, can trigger vestibular disorders (dizziness, nausea, headaches); content should let users turn it off. The criterion is Level AAA.

    Does not support: A prevalence figure, or that all animation is harmful. Essential motion is excepted, and the criterion is above the AA level most programs target.

    Checked 2026-10-25.