Checking Color Contrast on OLED and Mini-LED Displays

Checking Color Contrast on OLED and Mini-LED Displays

A WCAG contrast ratio is arithmetic. It compares the relative luminance of the two color values you enter, so #767676 on white returns the same ratio on a phone, a laptop and a projector. What changes from screen to screen is how that pair looks: OLED panels switch pixels fully off, mini-LED backlights dim in zones, wide-gamut panels push saturation, and battery and ambient-light features shift brightness and white point while you work.

That gap is why a pair can feel comfortably readable on a flagship phone and strained on a dim laptop while the badge never moves. Each section below covers one display, the iPhone 17 Pro, MacBook Pro M4, Samsung Galaxy S25 and Dell XPS 16, with its panel facts and the settings worth switching off before you judge a color by eye. The ratio stays the deciding number on all four; the device notes explain why your eyes may disagree with it.

Checking Contrast on the iPhone 17 Pro's Super Retina XDR Display

Every pixel on the iPhone 17 Pro's Super Retina XDR display is its own tiny light source, and that single fact changes how dramatic a passing dark-mode pair looks without changing a single digit this tool calculates. Apple rates the panel at a 2,000,000:1 typical contrast ratio,¹ twice the figure it quotes for the mini-LED MacBook Pro display, because an OLED panel can turn individual pixels off entirely rather than merely dimming a zone behind them. That physical difference matters for how a design feels on this phone. It has no bearing on the WCAG relative luminance formula above, which only ever sees the two color values you typed, never the technology rendering them.

Specifications¹

Why OLED's true black makes a passing ratio look more dramatic

An LCD panel, mini-LED backlight or not, always leaks some light through a black pixel, because a shutter layer is blocking a light source that never fully switches off. OLED works differently: each subpixel is its own emitter, so telling a pixel to show black means telling it to stop emitting light at all.²

No backlight means zero light leaves a black pixel

On the iPhone 17 Pro, a background you set to pure black renders as genuinely zero light output at that pixel, not a very dim gray standing in for black. Pair that with a light foreground color and the physical jump in brightness between the two is about as large as a screen can produce, which is exactly why dark-mode interfaces tend to look their most striking on OLED hardware. Designers who preview a dark palette exclusively on an iPhone can walk away with an inflated sense of how much contrast margin their colors actually carry.

None of that changes which pairs actually clear AA or AAA, though. A foreground and background sitting at 4.6:1 stay at 4.6:1 whether the black in that pair is a true OLED off-state or a backlit LCD's dark gray, because the formula works from the colors you specified, not from the physics of how a specific panel reproduces them.

The contrast ratio math never touches pixel emission physics

That separation is worth internalizing before you ship a design based purely on how it looks on your own iPhone. Relative luminance is calculated from the sRGB values in your design file,³ independent of gamma correction, panel technology, or how bright a given screen's backlight happens to be. Two designers holding the same hex codes get the same ratio whether one is staring at this OLED panel and the other at a decade-old office LCD.

If a pair looks borderline on a dim office monitor but gorgeous on this phone, the honest number is the one this tool reports, not the one your eyes are telling you on the most flattering screen in the room. Trusting the ratio over any single screen's rendering is what keeps a design decision consistent across every device it eventually ships to.

A 3000-nit outdoor peak, and why brightness cannot rescue a bad ratio

Apple rates the iPhone 17 Pro's display at up to 3000 nits in outdoor peak brightness mode, roughly three times the sustained brightness most laptop screens reach even at their maximum setting. That headroom exists specifically to fight ambient sunlight washing out the screen, not to compensate for a color pair that was already too close together before brightness was ever a factor.

Outdoor peak brightness only helps if your ratio already passes

That extra brightness headroom helps a passing pair stay legible in direct sunlight, where ambient light can otherwise wash out a screen entirely,⁴ but it cannot rescue a pair that fails the ratio check in the first place. Pushing a display brighter raises both the foreground and background proportionally, which does very little to widen the gap between them if that gap was already too narrow at the color level.⁵

A red-on-orange pair that scores 2.1:1 indoors will still read as red-on-orange at 3000 nits outdoors, just a more vivid version of the same illegible pairing. Judge the ratio the same way regardless of which brightness mode is active, since a bright screen can only ever make a passing pair more comfortable, never turn a failing one into a legible one.

Checking Contrast on the MacBook Pro M4's Liquid Retina XDR Display

A mini-LED backlight sits behind every panel Apple ships in the current MacBook Pro M4, and it changes what a passing contrast badge looks like without changing a single number this tool reports. The 14.2-inch Liquid Retina XDR display drives up to 1000 nits sustained and rates a 1,000,000:1 contrast ratio on its own spec sheet,¹ figures that describe the screen's own light output, not the mathematical relationship between two colors you type above. Reading a WCAG result on this specific panel means separating two things that look related but are not: how bright and dark this backlight can go, and how far apart your foreground and background sit in relative luminance. The second number is the only one that ratio ever measures.

Specifications¹

