Perceivable · Distinguishable

WCAG 1.4.3 Contrast (Minimum) Explained in Plain English

WCAG 1.4.3 Contrast (Minimum) explained simply: the 4.5:1 and 3:1 ratios, what counts as large text, the exceptions, fixes and how to test your colors.

1.4.3 Level AA Added in WCAG 2.0 1 automated rule

Illustration: a low vision symbol, with 1.4.3 and Contrast (Minimum)
Table of contents

1.4.3 Contrast (Minimum) is the WCAG success criterion that makes sure text stands out clearly from its background. Normal text needs a contrast ratio of at least 4.5:1, and large text at least 3:1. Light gray text on white, white text on a pale photo and faint placeholder text are among the most common accessibility failures on the web. This guide explains WCAG 1.4.3 Contrast (Minimum) in plain English: the ratios, what counts as large text, the exceptions, how to fix low contrast and how to test your colors.

The official wording: “The visual presentation of text and images of text has a contrast ratio of at least 4.5:1”, except that large text needs at least 3:1, and incidental text and logotypes have no contrast requirement. (W3C, WCAG 2.2)

What Is 1.4.3 Contrast (Minimum)?

1.4.3 Contrast (Minimum) is a Level AA requirement under the Perceivable principle, in the guideline “Distinguishable”. It applies to text and images of text, and compares the brightness of the text color with the brightness of the background behind it.

The contrast ratio runs from 1:1 (no difference, such as white on white) to 21:1 (black on white). WCAG sets two minimums:

Four gray text samples on white with their contrast ratios. Hex AAAAAA at 2.3 to 1 fails for all text. Hex 949494 at 3.0 to 1 passes for large text only. Hex 767676 at 4.5 to 1 passes Level AA for all text. Hex 595959 at 7.0 to 1 also passes the stricter Level AAA.
The same gray text gets easier to read as the contrast ratio rises. 4.5:1 is the Level AA minimum for normal text.
  • 4.5:1 for normal text, such as body copy, links, labels and buttons
  • 3:1 for large text

Large text means at least 18 point, which is about 24 CSS pixels, or at least 14 point bold, which is about 18.66 CSS pixels in bold. Most body text at 16 pixels is normal text and needs 4.5:1.

The same gray color, hex 949494 on white, with a contrast ratio of 3.0 to 1, used at two sizes. As a 24 pixel heading, it is large text and passes the 3 to 1 minimum. As 16 pixel body text, it is normal text and fails, because body text needs 4.5 to 1.
One color can pass as a large heading and fail as body text.

Why 1.4.3 Contrast (Minimum) Matters

Low contrast makes text hard or impossible to read for many people:

  • People with low vision often see less contrast than others, so faint text fades into the background.
  • People with color vision deficiency may see some color pairs as much closer in brightness than they look to others.
  • Older adults commonly need more contrast as their eyes age.
  • Everyone struggles with low-contrast text on a phone in bright sunlight or on a dim, low-quality screen.

The 4.5:1 minimum is set so text stays readable for people with moderately low vision, without them needing to use assistive technology.

Who Is Affected by 1.4.3 Contrast (Minimum)

  • People with low vision
  • People with color vision deficiency
  • Older adults
  • People with some cognitive or reading disabilities, who find low-contrast text tiring
  • Anyone reading in glare, on a small screen or on a poor display

How to Meet 1.4.3 Contrast (Minimum)

Pick text and background colors that pass

Check every text color against the background it sits on, and adjust until it passes. This is the W3C technique G18, ensuring a contrast ratio of at least 4.5:1, and G145 for 3:1 on large text. Our free WCAG color contrast checker calculates the ratio for any pair of colors and tells you which levels it passes.

Build the passing colors into your design system, so every page uses them:

:root {
  --text: #1f2430;        /* body text, far above 4.5:1 on white */
  --text-muted: #595959;  /* secondary text, 7.0:1 on white */
  --link: #2c5f2d;        /* check each brand color before use */
}

