Skip forward into hiring notes
RosterAcorn

2 color settings that change job posting text contrast

Two of the factors that affect job post text contrast are lightness (how bright the color itself is) and alpha (how transparent it is, which lets underlying colors bleed through).

  • Lightness sets the distance between text and background; the more you separate them, the higher the ratio
  • Alpha reduces contrast when lowered, because underlying colors mix into what the applicant sees
  • Set alpha to full for any text that must be read; keep transparency for decorative, wordless shapes only
  • Check every state — resting, hover, focus, visited, draft-input, disabled, error, and success — not just the default
  • Measure in sRGB, the default colour space named in IEC 61966-2-1

Why two settings decide whether your job post is readable

You are about to publish a job post. The text sits on a tinted panel, and it looks fine on your monitor. You are wondering if you should tweak the color one more time before it goes live. Two settings in your editor govern the lightness and alpha part of contrast: how light or dark the text color is, and how transparent it is. Photos, gradients and theme overlays can also make text hard to read. The contrast ratio is affected by those two dials and by the background behind the text, such as photos, gradients and overlays.

This matters more for a job post than for most pages. A careers page competes with other listings. If a sentence is hard to parse, the reader does not slow down. They leave. WebAIM explains that changing the lightness of a color will change its contrast ratio to another color. That single sentence is the whole foundation. Lightness is the first of your two settings.

The second is alpha, which is transparency. WebAIM notes that alpha, which is the opacity or transparency of a color, will also impact contrast. When you lower alpha, you are letting the layer underneath show through. WebAIM's own reasoning: reducing the alpha for an element will reduce its contrast because you are allowing an underlying color to bleed through. A gray label at reduced opacity over a photo is not gray. It is a mix of gray and whatever pixels sit behind it, and that mix is the color an applicant actually sees.

So the two settings are lightness and alpha. This post walks through each one, shows how they interact, and gives you a checklist you can run before you hit publish on any job post or careers page text.

Setting one: lightness, and what it does to your ratio

Lightness is how bright a color is, independent of its hue. A navy blue and a sky blue can share a hue family while sitting at opposite ends of the lightness scale. The ratio compares the relative luminance of the text against the relative luminance of the background behind it.

The practical rule for a job post: the more you separate text lightness from background lightness, the higher the ratio. For dark text on a light panel, darkening the text or lightening the panel raises the ratio; for light text on a dark panel, the opposite moves are needed. The opposite move — a medium gray on a medium blue — collapses the gap fast. This is why brand palettes with several mid-tone colors tend to fail contrast checks. They look sophisticated side by side in a style guide. Stacked as text on background, they are nearly the same brightness.

WebAIM's article on contrast gives you the arithmetic, and one of its cleanest observations is worth holding onto: if text and background colors are swapped, the contrast ratio remains the same. That symmetry tells you the ratio belongs to the pair, not to either color alone. You cannot evaluate your text color in isolation. You evaluate the pairing.

Two habits keep lightness honest in a careers page editor:

  • Check the pairing, not the swatch. Look at text on the exact panel it will sit on, not on white in your color picker.
  • Check every state. Hover, focus, visited, and disabled states often carry their own lightness values. A link that darkens on hover may have been fine at rest and broken on hover.

The lightness dial is also where most brand conflicts land. Designers pick a tint for its warmth. Recruiters pick text for its legibility. If those two choices pull in opposite directions, legibility wins, because the reader is the only person who matters once the post is live.

There is a second, less obvious lightness trap: text sitting on imagery. A careers page with a team photo behind a headline inherits the photo's local brightness, which changes every few pixels. Even strong text lightness can lose against a bright patch in the image. The fix is a solid backing panel or a solid color bar behind the words. Alpha over a photo is the bleed-through problem described in the alpha section, so it is not the fix.

Setting two: alpha, transparency, and the bleed-through problem

Alpha is the opacity value attached to a color. At full alpha the color is solid. At reduced alpha the color is see-through, and whatever is behind it mixes in.

Here is the part that trips people up. You pick a text color that passes a contrast check. You then lower the alpha on the text — or on a tint panel behind the text — and the checked pairing silently changes. The color you measured is no longer the color on screen. WebAIM states the mechanism plainly: reducing the alpha for an element will reduce its contrast because you are allowing an underlying color to bleed through.

