Menu

APCA Contrast Checker and Compare with WCAG 2

See the APCA Lc score and the WCAG 2 contrast ratio for the same colors, side by side, and find out where the two methods disagree.

Preview

Headline 32px bold
Body text 18px regular. The quick brown fox jumps over the lazy dog.
Light 16px weight 300 needs more contrast.
Small 14px regular text for captions.
Tiny 12px bold label

WCAG 2 contrast ratio

0: 1

APCA lightness contrast

0Lc

Side-by-side results

APCA levels follow the commonly published Lc guidance (body text 75+, preferred 90, large and bold text lower). Sizes and weights are simplified guidance, not a substitute for the full APCA font lookup table.

How both methods react on this background

WCAG 2 ratio (÷21) APCA |Lc| (÷106) Your text color (as a gray of equal luminance)

Dashed lines mark WCAG 4.5:1 and APCA Lc 75. Notice how WCAG gives the same credit to very dark and very light text near mid-tones, while APCA is polarity-aware: it rewards dark text on light backgrounds differently from light text on dark ones.

Try pairs where the two methods differ

✓ Copied!
ACCESSIBILITY • COLOR SCIENCE • READABILITY

APCA Contrast Checker: Test Perceptual Text Contrast Online

Use the APCA Contrast Checker to explore how foreground and background colors behave from a perceptual readability perspective. Compare an APCA Lc result with the traditional WCAG 2 contrast ratio, preview text at different sizes and weights, and make better color decisions for websites, apps, design systems, dashboards, and digital products.

APCA, short for Accessible Perceptual Contrast Algorithm, approaches contrast differently from the ratio-based method used by WCAG 2.x. Instead of treating every color relationship as a simple ratio, APCA is designed around perceived lightness contrast and considers factors such as polarity, text size, and font weight when evaluating readability.

Open the APCA Contrast Checker
What is an APCA Contrast Checker?

An APCA Contrast Checker evaluates a text color against a background color using the Accessible Perceptual Contrast Algorithm and reports a perceptual lightness contrast value called Lc. It can be used alongside a WCAG 2 contrast ratio to understand how different contrast models interpret the same color pair.

What Is APCA Contrast?

APCA contrast is a perceptual approach to measuring the visual difference between foreground text and its background. APCA stands for Accessible Perceptual Contrast Algorithm. It was developed as a readability-focused contrast model for self-illuminated displays such as computer monitors, smartphones, tablets, and other digital screens.

The central idea is simple: two color combinations can have a numerical contrast relationship that looks acceptable mathematically but can behave differently when people actually read text on a screen. APCA therefore focuses on perceived lightness contrast rather than relying only on the conventional WCAG 2 contrast ratio.

APCA is particularly useful when designing typography, user interfaces, dark mode themes, design systems, dashboards, navigation elements, buttons, labels, captions, and other components where readability matters. The algorithm is polarity-aware, meaning it distinguishes between dark text on a light background and light text on a dark background.

This makes APCA especially interesting for modern interface design because the same nominal luminance difference does not necessarily produce the same reading experience when the polarity is reversed.

Dark Text / Light Background Readable Aa Light Text / Dark Background Readable Aa

Why Use an APCA Contrast Checker?

Color accessibility is more complicated than selecting a dark color and a light color. Designers need to consider text size, font weight, display conditions, interface context, and whether the text is intended for continuous reading or short labels. An APCA contrast checker provides another way to investigate these relationships.

The biggest advantage is that APCA encourages designers to think about perceptual readability. Instead of asking only whether two colors produce a particular numerical ratio, you can ask whether the combination provides an appropriate level of perceived contrast for the typography being used.

This is valuable when building a modern color system. A brand may have a beautiful primary color that works perfectly for large headings but becomes difficult to read when used for small body copy. An APCA workflow helps reveal these differences earlier in the design process.

APCA can also be useful for dark interfaces. Dark mode often involves near-black surfaces, gray text, muted labels, and accent colors. A combination that appears elegant can become uncomfortable or difficult to read when used repeatedly across a large interface.

APCA Lc: What Does the Score Mean?

APCA uses Lc, meaning lightness contrast, as its primary output. Unlike a traditional contrast ratio such as 4.5:1 or 7:1, an APCA result is expressed on an Lc scale and can also communicate polarity.

APCA documentation commonly describes positive values for dark text on light backgrounds and negative values for light text on dark backgrounds. The magnitude represents the strength of perceptual contrast. This is one reason APCA results should not be interpreted as if they were WCAG 2 ratios.