How mini-LED local dimming changes what a passing ratio looks like

Local dimming means the backlight behind this display is not one uniform sheet of light.² Instead, independent zones of mini-LEDs can dim or shut off in areas where the image calls for black, letting the panel approach the deep, uniform darkness normally reserved for OLED while still using an LCD layer up front.

Local dimming boosts perceived contrast without touching your numbers

When your background color sits near black and a dimming zone underneath it drops close to off, the physical light leaving that part of the screen falls far below what a fixed backlight would allow. Your eye reads that as a bigger jump between foreground and background than the same hex values would produce on a MacBook without local dimming. Crucially, none of this touches the math above. The WCAG relative luminance formula runs entirely on the RGB values you entered,³ so a pair that scores 4.6:1 here scores exactly 4.6:1 whether it renders on this display, a decade-old office monitor, or a printed swatch under daylight.

That gap between the reported number and the felt impression is worth naming rather than ignoring. A badge that just clears AA on this screen can feel like it has more room to spare than it actually does, because the backlight is doing extra visual work the formula was never designed to credit.

Where zone-based dimming still falls short of true per-pixel control

Local dimming operates in zones, not individual pixels, so a small bright element sitting inside a mostly dark region can pull the whole zone brighter than ideal, a well documented artifact called blooming.⁴ A thin line of pale text on a near-black card can show a faint halo where the zone beneath it lifts to accommodate the bright pixels nearby.

For contrast testing specifically, that halo works in your favor rather than against it: it very slightly raises the effective brightness right around your text, never lowers it. Still, the safest habit is to treat this tool's number as the one that travels with your design, and treat the MacBook's own rendering as a preview of how forgiving that number will feel to actual readers.

True Tone and why it is worth switching off before you judge a color

True Tone is switched on by default across every current Mac, and it continuously adjusts the display's white point to match the ambient light in the room.⁵ Under warm indoor lighting, whites and light grays pick up a subtle amber cast; under cooler light, they shift the other way, all without you changing a single setting yourself.

What True Tone actually shifts, and what it leaves alone

Because True Tone changes the white point the panel renders, not the pixel values your operating system sends to it, it can make a passing pair look slightly warmer or cooler than the hex codes above would suggest on a color-managed reference display. A background you typed as pure white might render with a faint amber tint an hour before sunset, purely because the ambient sensor decided the room warranted it.

The contrast ratio itself is immune to this. WCAG's formula works from the sRGB values in your design file, not from whatever adaptive tint a specific screen happens to be applying at the moment someone looks at it. If you are picking a final color for a design system rather than just glancing at how it feels on your own laptop, open Control Center and turn True Tone off first, so the swatch you are judging matches the values you are about to ship.

Checking Contrast on the Samsung Galaxy S25's AMOLED Display

Out of the box, the Samsung Galaxy S25's screen mode is set to Vivid, and that single settings toggle can make a color pair that just clears WCAG AA look noticeably punchier, or a failing pair look deceptively close to passing, without touching a single value this tool reports. Samsung's own support documentation describes Vivid as optimizing the color range, saturation, and sharpness of the display, while the alternate Natural mode renders a softer, less saturated tone. The Dynamic AMOLED 2X panel underneath either mode is capable of up to 2600 nits peak brightness.¹ Whichever mode is active, the contrast ratio calculation above only ever sees the raw hex values you typed, not whichever version of them Vivid mode is currently pushing further.

Specifications¹

Vivid mode's saturation boost and what it does to your passing pair

Samsung ships every Galaxy S25 with Vivid mode active by default, and switching between it and Natural mode is a two-tap trip through Settings rather than something most owners ever touch. Most people never open that menu at all, which means the majority of your audience is viewing your design through whatever Vivid mode is doing to it right now.

What Vivid mode actually changes on screen

Samsung describes Vivid mode as optimizing color range, saturation, and sharpness,² which in practice means colors on screen render more intensely than the flat sRGB values a designer specified. A background and foreground pair that scores 4.6:1 in this tool can look like it has noticeably more separation on a Vivid-mode Galaxy S25 than the same pair would on a calibrated reference monitor, purely because the phone is pushing extra saturation into the render path.

This matters most for pairs sitting close to a pass or fail boundary rather than pairs that already clear a tier by a wide margin. A borderline pair that reads as barely-there on a calibrated monitor can look convincingly separated on a Vivid-mode screen, which is exactly the scenario where trusting your eyes on this one phone instead of the ratio above leads a team to ship a color that fails everywhere else.

Switching to Natural mode for an accurate preview

If you want a more accurate sense of how a color pair will look to someone viewing it on an sRGB-calibrated screen, switch this phone to Natural mode before judging it, following Samsung's own guidance that Natural renders a softer, less saturated tone closer to the source colors.² The toggle lives under Settings, Display, Screen mode, and switching it takes a few seconds compared to the time it costs to second-guess a design decision later.

