WHAT YOU
CAN DO
The same published color-vision method shows up wherever color carries meaning. Find your situation.
Everything below runs on one open-access method (Machado 2009 + CIEDE2000). Screening and correction aids, not a legal audit.
IF YOU CAN'T SEE THE COLOR
For people with color vision deficiency, at the screen and in the world.
I want to browse the web with the colors corrected.
The Colorblind Corrector extension — Chrome & Edge, corrects any page live.
I want to read a label, map, or sign in the real world.
The camera mode — point your phone, colors pull apart live. No app.
I want to check whether I'm colorblind, and which type.
Free color-vision tests — procedural, honest about screen limits.
IF YOU MAKE THINGS PEOPLE LOOK AT
For designers, developers, and data people shipping color.
I want to check my palette before I ship it.
The palette checker — paste colors, see the conflicts, get a fix.
Is the default palette in my chart library safe?
The benchmark — viridis, jet, Tableau, D3, Material, ColorBrewer, scored.
Is my text readable enough?
The WCAG contrast checker — AA/AAA for any text on any background.
I want to offer a colorblind mode on my own site.
The one-line widget — a floating eye your visitors can turn on.
I want to check colors in my code as I write.
The VS Code extension + the npm/pip packages for JS and Python.
I want to stop unsafe colors from reaching production.
The GitHub Action — fails a pull request when colors collapse.
IF YOU BUILD WITH SERVICES OR AI
For anything that calls an API or runs an assistant.
My app or agent needs to check and fix colors over HTTP.
The REST API — /check, /fix, /contrast, /simulate, plus a live badge.
I want my AI assistant to handle colors for me.
The MCP server — gives Claude/Cursor the check and fix tools.
I want to show that my palette is colorblind-safe.
The live badge — re-verifies your colors every time it loads.