Blog › Accessibility › How Do You Check Color Contrast on an Online Store?
Noibu blog

How Do You Check Color Contrast on an Online Store?

How do you check color contrast on an online store?

To check color contrast on an online store, measure each text and interface color pair against WCAG 2.1: at least 4.5:1 for normal text, 3:1 for large text, and 3:1 for buttons, form borders, icons and focus indicators. Test sale badges, text over images, placeholder text and focus states, not just body copy.

Last updated November 19, 2026

A color contrast ecommerce accessibility check answers one question: can a shopper with low vision, color blindness or a phone in bright sunlight read every price, badge, button and form field on the store? Body copy is rarely the problem. The failures usually sit in the places merchandising teams change most often, such as a coral sale badge, a pale gray placeholder in the email field, a banner headline set over a busy lifestyle photo, or a focus ring that disappears against the brand color.

This playbook walks through how to check color contrast on an online store step by step, which WCAG 2.1 success criteria set the thresholds, and where stores most often fall short. It is written for anyone who owns a storefront, from a solo Shopify merchant to an enterprise ecommerce team.

Key takeaways

  • WCAG 2.1 SC 1.4.3 sets 4.5:1 for normal text and 3:1 for large text; SC 1.4.11 sets 3:1 for interface components, states and meaningful graphics.
  • Ratios are not rounded: 4.49:1 fails the 4.5:1 threshold.
  • The usual ecommerce failures are sale badges, light buttons, text over images, placeholder text and weak focus indicators.
  • Automated scanners catch flat text colors well but miss text over images and states such as hover, focus and error.
  • Noibu's ADA agent audits high-traffic pages against WCAG standards, reports where they fall short and stages changes for your review.

Part of: Noibu's ADA Agent

What color contrast ratios does WCAG 2.1 require on an online store?

Two WCAG 2.1 success criteria cover color contrast. Success Criterion 1.4.3, Contrast (Minimum), requires text and images of text to have a contrast ratio of at least 4.5:1 against their background, or 3:1 for large-scale text. Large text means at least 18 point, or 14 point bold, which the W3C puts at roughly 24px and 18.5px on screen.

Success Criterion 1.4.11, Non-text Contrast, requires a 3:1 ratio against adjacent colors for the visual parts of user interface components and their states, such as input borders, checkbox marks, selected swatches and focus indicators, and for graphics needed to understand the content, such as a size chart icon or a rating star. Both criteria are Level AA, the level most accessibility audits and the WCAG 2.1 AA checklist for online stores work to.

The W3C is explicit that ratios are not rounded, so a pair that measures 4.499:1 does not meet 4.5:1. Logos and brand names are exempt, as is text in an inactive control, such as a disabled button, and text that is pure decoration.

WCAG 2.1 contrast thresholds for store elements

Common online store elements, the minimum contrast ratio and the WCAG 2.1 success criterion that applies
Store elementMinimum ratioWCAG 2.1 criterion
Product descriptions, prices, badge and button labels under 24px4.5:11.4.3
Headlines at 24px or more, or 18.5px bold3:11.4.3
Placeholder and hover text4.5:1, or 3:1 if large1.4.3
Input borders, checkboxes, selected swatches3:1 against adjacent colors1.4.11
Focus indicators set by the store3:1 against adjacent colors1.4.11
Disabled buttons and logosNo requirement1.4.3 and 1.4.11 exceptions

How do you run a color contrast check on an online store, step by step?

A full contrast check combines an automated pass with a short manual pass on the elements scanners struggle with. The six steps below work for any platform, including Shopify, BigCommerce and Salesforce Commerce Cloud.

Six steps to check color contrast on an online store

  1. 1

    Pick pages by traffic

    Start with the home page, top collection pages, top product pages, cart and checkout, on desktop and mobile.

  2. 2

    Run an automated scan

    Scan each page for low-contrast text against the 4.5:1 and 3:1 thresholds in WCAG 2.1 SC 1.4.3.

  3. 3

    Measure badges and buttons

    Sample the exact foreground and background colors of sale badges, add-to-cart buttons and promo bars.

  4. 4

    Check text over images

    Measure headline text against the lightest and darkest areas of each banner image it sits on.

  5. 5

    Test every state

    Check placeholder, hover, focus, selected and error states against SC 1.4.3 and SC 1.4.11.

  6. 6

    Change tokens, then re-test

    Update the theme color settings at the source, then re-check the same pages after release.

Steps 1 and 2 give a baseline quickly. Steps 3 to 5 are where most stores find the failures a scanner missed, because those elements change with every campaign. Step 6 matters because a contrast problem fixed in one template often lives on in a color setting reused across dozens of others.

Why do sale badges and buttons fail color contrast so often?

Sale badges and promo buttons are designed to stand out, which usually means a saturated brand color with small white text on top. Saturated reds, oranges and pinks look loud but are often too light to carry white text. White text on a coral such as #FF5A5F measures about 3.05:1, which passes only if the text is large, while white on a deeper red such as #D32F2F measures about 4.98:1 and passes at any size. Both figures come from the relative luminance formula WCAG 2.1 defines for SC 1.4.3.

Buttons fail in two ways. The label can be too light for its fill, which falls under SC 1.4.3. Or a ghost button, an outline with no fill, can have a border so pale that the control is hard to find, which falls under SC 1.4.11 when the border is the only thing identifying the button. The W3C notes that a button with clear text does not need a contrasting border, but a light gray border such as #CCCCCC on white, at about 1.6:1, is not enough to mark a control on its own.

How do you check text over product and banner images?