That single toggle strips out the saturation boost, leaving you with a closer approximation of how the same pair reads on a typical laptop or desktop monitor. Since most of your audience won't be viewing your design through Vivid mode specifically, treating Natural as your baseline avoids designing a palette that only looks correct on this one phone's default setting.

2600-nit peak brightness and where it actually applies

Samsung's spec sheet lists up to 2600 nits of peak brightness for the Galaxy S25 series, a figure reserved for a small portion of the screen in high-contrast HDR content rather than the sustained brightness the whole display runs at for everyday use.³ It is the kind of number that reads impressively in a spec comparison while describing a condition your browser tab will rarely, if ever, trigger.

Peak brightness is not the same as sustained everyday brightness

A typical web page or app interface, including the one your contrast pair ends up in, runs far below that 2600-nit ceiling, closer to the phone's adaptive brightness setting for the room you're standing in. Treating the peak HDR figure as a proxy for how legible your text will be during normal browsing overstates how bright the screen is actually behaving most of the time.⁴

For a realistic sense of how a color pair reads on this device, judge it at the brightness level you'd actually use to read a web page, not the number printed on the spec sheet, and remember that the ratio itself never changes regardless of which brightness the screen happens to be running at when you look.⁵

Checking Contrast on the Dell XPS 16 (2026) Tandem OLED Display

Dell's revived XPS 16 for 2026 ships with an optional Tandem OLED display that stacks two light-emitting layers to reach full sRGB and DCI-P3 color coverage, a genuinely different achievement from the contrast ratio this tool calculates above. Independent testing measured its SDR brightness peaking around 364 nits,¹ more modest than the mini-LED and OLED phone displays covered elsewhere on this page, and Dell's own Optimizer software can quietly lower that brightness further to save battery. None of that changes the math. WCAG's relative luminance formula reads only the two colors you typed, leaving color gamut and screen brightness as two separate stories worth understanding on their own.

Specifications¹

Tandem OLED's full P3 and sRGB coverage, and why gamut is not contrast

Color gamut describes the total range of colors a display can physically reproduce, and Tandem OLED's two stacked emissive layers let the XPS 16 cover both the sRGB space most web content targets and the wider DCI-P3 space in full. That's a genuinely impressive spec for a laptop panel, and it's worth understanding exactly what it does and doesn't promise about the contrast ratio you're about to check.

What Tandem OLED changes: color coverage, not the luminance math

A wider gamut means this screen can show more saturated reds, greens, and blues than a narrower-gamut panel can, which matters enormously for a designer choosing brand colors but has nothing to do with how a specific foreground and background pair relate to each other in brightness. Two colors that sit inside sRGB, the space most web design targets, render identically in terms of relative luminance whether the display underneath happens to cover 100% of that space or only 90%, because the values themselves are unchanged either way.

It helps to think of gamut and contrast as answering two entirely different questions.² Gamut asks how far outside a reference color space this particular screen can reach; contrast asks how far apart two specific colors already sit within whatever space they were defined in, a question the panel underneath has no way to influence. Keeping those two questions separate in your head avoids the common mistake of assuming a more capable screen automatically produces a more accessible result.

Full DCI-P3 coverage does not raise or lower a WCAG score

Where gamut does matter is upstream of this tool, at the moment you pick a color in the first place. A designer working exclusively on a wide-gamut screen can accidentally choose a color that looks great locally but clips or shifts on a narrower-gamut monitor elsewhere, an entirely separate risk from a contrast failure. That risk sits well before contrast checking even enters the workflow, since a clipped color still has a defined hex value the ratio formula can evaluate correctly.

The ratio this tool reports stays valid regardless of which gamut produced the screenshot you're looking at, since it operates on the sRGB numbers in your file, not on the physical light the XPS 16's OLED layers are capable of producing. A pair checked on a narrow-gamut office monitor and the same pair checked on this laptop's wide-gamut panel return the identical number every time.

Dell's Battery Extender and why auto-dimming can undercut a passing badge

Dell Optimizer, the XPS 16's included utility, ships with a battery extender feature that lowers screen brightness on the fly to stretch battery life, independent of anything happening in the browser tab you're viewing.³ It runs quietly in the background, adjusting brightness on its own schedule rather than waiting for you to reach for a keyboard shortcut.

A software brightness cut is invisible to the ratio calculation

That auto-dimming behavior can make a pair that comfortably clears AA at full brightness feel noticeably harder to read once the laptop quietly drops its backlight to conserve power, especially in Chrome or Edge windows sitting in the background while other work happens. Nobody has to trigger this manually; the utility decides on its own when the battery level or usage pattern justifies the cut.

The contrast ratio itself never registers this shift, because it operates on the hex values in your design, not on however many nits the panel happens to be emitting at that moment.⁴ If you're judging legibility on this laptop specifically, check Dell Optimizer's power profile first, since a pair that reads comfortably under a performance-focused profile can feel meaningfully dimmer once the battery extender kicks in.⁵ A quick glance at the current power mode before you approve a color saves you from chasing a legibility complaint that was never about the hex values at all.