A commonly discussed APCA starting point for body-text guidance is around Lc 75, with higher values providing stronger contrast. However, APCA's broader guidance also connects contrast with text size and weight, so a single Lc number should not be treated as a universal pass/fail rule for every design situation.

Your APCA Contrast Checker provides an easy way to experiment with these relationships. Enter a foreground color and background color, then inspect the APCA Lc result together with the WCAG 2 contrast ratio.

APCA Lc

Perceptual lightness contrast with polarity.

WCAG 2 Ratio

Relative luminance contrast expressed as a ratio.

Typography Size + Weight

Important factors for practical readability.

APCA vs WCAG 2 Contrast Ratio

APCA and WCAG 2 contrast ratio should not be treated as two versions of the same calculation. They are different models with different outputs and different design interpretations.

WCAG 2 contrast is based on the relative luminance of two colors. For WCAG 2.1 and WCAG 2.2, the familiar Level AA requirement for normal text is a minimum contrast ratio of 4.5:1, while large text has a minimum of 3:1. WCAG AAA uses higher thresholds. These requirements remain important when you are evaluating conformance to current WCAG 2.x success criteria.

APCA instead produces an Lc value intended to better represent perceived contrast for readability. It incorporates polarity and has been designed with text size and weight considerations in mind.

The practical lesson is that a designer should not simply replace every WCAG ratio with an APCA number. If your project has a WCAG 2.1 or WCAG 2.2 compliance requirement, evaluate the applicable WCAG success criteria directly. APCA can be used as an additional perceptual design tool to improve typography and color decisions.

WCAG 2 Contrast

  • Uses a contrast ratio.
  • Common results range from 1:1 to 21:1.
  • WCAG 2.x uses defined AA and AAA thresholds.
  • Useful for current WCAG 2.x conformance testing.
  • Does not express polarity in the result.

APCA Contrast

  • Uses perceptual Lc contrast.
  • Communicates contrast polarity.
  • Designed around readability and perception.
  • Considers typography-related factors.
  • Useful for modern color and type design exploration.

For the official WCAG 2 contrast requirements, see the W3C Understanding Contrast Minimum.

Is APCA Part of WCAG 3?

APCA is closely associated with the development and discussion surrounding future accessibility guidance, including WCAG 3. However, it is important to describe its status accurately. The current WCAG 3 working draft does not define a finalized contrast algorithm and explicitly indicates that the contrast measure is still being determined.

Therefore, it is better to describe APCA as an emerging perceptual contrast model associated with WCAG 3 discussions rather than saying that APCA is already the final mandatory WCAG 3 contrast standard.

This distinction matters for developers, accessibility specialists, agencies, and organizations that publish accessibility statements. Current WCAG 2.x conformance should continue to be evaluated according to the applicable WCAG 2.x requirements.

You can review the latest information directly through the official W3C WCAG 3 working draft.

How the APCA Contrast Checker Works

The workflow is straightforward. Start with two colors: a foreground color representing the text and a background color representing the surface behind it. These can be entered using common web color formats such as HEX, RGB, or HSL depending on the interface.

The checker then evaluates the relationship and displays the APCA Lc result. The same color pair can also be evaluated using the WCAG 2 contrast ratio, allowing you to see both measurements together.

The preview is especially useful because numerical values do not tell the entire story. A color combination may look acceptable for a large heading while becoming less comfortable when reduced to small body text. Testing the actual typography makes the result more meaningful.

  1. Choose a text color. Select the foreground color used for your heading, paragraph, button, label, navigation item, or other text.
  2. Choose a background color. Enter the surface, page background, card background, button background, or other color behind the text.
  3. Review the APCA Lc value. Look at the perceptual contrast result and its polarity.
  4. Compare the WCAG 2 ratio. Check how the same pair performs under the traditional relative-luminance contrast model.
  5. Preview typography. Test different text sizes and weights instead of judging only from the color swatches.
  6. Adjust the colors. If the contrast is weak, modify the foreground, background, font size, font weight, or component treatment.

APCA Contrast for Dark Mode

Dark mode is one of the strongest use cases for perceptual contrast testing. A typical dark interface may use a near-black background, a dark-gray surface, medium-gray secondary text, bright primary text, and one or more saturated accent colors.

The challenge is that simply making text brighter does not automatically create the best reading experience. Very high contrast can sometimes feel harsh, while insufficient contrast can make paragraphs, metadata, placeholders, and navigation labels difficult to read.

