---
name: Progressive Enhancement
type: reference
status: fixed
depends_on: [foundation/constant-contextual]
propagates_to: [aleris-design-governance.md]
open_questions: []
last_verified: 2026-03-21
---

# Progressive Enhancement — Design Principle for Aleris

## Definition

Progressive enhancement means building from the simplest functional layer upward. Each added layer of complexity enriches the experience but is never required for the base to work. The foundation stands on its own; everything else is additive.

The term comes from web development (Steve Champeon, ~2003) where it describes a three-layer approach: semantic HTML first (content and structure), CSS second (visual presentation), JavaScript third (interactivity). Each layer makes the experience richer. No layer is a prerequisite for the one below it to function.

## As a Design Principle

Progressive enhancement extends beyond code architecture into a design philosophy:

**The base layer must be complete, not minimal.** Progressive enhancement is not "build a bad version first." The base layer should be well-considered, functional, and dignified. It is the experience most users will have, not a fallback for edge cases.

**Complexity is earned, not assumed.** Every layer of richness — animation, dynamic behaviour, visual elaboration, interactive features — must justify itself. If removing a layer breaks the experience rather than reducing it, the architecture is wrong.

**Capability differences are normal, not exceptional.** Users arrive with different devices, connections, abilities, and contexts. A system built on progressive enhancement treats this variance as the default condition, not as a problem to solve.

## How This Applies at Aleris

**Across technical capability.** Separate IT tenants per country, varying digital maturity across 43 organizational units, colleagues building with different tools and competence levels. Progressive enhancement means the design system's base layer works for the least capable implementation, while more capable teams can add refinement without diverging from the system.

**Across surface temperature.** An instrumental surface is not a stripped-down communicative surface — but the relationship between them follows progressive enhancement logic. The instrumental surface is a complete base layer. The communicative surface adds expressive layers (generous spacing, richer typography, illustration, visual warmth) on top of the same structural foundation. Remove the expressive layers and you have a functioning instrumental surface, not a broken communicative one.

**Across patient contexts.** A patient on a slow connection, an older device, or using assistive technology meets a complete service — not a degraded version of the full experience. Features that require JavaScript, high bandwidth, or specific capabilities are enhancements, not prerequisites.

**Across the design token system.** The token architecture itself can follow progressive enhancement: primitive tokens are the base (always present, always functional). Semantic tokens add meaning and context. Surface mode tokens add situational adaptation. Each layer references the one below it. A product that only implements primitives still gets a coherent Aleris palette. A product that implements all layers gets full contextual expression.

## What Progressive Enhancement Is Not

**Not graceful degradation.** Graceful degradation starts from the richest experience and tries to handle what happens when things break. Progressive enhancement starts from what always works and builds upward. The direction matters — it changes what you treat as default.

**Not lowest common denominator.** The base layer is not the worst version. It is the most robust version. Layers added on top make it more expressive, more efficient, or more delightful — but the base is already good.

**Not anti-complexity.** Progressive enhancement does not avoid complex features. It ensures complex features are structured as additions to a functioning foundation, not as load-bearing walls that collapse when conditions are imperfect.

## Design Decision Record

**Decision:** Progressive enhancement is a foundational design principle for Aleris digital products and the design token system.
**Why:** Aleris operates across three countries with separate IT infrastructure, varying technical capability, and diverse user contexts (patients, clinicians, administrators). A principle that treats capability variance as default rather than exception produces more resilient products and a more adoptable design system. It also aligns with healthcare UX requirements where accessibility and reliability are non-negotiable.