# Neumorphism DS057. Aesthetic: Surfaces. Page: https://ui.codeatlas.com.br/atlas/neumorphism/. Index: https://ui.codeatlas.com.br/llms/atlas.txt Controls suggested by relief created with outer and inner shadows. - Status in 2026: Niche. Used in a narrow community or product type. - Trend 2027 to 2030: Declining (an editorial projection, not a forecast). - The term: Community or market label, or a descriptive term. ## Traits - low contrast - soft extrusion Typical settings: Prototypes, Illustrative components. ## When to use it, and when not Consider it when the task and motivation match: experimental audience interested in texture. Typical settings: prototypes, illustrative components. Be careful when the risk below would hurt the main task: poor affordance and contrast. Audience (a hypothesis about motivation and task, never measured, not a statement about any group): Experimental audience interested in texture. ## UX risk and how to reduce it - Risk: Poor affordance and contrast. - Mitigation and accessibility: Avoid on critical controls and test contrast. - 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 support the principles that apply to this term. None shows that this style works better or is preferred. - [E07] W3C Web Accessibility Initiative (2023). WCAG 2.2: How to Meet WCAG (Quick Reference). https://www.w3.org/WAI/WCAG22/quickref/ (Standard or guideline). Does not support: What users prefer or what performs better. A standard says what is required, not what is popular. - [E19] Nielsen Norman Group (2026). The Aesthetic-Usability Effect. https://www.nngroup.com/articles/aesthetic-usability-effect/ (Standard or guideline). Does not support: An effect size, or that appeal improves task performance. The article's example is one participant; it is a practitioner synthesis, not a controlled study. ## Limits - The atlas is a broad, living catalogue, not every style that exists. No authority enumerates them, and the classes (movement, aesthetic, design system, layout, pattern, principle) overlap. - The 1 to 5 scores are relative editorial judgements. They are not results of a study and not a measure of quality. - An audience is a hypothesis about motivation, task and context. It was never measured and says nothing about any age, gender or other group. - The sources support underlying principles (visual complexity, legibility, grouping, accessibility, platform conventions). None shows that a particular style works better or is preferred. - The 2027 to 2030 trend is an editorial projection, not a forecast. - Terms in the Future / AI category rest on exploratory work, some of it preprints, with no causal validation. Last reviewed 2026-10-25. ## Heuristic scales Relative editorial judgements from 1 to 5, not results of a study. - Visual complexity: 2 / 5 (heuristic) - Expressiveness: 3 / 5 (heuristic) - Information density: 2 / 5 (heuristic) ## In our library - designStyle("neumorphism"): Neumorphism. Monochrome base extruded by paired shadows. Showcase surfaces, not dense data. ## Prompt for your AI ```text Design this interface in the "Neumorphism" direction (aesthetic, surfaces): Controls suggested by relief created with outer and inner shadows. Visual and interaction traits to use: low contrast, soft extrusion. Main UX risk: Poor affordance and contrast. Mitigate it: Avoid on critical controls and test contrast. 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 recipe `designStyle("neumorphism")` and override only tokens (`--ca-*`). ```