Design-system accessibility · 2026 · Solo — product framing, contrast engine, interaction design, TDD, verification, deployment
Luma Weave
An editorial weaving instrument for finding a palette's weak contrast thread and repairing it without uploading source.
The problem
Frontend engineers and design-system maintainers often audit contrast one hand-picked pair at a time, then guess at a replacement color when a token fails. Luma Weave accepts a bounded set of named CSS hex variables, generates every unique pairing, exposes the exact WCAG 2.x ratio, and lets the reviewer apply the smallest hue-preserving foreground shift that reaches 4.5:1. It is a local inspection instrument, not a complete accessibility certification or live-page crawler. GitHub-connected production deployment dpl_8ojj11uyaCr3jCvu2ARMYD9B3JGy completed successfully from exact private-repository SHA 5aa4b62542ce0e808c1ee1b69fe0c18b1507820b before the seven-step production repair path was re-proved.
Architecture
Key decisions
Make pair relationships spatial
The central weaving field encodes each token relationship as a selectable thread whose length follows contrast strength. One pair, its rendered specimen, threshold, and source repair stay causally connected instead of becoming a generic metric dashboard.
Repair the token the reviewer selected
The engine does not invent a new palette. It searches only along the chosen foreground's RGB line toward black and white, chooses the smallest Euclidean change that clears 4.5:1, and writes that explicit hex value back into the editable source.
Keep the claim narrower than accessibility
Luma Weave computes WCAG 2.x color contrast for bounded opaque hex pairs. It does not infer text size, alpha compositing, cascade context, focus behavior, or complete conformance, and the interface names those exclusions rather than implying certification.
Stop publication on dependency evidence
The first production audit inherited four high-severity advisories from the frozen template's framework resolution. Publication paused until Next.js 16.3.1 and repaired transitive packages produced a clean rebuild and zero-vulnerability production audit.