Common problem spots to check:

  • Light gray body text, captions and footer text
  • Placeholder text in form fields
  • Text on colored buttons and badges, especially white text on light brand colors
  • Links, including their hover and focus states
  • Text on top of images and gradients

Always set the background with the text color

If you set a text color but leave the background to the browser, someone whose default background is dark can end up with dark text on dark. The W3C lists this as failure F24, specifying foreground colors without specifying background colors. Set both together on the same element or a parent.

Make text on images readable

Text over a photo or video is only as readable as the lightest or darkest part behind it. The W3C lists low contrast from a background image as failure F83.

Two hero banners with the headline Spring Trail Sale in white over a pale sky photo. In the failing one, the white text blends into the light sky. In the passing one, a dark semi-transparent overlay behind the text raises the contrast from 1.3 to 1 to 6.3 to 1.
A dark overlay or solid panel behind the text keeps it readable whatever the photo does.
/* A dark overlay under white hero text */
.hero {
  background: linear-gradient(rgba(20, 24, 32, 0.65), rgba(20, 24, 32, 0.65)), url('hero.jpg') center / cover;
  color: #fff;
}

Check the contrast against the lightest part of the image behind the text, not an average.

Know what is exempt

Four examples. Exempt: a logo with pale lettering, a disabled Submit button, and a street sign inside a photo of a busy street. Not exempt: light gray placeholder text reading Your email inside a form field, at only 1.8 to 1, which must still meet 4.5 to 1.
Logos, disabled controls and text inside photos are exempt. Placeholder text is not.

1.4.3 Contrast (Minimum) does not apply to:

  • Logotypes: text that is part of a logo or brand name.
  • Inactive controls: text on a disabled button or field.
  • Decoration: text that is purely decorative or not visible to anyone.
  • Text in pictures: text that is part of a picture with other significant visual content, such as a sign in a street photo.

Contrast for icons, form field borders and chart elements is covered separately by 1.4.11 Non-text Contrast, which asks for 3:1.

How to Test for 1.4.3 Contrast (Minimum)

Contrast on plain backgrounds is one of the easiest things for software to find. In our test of 10 accessibility checker tools, 9 of the 10 caught light gray text with a 2.3:1 ratio. Text on images is harder: none of the tools reported white text over a light background photo as an error, though 7, including AccessBell, flagged it for a manual check. Test in two steps:

  1. Run an automated scan to find low-contrast text on solid backgrounds. Run a free WCAG scan of any page to start.
  2. Check what tools cannot measure: text on images, gradients and videos, text that appears on hover or focus, and text in images.
  3. Measure any pair by hand with an eyedropper tool and our WCAG color contrast checker.
  4. Check every state: hover, focus, visited, selected and error states often use different colors.
  5. Check the whole template: navigation, footers, cookie banners and pop-ups are easy to miss.

For a quick reference, see our 1.4.3 Contrast (Minimum) page in the WCAG library, and the W3C’s Understanding 1.4.3 Contrast (Minimum).

Want to find low-contrast text across a page in seconds? Run a free WCAG scan, then check text on images by hand.

Builders put colors in global settings, so one fix can correct a whole site. See the Elementor accessibility checker, Divi accessibility checker, Wix accessibility checker and Squarespace accessibility checker checkers.

Pass and fail examples

The guide above is the long version. These two snippets are the shortest pair that shows the difference.