APCA's polarity-aware approach makes it useful for exploring the difference between light-on-dark and dark-on-light text. When designing a dark theme, test the actual combinations used by your interface instead of assuming that one contrast value works for every component.

SECONDARY TEXT Dark Mode Test real typography instead of color alone. Contrast layers

APCA for Web Designers

Web designers can use APCA during the color-system stage, before the final interface is built. Start with your brand colors and identify which colors will be used for text, surfaces, borders, icons, buttons, and interactive states.

A common mistake is to create a palette based entirely on visual appearance. A color may look excellent inside a design file but fail when used as small text on a similarly bright background. Accessibility testing should therefore happen while the palette is being constructed, not only after development.

You can also combine APCA testing with the other color tools available on BestColorPicker. For example, use the Color Picker to identify a color, the Color Wheel to explore relationships, the Color Harmony Finder to build coordinated palettes, and then use the APCA checker to investigate text readability.

APCA for Developers

Developers can use perceptual contrast testing when implementing CSS variables, design tokens, component libraries, Tailwind themes, UI frameworks, and responsive interfaces. A color token should not be considered complete simply because it has a HEX value. Its intended usage should also be documented.

For example, a design system might define separate tokens for primary text, secondary text, muted text, surface backgrounds, elevated surfaces, borders, links, focus indicators, success states, warning states, and error states.

Each token combination should be tested according to its actual purpose. Body text needs a different evaluation from a large display heading. A decorative accent is different from a button label. A border is different from an icon that communicates status.

Developers working with modern color spaces can also use BestColorPicker's OKLCH Color Picker, HEX to OKLCH converter, RGB to OKLCH converter, and Color Difference Calculator as part of a broader color workflow.

APCA and Typography: Why Font Size Matters

Contrast does not exist independently of typography. A large, heavy headline is visually different from a small, thin caption even when both use exactly the same foreground and background colors.

Font size affects the spatial characteristics of letterforms. Font weight changes the amount of visual information presented by each character. A light 14px font can therefore behave very differently from a bold 32px heading.

This is one of the reasons perceptual contrast models are useful when making design decisions. Instead of treating the color pair as the only variable, you can evaluate the color together with its intended typographic role.

When using the APCA Contrast Checker, test your most important text styles separately. At minimum, consider display headings, section headings, body text, navigation labels, button text, metadata, captions, form labels, placeholder text, and disabled or secondary content.

APCA Contrast and Color Blindness

Contrast and color vision accessibility are related but they are not identical problems. A color combination can have strong lightness contrast while still using hue as the only method for communicating information.

For example, an interface should not communicate "success" only through green and "error" only through red. Add text, icons, patterns, labels, or other non-color indicators where the meaning matters.

BestColorPicker also provides a Colorblind Palette Checker that can be used alongside APCA testing. First evaluate whether your text has adequate contrast, then check whether the palette remains distinguishable for users with different forms of color vision deficiency.

APCA for Design Systems and Brand Colors

Brand colors often create accessibility challenges because marketing palettes are selected for identity rather than readability. A bright brand color may work beautifully for a logo or illustration but become unsuitable as paragraph text.

The solution is not necessarily to abandon the brand color. Instead, create a functional color scale around it. Keep the original brand color for appropriate visual roles and develop darker or lighter variants for text, backgrounds, borders, hover states, and other interface components.

The Color Tint Generator can help create lighter variations, while the Color Mixer can help explore blended color relationships.

For more complex palettes, use the Color Library to explore color references and then validate important text combinations with the APCA Contrast Checker.

APCA Contrast for Accessibility Audits

Accessibility audits should examine real components rather than isolated colors. A webpage may contain dozens of combinations: primary text on the page background, secondary text on cards, links on white surfaces, buttons on brand colors, badges on colored backgrounds, navigation states, form controls, alerts, tables, and data visualizations.

Start by identifying the combinations that users encounter most often. Prioritize body copy, headings, interactive controls, form labels, navigation, error messages, important status information, and content that users need to complete a task.

After identifying the combinations, evaluate them using the applicable accessibility requirements. For WCAG 2.x projects, use the current WCAG contrast criteria and supplement them with APCA where perceptual readability analysis is useful.

W3C's guidance explains that WCAG 2.2 Success Criterion 1.4.3 requires a minimum 4.5:1 contrast ratio for normal text and 3:1 for large text, with specific exceptions. See the W3C contrast documentation for the normative context.

Common APCA Contrast Testing Mistakes

Using APCA as a simple replacement for WCAG 2

