PDF color contrast: how to check it, and how to fix brand colors that fail

PDF color contrast is how clearly text stands out from the color behind it, expressed as a ratio. WCAG 2.1 Level AA, the standard named in the ADA Title II web rule, asks for at least 4.5:1 for ordinary text and 3:1 for large text. Acrobat's Accessibility Checker does not measure contrast, so you check it yourself with an eyedropper and a free contrast checker. The failures tend to come from a short list of colors: light gray fine print, white text on a bright brand color, a pale table header row. Those colors usually live in a template, so fixing two or three of them at the source can clear hundreds of failing lines at once. This guide covers what the rule asks, how to measure it, common failing colors with passing alternatives, text over photos, and how to raise it with your brand owner.

What contrast ratio a PDF needs under WCAG 2.1

Success criterion 1.4.3, Contrast (Minimum), sets two thresholds. Text needs a contrast ratio of at least 4.5:1 against its background, and large-scale text needs at least 3:1. WCAG's formula compares the relative luminance, or perceived brightness, of the two colors, on a scale from 1:1 (identical colors) to 21:1 (black on white).

W3C explains that the 4.5:1 figure accounts for "moderately low visual acuity, congenital or acquired color deficiencies, or the loss of contrast sensitivity that typically accompanies aging." It is set so that people with low vision, people with color vision deficiencies and older readers can read the text without special software.

The thresholds are hard lines. W3C's Understanding document says computed ratios "should not be rounded (e.g., 4.499:1 would not meet the 4.5:1 threshold)." A gray that measures 4.48:1 fails, however close it looks.

What counts as large text in a PDF

WCAG defines large-scale text as "with at least 18 point or 14 point bold or font size that would yield equivalent size for Chinese, Japanese and Korean (CJK) fonts." PDF measures type in points, so use the font size the document was made with, as Word or InDesign shows it.

• Body text at 10–12 point, footnotes, captions, table text and form labels are not large. They need 4.5:1.
• A 16 point heading in regular weight is not large either. It needs 4.5:1.
• An 18 point heading, or a 14 point bold subheading, is large and needs 3:1.

What has no contrast requirement

WCAG exempts two groups. The first is incidental text: text that is part of an inactive control, that is "pure decoration," that is not visible to anyone, or that is "part of a picture that contains significant other visual content." The second is logotypes: "Text that is part of a logo or brand name has no contrast requirement."

The logo exemption is narrower than many teams hope. W3C's Understanding document says that "text that has insufficient contrast due to corporate identity or brand guidelines is not exempted." Your logo can stay as designed. A heading set in the logo's pale green cannot.

Graphics and form fields: success criterion 1.4.11

A separate criterion, 1.4.11 Non-text Contrast, asks for 3:1 for "parts of graphics required to understand the content" and for the visual information that identifies form controls. In a PDF, that means the border of a fillable field, and the lines, bars and slices of a chart that a reader needs to tell apart. Which parts a reader needs is a judgment, so Ockem's coverage map lists 1.4.11 with the other human-verified checks.

Does Acrobat check color contrast?

No. Acrobat's Accessibility Checker does not test color contrast. It lists contrast, along with logical reading order, as a manual check on every document. Clemson University's guide puts it plainly: "Acrobat's Accessibility Checker results will always warn to manually check color contrast." A job aid from the National Clearinghouse of Rehabilitation Training Materials, funded by the U.S. Department of Education, says the same: "The checker does not test color contrast." This comparison was written by Ockem. Our guide to free PDF accessibility checkers compares what each tool tests.

How to check color contrast in a PDF with free tools

1. List every pairing of text color and the background directly behind it: body text, headings, footnotes, links, callouts, table header rows, cover text and captions.
2. Find each color's value. The original file is the most accurate source: Word's font color settings and InDesign's swatches show the exact color. With only the PDF, use an eyedropper.
3. Enter the pair in a free checker. The WebAIM Contrast Checker (opens an external site) runs in a browser: type two hex values, or use its eyedropper, and it reports the ratio and a pass or fail for normal and large text. The Colour Contrast Analyser (opens an external site) (CCA) is a free Windows and Mac app from Vispero, long known as a TPGi tool, whose eyedroppers sample any color on screen.
4. Compare the ratio with the right threshold: 4.5:1, or 3:1 only for text that is truly large.
5. Write down each failing pair and where it comes from. That is your fix list.

Where the measurement goes wrong

