No. It approximates average perception with a mathematical model; real people vary in severity, adaptation and lighting context, and many have reduced color vision, not absent.
Carregando ferramenta… / Loading tool…
Compare palettes under protanopia, deuteranopia, tritanopia and achromatopsia before shipping.
Color vision deficiency ("color blindness") is not rare: it affects roughly 1 in 12 men and 1 in 200 women. For those people, an interface that differentiates states by color alone, green "ok", red "error", can become ambiguous. This tool applies a matrix-based simulation to approximate how a palette is perceived under protanopia, deuteranopia, tritanopia and achromatopsia, showing the original and the simulated side by side. It is a design approximation (not a medical diagnosis) to help you spot colors that collide and reinforce important states with something beyond hue: a label, icon, shape, pattern or contrast.
The most common deficiencies are on the red-green axis: protanopia (difficulty with red) and deuteranopia (difficulty with green) make greens, reds, oranges and browns converge. Tritanopia, much rarer, affects the blue-yellow axis. Achromatopsia, rare, is the near-total absence of color perception, where everything becomes shades of gray.
That is why the red/green pair, so often used for "wrong/right", is precisely the worst choice to carry meaning alone: for a good share of men, those colors can look the same. Simulating these types reveals collisions that go unnoticed by someone who sees the full spectrum.
Example 1, status indicators: if "available" is a green dot and "unavailable" a red dot, test under deuteranopia. If the two dots look alike, add an icon (check and x), text or a different shape, so the state does not depend on color.
Example 2, chart lines: series distinguished by color alone can merge. Beyond choosing colors that survive the simulation, use redundant encodings: dashed vs solid lines, different markers, and direct labels at the end of each line.
Matrix simulation is a mathematical average: real people vary in severity, adaptation and lighting condition, and many have reduced (not absent) color vision. So the result guides design decisions but does not replace user testing or an accessibility audit.
The principle to take away: never let color be the only way to communicate something important. Sufficient contrast (WCAG) helps a lot, but contrast and hue are different things, two grays can have okay contrast and still confuse color-coded meanings. Pair color with text, shape, icon or pattern for a robust interface.
Paste the code into your HTML and the tool shows up on your page, without J-Kit's navigation and ads. It still runs in the browser of whoever visits your site.
<iframe
src="https://jkit.tools/embed/en-US/color-blindness-simulator"
width="100%"
height="600"
style="border:0"
loading="lazy"
title="Color Blindness Simulator"
></iframe>These references help contextualize formulas, standards, APIs and limitations used on this page. They do not replace professional validation when a result has legal, financial, medical or operational impact.
No. It approximates average perception with a mathematical model; real people vary in severity, adaptation and lighting context, and many have reduced color vision, not absent.
#3DDC97#E5C46B#E07B8E#4EA8DE#F7F8F7#796DAC#D9DB86#BAC288#7069CE#F7F7F7#796DAC, #D9DB86, #BAC288, #7069CE, #F7F7F7The palette is processed locally; no color or image is sent to the server.