Yes — a free accessibility color checker tells you in seconds whether cover art or EPUB text is readable. Type two hex codes into a checker and it scores the pair against the WCAG contrast formula. The resulting ratio decides whether a reader with low vision can decipher the words.
Contrast rules reach across the reading stack, from device hardware to the files loaded onto it. The comparison of Kindle and Kobo accessibility features covers what e-readers do for low-vision readers, and the accessibility hub collects the wider coverage. Here the focus stays on color.
What Does an Accessibility Color Checker Actually Measure?
It measures the contrast ratio between a foreground and a background color. Per the W3C's WCAG documentation, the ratio is computed as (L1 + 0.05) / (L2 + 0.05), where L1 and L2 are the relative luminances of the lighter and darker color. Values run from 1:1 for identical colors up to 21:1 for black on white.
WebAIM's Contrast Checker reports the ratio with pass and fail states at WCAG AA and AAA, separately for normal text and for large text, plus graphical objects. Appending &api to a permalink returns the same data as JSON, per WebAIM's documentation.
Which Contrast Ratios Should E-Book Text Hit?
Aim for at least 4.5:1 on normal text and 3:1 on large text at WCAG level AA, per the W3C's Understanding Contrast Minimum page. Large-scale text means at least 18 point, or 14 point bold. Level AAA, the stricter tier, asks for 7:1 on normal text and 4.5:1 on large text.
The size definition matters more than it first appears. WebAIM converts the thresholds to roughly 18.66 pixels for 14 point bold and 24 pixels for 18 point, larger than most cover taglines and chart labels. The W3C also cautions that computed values should not be rounded, so 4.499:1 fails.
Two documented exceptions matter for cover work. Text inside a logo or brand name has no contrast requirement, and neither does incidental text such as pure decoration, per the same W3C page. A publisher's colophon mark escapes the math; a title does not.
How Do You Fix a Failing Pair?
Most failing pairs are fixed by changing lightness rather than hue. The WCAG formula runs on relative luminance, so lightening the darker color or darkening the lighter one moves the ratio in a predictable direction. The checker shows a new score as you drag.
- Enter the exact hex values from the stylesheet or design file, including the alpha value if the foreground is partly transparent.
- Read the ratio against the AA row for your text size first, since that is the level most briefs reference.
- Drag the lightness slider on whichever color has room to move, stopping when the pass state flips.
- Re-check the exported art, because flattening and overlay layers can shift the effective color under small type.
That last step matters for covers. A pair that passed inside the design file can drift once texture layers are merged, so sample the final image instead of trusting the earlier numbers.
Where Do Automated Checks Fall Short?
A checker only sees the two colors you feed it, so anything that puts many colors under the type sits outside its model. Gradients and photographs behind a title break that assumption, and the W3C's Easy Checks guide notes that contrast tools each come with strengths and weaknesses.
Charts and diagrams live in a separate WCAG lane. Since WCAG 2.1, per WebAIM's summary, graphics and user interface components need 3:1 against adjacent colors, a requirement a text-pair workflow can miss entirely.
EPUB adds one more wrinkle. Many reading apps ship dark modes and theme controls that recolor a book, so a palette checked in one theme is not always the palette every reader sees. None of these tools establish how a given app restyles text.
Conclusion: Run the Numbers Before You Publish
Contrast checking is the rare publishing chore that costs nothing and takes minutes. The thresholds are public, the tools are free, and the failures they catch, faint body copy above all, are the complaints low-vision readers raise most often. One ratio settles the question before a reader squints. Readers following this should also see What Should Indie Authors Check Before Publishing An Accessible EPUB?.
The sequence is short: pull hex values from the final art and run them through a checker, holding body text to the 4.5:1 line the W3C sets. What no tool settles is taste. The math can approve a palette while the cover still feels flat, and that judgment stays with the author.