APCA and WCAG 2 contrast ratio answer related but different questions. If a project requires WCAG 2.1 or WCAG 2.2 conformance, do not replace the applicable WCAG tests with an APCA number.

Testing colors without testing typography

A color pair should be considered in the context where it is actually used. Test headings, paragraphs, buttons, labels, navigation, captions, and other text styles at their real sizes and weights.

Ignoring polarity

Dark text on a light surface and light text on a dark surface should not automatically be assumed to provide an identical reading experience simply because the colors have a similar luminance separation.

Checking only the brand color

Accessibility problems often occur in secondary colors: muted gray text, disabled states, placeholder text, pastel badges, low-contrast links, and subtle borders. Test the entire component system.

Using color as the only information channel

Contrast testing does not solve every accessibility problem. Color should not be the sole method of communicating meaning, state, errors, warnings, or successful actions.

Assuming WCAG 3 is already finalized

WCAG 3 remains under development. The current W3C draft says the contrast measure is still being determined, so APCA should be described accurately as an important perceptual contrast model under discussion rather than a finalized WCAG 3 conformance requirement.

APCA Contrast Checker vs Traditional Contrast Checker

A traditional contrast checker is still extremely useful. WCAG 2 contrast ratios remain an important part of accessibility workflows, especially when a website is being evaluated against current WCAG 2.1 or WCAG 2.2 requirements.

The APCA Contrast Checker adds another perspective. It lets designers investigate perceptual contrast and compare the result with the conventional ratio for the same colors.

If you are starting with a new palette, you can use the Color Contrast Checker for traditional WCAG-style ratio testing and then use the APCA tool for an additional perceptual analysis.

01 Pick

Find your foreground and background colors.

02 Compare

Check APCA Lc and WCAG 2 ratio together.

03 Preview

Test real typography and interface states.

04 Improve

Adjust colors, type size, weight, or hierarchy.

Best Practices for Better Color Contrast

How to Improve a Low APCA Contrast Result

If your APCA result is weaker than intended, you have several design options. The first is to increase the lightness difference between the text and its background. A darken-or-lighten adjustment is often enough for body text.

Another option is to modify the typography. A larger or heavier font may have a different readability requirement from small, thin text. However, typography should never be manipulated solely to hide an accessibility problem when a straightforward color correction would produce a better result.

You can also change the surface behind the text. For example, instead of placing gray text directly over a bright brand color, use a neutral surface and reserve the brand color for a border, icon, accent, or larger heading.

When working with a design system, avoid fixing individual components one by one if the same color token is used everywhere. Correct the underlying design token and retest all components that depend on it.

APCA for Websites, SaaS Apps, and Mobile Interfaces

APCA testing is useful across many digital products. Website designers can use it for navigation, hero sections, blog content, landing pages, forms, and calls to action. SaaS developers can apply it to dashboards, data tables, settings pages, notifications, account areas, and dark-mode interfaces.

Mobile app designers can also use perceptual contrast thinking when building compact interfaces where typography is often smaller and screen conditions vary. The goal is not simply to produce a good-looking palette but to create an interface that remains readable and understandable.

E-commerce interfaces have another challenge: product imagery, badges, pricing, promotional labels, discounts, and buttons often compete for attention. Good contrast and a clear hierarchy help users identify important information without making every element visually aggressive.

APCA and Modern Color Spaces

Modern color workflows increasingly use perceptual color spaces such as OKLCH because they make certain color adjustments more intuitive. OKLCH is particularly useful for creating lightness and chroma variations while maintaining a more consistent perceptual structure.

APCA and OKLCH solve different problems, so they should not be confused. OKLCH is a color representation and manipulation space. APCA is a contrast assessment method. You can use both in a design workflow: construct and adjust a palette using an appropriate color space, then evaluate important foreground/background combinations using contrast analysis.

BestColorPicker provides several related conversion tools, including OKLCH to RGB, OKLCH to HEX, HSL to OKLCH, LAB to HEX, and HEX to LAB.

Why Perceptual Contrast Matters for AI and Design Automation

Modern design workflows increasingly use AI to generate websites, interfaces, palettes, illustrations, and component systems. AI can produce visually attractive color combinations very quickly, but visual attractiveness does not automatically guarantee accessibility.

A strong accessibility workflow therefore needs measurable checks after generation. AI can propose a palette, while contrast tools can evaluate how that palette behaves in real UI contexts.

