Skip to content
Codex Skin Index
応募
accessibilitycontrastwcag

High-Contrast Codex Skins: Accessibility That Actually Looks Good

High contrast isn't ugly gray-on-black. Good accessible Codex skins meet WCAG contrast ratios while keeping character — here's how to pick and check them.

“Accessible” sounds like a downgrade. Gray on black, big fonts, no personality. It doesn’t have to be — some of the most striking Codex skins in this index also pass WCAG contrast checks. The trick is knowing what to look for, and a couple of skins here prove the point.

The number you actually need: 4.5:1

WCAG AA for normal text wants a contrast ratio of at least 4.5:1 between text and background. Large text (18px+ or 14px bold) only needs 3:1. Code — your main content — is normal text, so 4.5:1 is the bar.

You don’t need to be a designer to check it. Plug any skin’s foreground and background hexes into any contrast checker, and you get the ratio in seconds. If your text color sits below 4.5:1 on its background, that’s the whole problem — fix that one pair and you’re 90% there.

What makes an accessible skin feel nice

High contrast fails only when it’s high everywhere. The good skins keep a clear hierarchy:

  • Code text on background: ≥ 4.5:1. Non-negotiable.
  • Muted UI chrome: comments, line numbers, panel labels can sit lower (3:1+), so the eye isn’t shouting at everything at once.
  • One strong accent for cursors/selection, kept above 3:1 against its neighbors.

Monokai Stone (CLI) does this well — the syntax colors stay bright enough to read while the UI frame stays quiet. Forest Mist shows an accessible palette that doesn’t have to be high-contrast-ugly; the muted greens still clear the bar.

Color blindness: the extra check

Contrast ratio only covers brightness. If you’re colorblind — about 8% of men — red/green distinctions disappear. So:

  • Don’t rely on color alone to distinguish states (e.g. only a red/green dot for errors). Pair it with an icon or a word.
  • Prefer blue/orange accents over red/green pairs where possible. Blue Enchantress and Vivid Purple are both safe bets on that axis.

If you share your setup or publish screenshots, these checks matter for your readers too, not just you.

How to check a skin in 30 seconds

  1. Open the skin’s detail page — the palette hexes are listed there.
  2. Grab the background and foreground hexes.
  3. Run them through a contrast checker (any free one works).
  4. Text below 4.5:1 → adjust or pick another skin from this index.

Quick FAQ

Is dark mode worse for accessibility? Not inherently. Contrast ratio is what matters, not the background’s lightness. Some people with astigmatism prefer light mode; some don’t. Pick by your eyes, then verify the ratio.

Can I edit a skin’s colors to fix contrast? Yes, if you’re comfortable editing the theme file. Bump the foreground lightness or darken the background until the pair clears 4.5:1, save as your own variant.

Do accessible skins look “boring”? Only if the palette is flat. The skins in this index with strong accents — Vivid Purple, Blue Enchantress — are loud and accessible at the same time. Contrast and personality aren’t opposites.

Accessibility is a checklist, not an aesthetic. Verify the 4.5:1 ratio on whatever skin you love, fix the one pair that fails, and keep the look. Start from Monokai Stone if you want a known-good base, or browse the full index — the creating a skin guide also shows where to edit the hexes.

この記事で紹介したスキン

すべて見る skins .