Alpha hurts in three common careers-page situations:

  • Ghost buttons. A "Apply now" button with a semi-transparent fill over a hero image is a moving target. The fill mixes with the image; the label mixes with the fill.
  • Tinted cards. A card at 80% opacity over a patterned background inherits the pattern's brightness in spots.
  • Overlaid quotes. A pull quote from an employee, written in white at reduced alpha over a photo, will pass in dark areas and fail in light areas of the same photo.

The remedy is mechanical, not artistic: set alpha to full for any text that must be read. Keep transparency for decorative shapes that carry no words. If you need a softer look, soften the lightness of a solid color instead of making it transparent. That way the pairing you checked is the pairing that ships.

One more useful symmetry from WebAIM applies here too: if text and background colors are swapped, the contrast ratio remains the same. So if you flip a design — dark card on light page becomes light card on dark page — the ratio holds, provided both layers stay solid. Drop either layer's alpha and the symmetry breaks, because the underlying page color re-enters the mix.

How the two settings interact in a real job post

Lightness and alpha are not independent in practice. A designer lowers alpha to create a softer panel, then compensates by nudging text lightness darker. The text passes a quick visual check on the design tool's flat canvas. On the live page, the panel sits over a section background of a different lightness, and the pairing shifts again.

Think of it as two multiplications stacked on each other. Lightness sets the distance between your two colors as drawn. Alpha then scales how much of that distance actually survives contact with whatever is underneath. Two dials, one output: the ratio an applicant experiences.

A simple way to reason about a careers page before publishing:

  1. Fix the text and background as solids first. Choose a pairing with a comfortable margin. Do not reach for alpha yet.
  2. Add transparency only to non-text layers. Decorative rules, dividers, and shape accents can be transparent without harming words.
  3. Recheck after any layering change. Adding a gradient, a photo, or a second tint behind the text changes the effective background.

The World Wide Web Consortium's page on the contrast minimum success criterion anchors the measurement itself to a defined color space, citing IEC/4WD 61966-2-1: Colour Measurement and Management in Multimedia Systems and Equipment - Part 2.1: Default Colour Space - sRGB. If your editor lets you pick colors in another space, the same visual swatch can compute to a different ratio. The W3C page refers readers to its Understanding Success Criterion 1.4.3 guidance for other color spaces.

Practically, this means: check your colors in a tool that reports in sRGB. An sRGB-based ratio may differ from a ratio computed in another color space, so the check should use sRGB values.

Here is a compact reference for how each setting behaves when you change it:

Setting you changeDirection of changeEffect on text-to-background contrastWhere you see it in a job post
Lightness of text or backgroundIncreased separationContrast ratio increasesHeadline, body copy, button label
Lightness of text or background Decreased separationContrast ratio decreasesMid-tone labels on tinted cards
Alpha of a text layerReduced Contrast decreases, underlying color bleeds throughSemi-transparent overlays on photos
Alpha of a background layerReduced Effective background shifts, ratio moves unpredictablyGhost buttons, tinted panels

The careers page states you keep forgetting to check

A job post is not one static composition. It is a text color used across several states, each with its own lightness and alpha values pulled from your theme configuration or code. The resting state is the one you designed. The other states are the ones applicants actually touch.

Walk through these before you publish:

  • Resting text. The default pairing on the page background. This is the one people check.
  • Hover and focus. Link color and button label color often shift. Focus rings introduce a third color against a fourth.
  • Visited links. Your careers page may link out to benefits documents or an employee handbook. Visited purple can fail against a dark panel. Two dials, both working against you.
  • Error and success messages. Application form feedback inherits your theme's red and green, which may have been chosen for a light background and now appear on a tinted one.

The U.S. Department of Justice guidance on web accessibility adds a separate caution that belongs in this checklist: people who are color-blind may not have access to information when that information is conveyed using only color cues because they cannot distinguish certain colors from others. That warning sits alongside your contrast work. If your "Required field" marker is a red asterisk and nothing else, an applicant who cannot distinguish the red loses the cue entirely. Contrast gets the text read; redundancy gets the meaning across.