• Anti-aliasing at small sizes. Screens soften letter edges with paler shades, so an eyedropper on a 9 point footnote often picks up an edge pixel instead of the text color. Zoom to 400% or more and sample the middle of a thick stroke, or read the color from the source file. WCAG notes that contrast "can be evaluated with anti-aliasing turned off."
• Transparency and tints. Text set at 60% opacity, or in a 40% tint of a brand color, renders lighter than its swatch suggests. Measure what is painted on the page.
• Gradients. Measure against the part of the background behind the letters that gives the lowest ratio, not the average.
• The usual suspects. Light gray fine print such as disclaimers and page numbers, white text on brand teal, orange or light blue, and white text on pale table header rows in budget books and annual reports. The table below shows typical ratios.
• Links that differ only by color. Success criterion 1.4.1, Use of Color, says color must not be "the only visual means" of conveying information, and W3C's failure F73 covers links "that are not visually evident without color vision." In a PDF, the simplest fix is to underline links.

Brand colors that commonly fail, with passing alternatives

We computed these ratios with WCAG's relative-luminance formula, cut them off at two decimals instead of rounding, and spot-checked them against the WebAIM Contrast Checker. The colors are typical of public-sector templates, not any organization's actual brand.

Three patterns stand out. The light blue passes only as large text, so it can pass in a cover headline and fail in a sidebar. The green at 4.11:1 is close and still fails. And the orange callout keeps its brand color by switching to dark text: a color too light for white text often works behind near-black.

How to fix contrast at the source: templates and brand colors

Contrast failures cluster. A 60-page annual report can show hundreds of failing text runs (stretches of text in one font and color) that trace back to two or three colors: the footer gray, the header row fill, the callout color. Fix them in the template, and every future document inherits the fix.

• Word. Change the theme colors once (Design, then Colors, then Customize Colors) and save the theme as the default, as Microsoft's instructions (opens an external site) describe. Text formatted through styles and theme colors updates everywhere at once. Text colored by hand does not.
• InDesign. Edit the swatch, and every object that uses it changes. Check styles for tints that lighten a passing color.
• The brand guide. This is where the fix lasts. Ask for an accessible text variant of each brand color: a darker shade of the same hue that reaches at least 4.5:1 on white, used for text, while the original stays for logos, fills and large shapes.

When you talk to the brand owner, lead with what does not change. The logo is exempt, and the brand colors stay for backgrounds, illustrations and large display type that reaches 3:1. What changes is text: body copy, small headings, captions and white text on light fills. Bring the numbers for your own colors, laid out like the table above, and a proposed darker variant of each, so the conversation is about which shade rather than whether.

How to fix text over photographs

Text over a photograph is the hardest case, because the background changes from one letter to the next. First decide whether the requirement applies. Words that are part of the picture, such as a banner in a parade photo, are exempt. A headline or date laid on top of a photo must reach the ratio against the part of the photo directly behind it.

The fixes, from least to most change to the design:

1. Add a solid backing band or panel behind the text in a color that passes. W3C's technique G18 describes shading the background "so that the letters maintain a 4.5:1 contrast ratio with the background behind them."
2. Add an overlay across the photo so its worst spot still gives the text enough contrast.
3. Move the text to a calmer part of the image, or off it entirely.
4. Change the text color. When the background is already as dark or as light as the design allows, the honest fix is darker (or lighter) text.

How Ockem Proof fixes contrast

Ockem Proof, our product, measures the real rendered contrast of every piece of text in a document against 4.5:1, or 3:1 for large text. Each finding points at the exact spot on the page, with the measured color pair. On scanned pages, contrast is measured from the page image itself, and you are asked only where it falls short. Template text hidden behind full-bleed cover artwork, which no reader can see, is detected and dismissed instead of being reported.

Then it compresses the problem. Hundreds of failing text runs usually trace back to two or three template colors, so Proof groups them into a handful of decisions: one document-wide color swap first, then changes for an area, then individual lines. For each decision it suggests compliant replacements, starting with the nearest accessible color. You set your organization's brand colors once, and every color pick shows them beside the replacements you chose before, each checked for contrast. Your reviewer accepts or adjusts each decision, then Proof applies everything in one pass and re-measures to confirm.

What a person still decides:

• Every color change. A color change is never applied without a person's approval.
• Text over photos. Proof proposes a solid backing band instead of a recolor. That is a visible design choice, so it is always yours to approve. When a background is already at its limit, Proof tells you the honest fix is darker text.
• Print-production color setups. A few color setups used for professional printing are routed to fixing in the source file rather than risked in the PDF.
• Non-text contrast. Proof measures form-field borders against their background, and a person attests to the graphics a reader needs.

Contrast is certified only on evidence the audit actually had. See the color contrast rule page.

See it on your own files

You can try one PDF (opens an external site) of up to 10 pages free, with no account, and see every contrast finding with its evidence. To size your library first, use the free PDF inventory tool. The color contrast rule page shows how Proof handles each case. For which checks software settles on its own, read what software fixes and what needs a person, and for charts and maps, see alt text for complex images.

Questions

This guide explains the rules in plain language. It isn’t legal advice. Check how they apply to your organization with counsel.