This is particularly important for automatically generated design tokens. An AI system may select a muted gray because it looks sophisticated, but that gray could become difficult to read when used as small text on a light background.

APCA provides another useful signal for these workflows because it encourages consideration of perceived text contrast rather than relying exclusively on a traditional ratio.

Who Should Use an APCA Contrast Checker?

Frequently Asked Questions About APCA Contrast

What is an APCA Contrast Checker?

An APCA Contrast Checker evaluates a foreground and background color using the Accessible Perceptual Contrast Algorithm and reports an Lc lightness-contrast result. It can also be used alongside a traditional WCAG 2 contrast ratio for comparison.

What does APCA stand for?

APCA stands for Accessible Perceptual Contrast Algorithm. It is a perceptual contrast model designed to predict readability contrast for digital displays.

What is APCA Lc?

Lc represents APCA lightness contrast. It communicates the strength and polarity of perceptual contrast between foreground and background colors.

Is APCA the same as WCAG contrast ratio?

No. APCA and WCAG 2 contrast ratio are different contrast models with different calculations and outputs. WCAG 2 uses a relative-luminance contrast ratio, while APCA reports perceptual lightness contrast.

Can I use APCA instead of WCAG 2?

Not automatically. If your project requires WCAG 2.1 or WCAG 2.2 conformance, you should evaluate the applicable WCAG 2.x requirements. APCA can provide additional perceptual insight during design and accessibility work.

What APCA score is good for body text?

APCA guidance commonly discusses Lc values around 75 or higher for body-text-oriented use, with stronger values often preferred. However, APCA guidance is connected to text size, weight, and polarity, so there is no single number that should be treated as a universal answer for every text style.

Does APCA work for dark mode?

Yes. APCA is particularly useful for investigating polarity because it distinguishes dark text on light backgrounds from light text on dark backgrounds. This can make it valuable when designing and reviewing dark interfaces.

Does APCA consider font size?

APCA's broader readability guidance considers text size and weight because typography affects perceived readability. A color pair should therefore be evaluated in the context of the actual text style being used.

Is APCA required by WCAG 2.2?

No. WCAG 2.2 uses its established contrast requirements rather than requiring an APCA Lc score. APCA can be used as an additional perceptual design and readability analysis.

Is APCA the final WCAG 3 contrast algorithm?

WCAG 3 is still under development, and the current W3C working draft states that the contrast measure is still being determined. APCA is an important contrast model associated with WCAG 3 research and discussion, but it should not currently be described as a finalized WCAG 3 requirement.

Can APCA be used for websites and apps?

Yes. APCA is designed around contrast and readability on self-illuminated digital displays, making its concepts relevant to websites, SaaS applications, dashboards, mobile interfaces, design systems, and other screen-based products.

Should I check color blindness separately?

Yes. Contrast testing and color-vision testing address different accessibility concerns. Use sufficient contrast and avoid relying on color alone to communicate important information.

Can I use HEX colors with an APCA checker?

Yes. HEX is one of the most common ways to specify web colors. The APCA Contrast Checker on BestColorPicker allows color values to be entered and evaluated so you can test practical CSS color combinations.

Build a Complete Accessible Color Workflow

An effective color-accessibility workflow does not depend on one tool. Start by finding or selecting colors, then build relationships between them, convert values when needed, test contrast, and finally review the colors in realistic interface components.

BestColorPicker provides a connected collection of color utilities that can support this workflow. Use the Color Picker to identify colors, the Image Color Picker to extract colors from images, the Color Harmony Finder to explore palette relationships, and the Color Contrast Checker for WCAG-style contrast ratios.

Then use the APCA Contrast Checker to examine perceptual contrast and compare how the same pair behaves under APCA and WCAG 2.

READY TO TEST YOUR COLORS?

Check APCA Contrast Before You Ship Your Design

Test foreground and background colors, inspect APCA Lc, compare WCAG 2 contrast, and preview your typography before publishing a website, app, dashboard, or design system.

Check APCA Contrast Now

Useful Accessibility Resources

For authoritative accessibility information, review the W3C Web Accessibility Initiative, the WCAG 2.2 specification, and the current WCAG 3 working draft.

For APCA-specific technical background and documentation, see the APCA documentation repository. The APCA documentation explains the perceptual contrast approach, polarity, typography-related considerations, and the broader reasoning behind the model.

The most important principle is to use contrast measurements as part of a broader accessibility workflow. Good color accessibility combines measurable contrast, readable typography, meaningful hierarchy, clear interaction states, and communication methods that do not depend on color alone.