LANE 02c / EDITORS · NORMALLED

Recent themes

Recent engineering-heavy themes. All verified against primary sources.

Opo — the most engineered entry in this report

IschaGast, 2026 (repo, MIT). “Colorblind-safe, OKLCH-based accessible color theme for editors, terminals, and web.” 363 contrast checks enforced at build time (121 per variant) plus a trichromacy CVD-distance gate — color pairs are checked for perceptual distance under simulated deuteranopia, protanopia, and tritanopia, and the build fails on collision. Uses the Okabe–Ito blue+orange move by name. Ships to 21 export targets (VS Code, Zed, JetBrains .icls, Neovim, Ghostty, Alacritty, iTerm2, Warp, Windows Terminal, Firefox, Slack, Raycast, Figma tokens, Adobe ASE, CSS, and more) — the widest platform spread of any CVD theme found. Light (primary), Dark, and a WCAG-AAA High Contrast variant. Notably it remaps ANSI green to teal (#33a397) rather than pure blue.

Opo dark editor mock

Opo dark CVD strip

Opo light editor mock

Opo light CVD strip

Shroom Space — three dichromacy variants, CI-enforced

WyattAu, 2025 (marketplace, repo). Seven variants including dedicated deuteranopia, protanopia, and tritanopia themes. Unusually honest engineering: ACCESSIBILITY.md enforces WCAG 2.1 AA on alpha-composited pairs, WCAG 2.2 SC 1.4.11 non-text, APCA |Lc| ≥ 2 separation between competing token categories, and linear-RGB CVD simulation — all in CI (npm run audit:palette), with an explicit note that simulation is “a worst-case collision detector, not a picture of what anyone sees,” plus a user-testing protocol.

Shroom Space deuteranopia editor mock

Shroom Space CVD strip

ColorSafe Themes (JetBrains) — measured axes

Clément Séhan, 2026 (plugin, repo). Two dark schemes — Pro-Deutan Dark (blue #5BB8F5 / amber #E6A020 axis, errors in hot pink #FF5F87 triple-encoded as color + squiggly + bold) and Tritan Dark (hot pink #FF216A / cyan #01D4F9, chosen because under tritanopia they sit at opposite ends of the preserved L–M axis). Rare rigor: the .icls source headers contain per-color WCAG contrast tables computed against the editor background.

ColorSafe Pro-Deutan editor mock

ColorSafe CVD strip

Cindervale Accessible — CVD-measured dark + light pair

erenthedeveloper0, 2026 (marketplace, repo, MIT). Original warm pair plus Accessible Dark / Accessible Light measured under all three dichromacies. The method is published and honest about its failures (docs/accessibility.md records where the accessible palette ended up closer than the original). Design rule: “pairs that share a hue family under a color vision deficiency are kept a full lightness tier apart”; red never needs to be told from green.

Cindervale Accessible dark editor mock

Cindervale CVD strip

More recent entries

ThemePlatformWhy it mattersLink
Slatis Nyx (utreras)VS Code + Zedbuild refuses to finish when two syntax roles collide under CVD; GitHub-CB syntax on true blackrepo
modus-theme-suite (lovesqualor)Ghostty/kitty/iTerm2/Neovim/Claude Codemodus deuteranopia ported across terminals + agentsrepo
gitlab-colorblind (bassepeder)GitLab web UIfirst GitLab CVD skin — browser extension remapping every --gl-color-green-*→blue, --gl-color-red-*→orangerepo
claude-code-contrast (samgutentag)Claude Codedocuments that the stock dark-daltonized theme leaves userMessageBackground at 1.18:1 contrast — “a luminance problem wearing a color problem’s clothes”repo
colbrush (2025-OSDC)React/PostCSSCVD-variant generator: derives protan/deutan/tritan themes from any base CSS paletterepo
Locus (Jeff1995)ObsidianOkabe-Ito variables verbatim in CSS (--oi-blue: #0072b2…), built for computational biologyrepo

Cautionary tale worth citing: claude-code-contrast shows that Claude Code’s shipped “daltonized” theme fixes every hue token but leaves the worst offender — a 1.18:1 message background — untouched. CVD safety is a luminance problem as much as a hue problem.