Text over images is the hardest contrast check on a store, because the background is not one color. WCAG 2.1 lists background images that do not provide sufficient contrast with foreground text as a known failure, F83, under SC 1.4.3. A hero headline in white can pass over the dark half of a photo and fail over a pale sky in the same banner, and a crop that changes at a mobile breakpoint can move the text onto the light area.

To check it, sample the background color directly behind the lightest part of the text and behind the darkest part, and measure the text against both. The reliable ways to pass are a solid or semi-opaque overlay behind the text, a text shadow or halo wide enough to act as the background, or moving the copy off the image entirely. Repeat the check whenever the merchandising team swaps a banner, since the text styling usually stays the same while the photo changes. Product images also need text alternatives; the guide to alt text for product images covers that half of the same pages.

Do placeholder text, focus states and disabled buttons need to meet contrast?

Placeholder text does. The W3C's understanding document for SC 1.4.3 states that the criterion applies to text in the page, including placeholder text and text shown on hover. Light gray placeholders are among the most common failures on a store: #A9A9A9 on white measures about 2.35:1, while #767676 on white measures about 4.54:1 and passes. Placeholder text should still not replace a visible label, a point the guide to screen reader checkout accessibility covers for checkout forms.

Focus indicators do, when the store styles them. SC 1.4.11 requires a visual focus indicator the store has customized to reach 3:1 against the adjacent colors. A focus ring in the brand purple can vanish on a purple button, and removing the browser outline with no replacement leaves keyboard shoppers with no way to see where they are. Selected states count too: the outline around a chosen size or color swatch needs 3:1 against what sits next to it.

Disabled buttons do not. Both SC 1.4.3 and SC 1.4.11 exempt components that are not available for user interaction. The exemption covers a genuinely disabled control only. An add-to-cart button styled pale gray to look unavailable but still clickable is an active control and has to meet the thresholds.

Which tools check color contrast on an online store?

Three kinds of tools cover the job. Browser developer tools, such as the color picker in Chrome DevTools, show the contrast ratio of a selected text element. Standalone contrast calculators take two hex values and report the ratio against both thresholds. Page scanners flag every low-contrast text element they can compute on a page, which makes them the fastest way to get a baseline. Accessibility testing tools for ecommerce compares what each type of tool catches.

Scanners have the same blind spots everywhere: text over images, states that only appear on hover, focus or error, and colors applied by scripts after the page loads. That is why the manual steps above still matter. Contrast is also one of the most widespread problems on the web: WebAIM's 2026 Million report found low-contrast text below the WCAG 2 AA thresholds on 83.9% of the top one million home pages, with an average of 34 distinct instances per page.

How does Noibu's ADA agent help with color contrast on an online store?

Noibu's ADA agent checks a store's highest-traffic pages against WCAG standards, which includes contrast failures such as low-contrast prices, badges, buttons and form text. It produces a detailed list of where each page falls short, so a pale placeholder in the checkout email field shows up as a specific issue on a specific page rather than one line among hundreds from a generic scanner. It then prepares the changes and sends them for review, and nothing ships without the team's approval. After an approved change goes live, the agent re-audits the page to confirm the issue is resolved.

The ADA agent works in the Noibu console and in Claude, ChatGPT and other AI tools through Noibu MCP. It sits alongside Noibu's five other agents, Bug Resolution, Performance, CRO, A/B Testing and ROAS, which together cover what is broken, slow, accessible, converting and earning on an online store. If you are deciding what to tackle after contrast, which accessibility issues to fix first walks through how to prioritize. The ADA agent is a way to find and prioritize accessibility work; it does not replace manual testing or legal advice. To see what it finds on your own store, start with the free website audit.

Noibu is AI for ecommerce operations, the always-on optimization system that keeps online stores running at their best. A team of supervised AI agents finds what's broken, slow, or leaking revenue, does the work, and hands results back for human approval. Trusted by retailers like Free People, Guess, Liquid I.V., and Ariat.

Frequently asked questions

What contrast ratio does an online store need for text?

WCAG 2.1 success criterion 1.4.3 requires at least 4.5:1 for normal text and 3:1 for large text, which is at least 24px, or about 18.5px bold. Prices, product descriptions and badge and button labels under that size need 4.5:1.

Does a sale badge need to meet color contrast requirements?

Yes. The text on a sale badge is text, so it needs 4.5:1 against the badge color, or 3:1 if the text is large. Saturated reds, oranges and pinks often fail with small white text, so measure the exact colors rather than judging by eye.

Does placeholder text have to meet WCAG contrast?

Yes. The W3C states that success criterion 1.4.3 applies to placeholder text. Light gray placeholders often fall below 4.5:1, and a placeholder should not replace a visible label for the field.

Do disabled buttons need to meet color contrast?

No. WCAG 2.1 exempts components that are not available for user interaction. The exemption only covers controls that are truly disabled; a pale button that can still be clicked must meet the normal thresholds.

How do I check contrast for text on top of an image?

Sample the background behind the lightest and darkest parts of the text and measure the text against both. If either fails, add a solid or semi-opaque overlay behind the text, a wide text shadow, or move the text off the image, then re-check on mobile crops.

Can Noibu's ADA agent check color contrast on my store?

Yes. The ADA agent checks a store's highest-traffic pages against WCAG standards, lists where they fall short, including contrast, and stages changes for review. Nothing ships without approval, and the agent re-audits pages after approved changes go live.

Back to all blogs
‍
‍
See what Noibu’s AI agents would change on your store first.
Free website audit
Share

Keep your store running at its best, with AI agents that never clock out.