Fail Gray #aaaaaa on white is about 2.3:1, which fails for every text size under 1.4.3.
p { color: #aaaaaa; background: #fff; }
Pass Body text at #1f2430 on white is far above 4.5:1. The muted color #595959 on white is about 7:1.
body { color: #1f2430; background: #fff; }
.note { color: #595959; }

Testing WCAG 1.4.3 with AccessBell

AccessBell's scanner runs axe-core, which includes 1 rule that catch code-level failures of this criterion. Automated checks help you spot issues quickly. A person still needs to review what they cannot judge.

  • color-contrast: Ensure the contrast between foreground and background colors meets WCAG 2 AA minimum contrast ratio thresholds (details (opens in a new tab))

This criterion is included in: WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker.

Check your site for this with a free scan of one public page. AccessBell is a website accessibility monitoring tool, not an overlay.

Common failures on Shopify, WordPress, Wix and Squarespace

These are patterns in how the builders work. They are not counts from AccessBell scans. Where a platform hosts the screen, a merchant may not be able to change it, and an unscanned page is not a pass.

Shopify

Theme color settings and text sitting on product photos are the usual misses. Muted gray for prices and placeholders often falls under 4.5:1. Measure the pair in the contrast checker before you save the theme color, and scan the page with the Shopify checker.

WordPress

Global styles and page-builder color pickers allow body text that looks “soft” and fails 4.5:1. Placeholder text on search and comment fields is in scope. The WordPress checker reports text contrast axe-core can compute. Sample text on photos yourself.

Wix

The Accessibility Wizard requires Level AA and does not check every element. The Wix checklist says to measure contrast yourself. Site text styles and text over strip backgrounds are the pair to sample. Then run the Wix checker.

Squarespace

Site-wide text and button colors, and text on Fluid Engine photos, are the cases the Squarespace checklist calls out for 1.4.3. Change the color, add a background, or move the text. The editor preview is not the measurement. Use the contrast checker.

Level and conformance

Level AA, in WCAG since 2.0. Normal text needs at least 4.5:1. Large text, at least 18 point or 14 point bold, needs at least 3:1. Incidental text and logotypes are excepted. The guide above has the ratios and the figures. 1.4.11 covers non-text parts at 3:1.

Conforming at Level AA means meeting every Level A and Level AA criterion that applies, not only the ones labeled AA. See the WCAG 2.2 conformance requirements. This page explains the technical rule. It is not a legal opinion. Read the disclaimer.

Related WCAG criteria

Every criterion is listed in the WCAG 2.2 success criteria guide.

Frequently Asked Questions

What level is WCAG 1.4.3 Contrast (Minimum)?

Level AA. It has been part of WCAG since version 2.0, so it applies to every site that aims for WCAG 2.0, 2.1 or 2.2 Level AA, the level most accessibility laws point to.

What contrast ratio does 1.4.3 Contrast (Minimum) require?

At least 4.5:1 for normal text and 3:1 for large text. Large text means at least 18 point (about 24 CSS pixels), or at least 14 point bold (about 18.66 CSS pixels bold).

Does placeholder text need to meet 1.4.3?

Yes. Placeholder text is text people need to read, so it needs a contrast ratio of at least 4.5:1 against the field background. Many default placeholder styles are lighter than that.

Do logos and disabled buttons need good contrast?

No. Text in a logo or brand name, text on inactive (disabled) controls, purely decorative text and text that is part of a picture with other significant content have no contrast requirement under 1.4.3 Contrast (Minimum).

Can AccessBell test WCAG 1.4.3 automatically?

Yes. AccessBell runs 1 automated rule that can catch failures of this criterion, including in our WCAG 2.2 AA Checker, WCAG 2.1 AA Checker, ADA Compliance Checker, Section 508 Checker, EN 301 549 Checker. A person still needs to check what automation cannot judge.

Sources

This page explains a technical standard and is not legal advice. See our disclaimer.

About the Author

Anton StewartAuthor

Contributor, AccessBell

Anton Stewart writes and reviews accessibility guides for the AccessBell blog, checked against the W3C standards and other primary sources.

How we reviewed this page
  1. Current version

    First published. Checked against the W3C WCAG 2.2 Recommendation and the Understanding document for 1.4.3 Contrast (Minimum).

Check your site for WCAG 1.4.3

The free scan checks one public page for 1.4.3 Contrast (Minimum) and the other rules an automated test can see. AccessBell is a website accessibility monitoring tool, not an overlay. The main report is a one-time Domain Audit. Pro keeps the site monitored.

Pro is a 3-day free trial, then $29 per domain per month or $199 per year. You add a card at checkout and are not charged until the trial ends. Cancel before then and you will not be charged. A Page Report is $19 for one page.