Atlas · DS076 · Aesthetic: Digital Retro
Dithered UI
Intentional use of dithering to create tones and grainy texture.
- Status in 2026: Niche. Used in a narrow community or product type.
- Trend 2027 to 2030: Niche (an editorial projection, not a forecast).
- The term: Community or market label, or a descriptive term.
Definition
Intentional use of dithering to create tones and grainy texture.
Traits
- dotted pattern
- raster
Typical settings: Portfolios, Creative.
When to use it, and when not
Consider it when the task and motivation match: experimental designers and retro culture. Typical settings: portfolios, creative.
Be careful when the risk below would hurt the main task: noise in text and images.
The audience is a hypothesis
"Experimental designers and retro culture" describes a motivation, task or context for which this direction tends to be chosen. It was not measured, and it says nothing about any age, gender or other group.
UX risk and how to reduce it
Risk: Noise in text and images.
Mitigation and accessibility: Never apply dithering to main 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.
- Tuch 2012 (Supported): Visual complexity and prototypicality in first impressions.
- W3C Web Accessibility Initiative 2023 (Standard or guideline): Accessibility requirements.
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
- 4 / 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
- 2 / 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 "Dithered UI" direction (aesthetic, digital retro): Intentional use of dithering to create tones and grainy texture. Visual and interaction traits to use: dotted pattern, raster. Main UX risk: Noise in text and images. Mitigate it: Never apply dithering to main 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.
References
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.
W3C Web Accessibility Initiative (2023). WCAG 2.2: How to Meet WCAG (Quick Reference). W3C Recommendation.Standard or guideline
Supports: What conformant content must do, as testable success criteria with a level (A, AA, AAA): for example 1.4.10 Reflow (no two-dimensional scrolling at a width equivalent to 320 CSS pixels, except content that needs two-dimensional layout), 2.4.11 Focus Not Obscured (Minimum) and 2.5.8 Target Size (Minimum) (at least 24 by 24 CSS pixels, with listed exceptions).
Does not support: What users prefer or what performs better. A standard says what is required, not what is popular.
Checked 2026-10-25.