So a final pass on your job post should look at both problems at once: is every piece of text separated enough in lightness and alpha, and is any meaning carried only by hue? The first question is about your two color settings. The second is about the design around them.

A pre-publish checklist for job post and careers page text

Run this list on the post you are about to send out. It takes a few minutes and helps catch common lightness and alpha mistakes.

  • Text is solid, not transparent. Alpha at full for every label, heading, paragraph, and button word.
  • Background behind text is understood. Note what sits behind the text: flat color, gradient, photo, or patterned section.
  • Lightness gap is visible at a glance. Squint at the post. If the text and background blur together, the ratio is too tight.
  • All states checked. Rest, hover, focus, visited, draft-input, disabled, error, and success.
  • Photo-backed text has a solid backing. A solid panel or a solid color bar behind words, rather than transparency over an image.
  • Color space matches sRGB. Measure in the same space your checkers and browsers use.
  • No meaning carried by hue alone. Pair every color cue with a word, icon, or shape.
  • Logo and brand text exempt. WebAIM notes that logotypes, meaning text that is part of a logo or brand name, have no contrast requirement. Your logo in the header is treated differently from your job title in the listing.

That last item is a relief and a trap. Relief: you do not need to restyle your brand mark to chase a ratio. Trap: people extend the exemption to the tagline under the logo, to the section headers styled in brand color, and to the button that says "Apply now" because it uses brand color. The exemption covers the logotype itself. Your job post's functional text is not a logotype.

When the two dials will not be enough

Sometimes lightness and alpha are both correct and the text still fails for some readers. The cause is usually outside those two settings: a photo with hot spots behind the words, a gradient that crosses the lightness range, or a theme that applies a color overlay at the browser level after your values are set.

If you have fixed both dials and the text still reads weakly, change the composition instead. Move the text onto a solid panel. Replace the photo behind the headline with a flat color. Remove the gradient from the section. Composition outranks color settings when the two disagree.

Another case that sits outside the two dials: the logo lockup in your careers header, where the brand name is set as a graphic. That is the logotype exemption above, and it is the right treatment for a brand mark. It is the wrong treatment for the job title underneath it, which must behave like every other piece of functional text on the page.

One open question your sources will not settle: how much margin you should hold above the minimum ratio for a busy careers page with photos and tints. That depends on your audience and your imagery. Ask your own accessibility lead or your design system owner for the house number, and hold to it consistently across every post.

Quick answers recruiters ask before publishing

Do I have to restyle my company logo for contrast? No. WebAIM's guidance treats a logotype as exempt: text that is part of a logo or brand name has no contrast requirement. Keep the mark as designed. Apply your lightness and alpha checks to everything else on the page — job titles, requirements, button labels, form fields.

My text looks fine on my laptop. Why does it fail on a colleague's screen? Two likely causes. First, your editor may be computing color in a space other than sRGB. Second, a colleague's display brightness or a system-level dark mode may be shifting the effective background. Check on a second machine with the site in its default state.

If I swap my text and background colors, does the contrast change? No. The pairing keeps the same ratio when reversed, because the ratio describes the distance between the two colors, not their order. WebAIM states it directly: if text and background colors are swapped, the contrast ratio remains the same.

Should I lower alpha to make a heavy block of requirements text feel lighter? Not on the text itself. Lowering text alpha lets the background bleed into your letterforms, which reduces contrast in the exact place you need it. If the block feels heavy, lighten the background's lightness instead, or increase spacing. Keep alpha for decoration that carries no words.

My hiring manager wants a semi-transparent overlay on the team photo with the headline on top. What do I do? Set the overlay to a solid color at full alpha, or place the headline on a solid bar with no transparent overlay over the text. Transparency behind live text reintroduces the bleed-through problem, and the photo's brightness varies across the frame, so a pairing that passes in one spot will fail in another.

Where does color blindness fit into a contrast fix? Contrast work handles legibility. Color blindness handles meaning. The Department of Justice guidance warns that people who are color-blind may not have access to information when that information is conveyed using only color cues because they cannot distinguish certain colors from others. So alongside your lightness and alpha pass, confirm that every "required," "new," or "closed" state on the listing is labeled in words, not shown by color alone.

Sources