# Brutalism DS015. Movement: Digital Brutalism. Page: https://ui.codeatlas.com.br/atlas/brutalism/. Index: https://ui.codeatlas.com.br/llms/atlas.txt Web translation of formal roughness, explicit structure and challenged conventions. - Status in 2026: Active. In current use. - Trend 2027 to 2030: Niche (an editorial projection, not a forecast). - The term: Established historical name. ## Traits - raw type - blocks - contrast Typical settings: Portfolios, Art, Alternative technology. ## When to use it, and when not Consider it when the task and motivation match: experimental audiences and creative communities. Typical settings: portfolios, art, alternative technology. Be careful when the risk below would hurt the main task: inconsistent usability and legibility. Audience (a hypothesis about motivation and task, never measured, not a statement about any group): Experimental audiences and creative communities. ## UX risk and how to reduce it - Risk: Inconsistent usability and legibility. - Mitigation and accessibility: Preserve navigation and access to information. - 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. - [E02] Lavie, Tractinsky (2004). Assessing dimensions of perceived visual aesthetics of web sites. https://doi.org/10.1016/j.ijhcs.2003.09.002 (Supported). Does not support: That either dimension is preferred, or that a named style is classical or expressive. It measures how people perceive aesthetics, in 2003-era web sites, not task success or the effect of any style. - [E04] Hassenzahl (2004). The Interplay of Beauty, Goodness, and Usability in Interactive Products. https://doi.org/10.1207/s15327051hci1904_2 (Supported). Does not support: Results for other products, tasks or populations. The products were four skins of one kind of player. - [E08] W3C Web Accessibility Initiative (2021). WCAG 2 supplemental guidance. https://www.w3.org/WAI/WCAG2/supplemental/ (Standard or guideline). Does not support: Normative requirements: supplemental guidance is advisory, not required for conformance. This page is an index; a specific recommendation needs the linked document. ## 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: 4 / 5 (heuristic) - Expressiveness: 5 / 5 (heuristic) - Information density: 3 / 5 (heuristic) ## In our library - designStyle("brutalism"): Neobrutalism. Thick black strokes, hard offset shadows, flat saturated fills, loud type. - designStyle("sketchbook"): Sketchbook. Journal on grid paper: serif display, square outlined cards with hard shadows, hand-drawn marks (.ca-mark-*). ## Prompt for your AI ```text Design this interface in the "Brutalism" direction (movement, digital brutalism): Web translation of formal roughness, explicit structure and challenged conventions. Visual and interaction traits to use: raw type, blocks, contrast. Main UX risk: Inconsistent usability and legibility. Mitigate it: Preserve navigation and access to information. 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("brutalism")`, `designStyle("sketchbook")` and override only tokens (`--ca-*`). ```