Picture three compact badges in a review queue: Pending, Approved and Needs review. Each has its own color and its own stripe or dot motif. The question behind patterned status badges accessibility labels is simple: does the motif carry meaning, or does it only add texture? If removing it leaves the status clear to everyone, it is decoration. If it communicates something the words do not, it is information and needs a text equivalent.
In this workflow I take a motif and companion colors from a color page’s Pattern Lab, keep a visible word on every badge, and use the 66Colorful Contrast Checker to examine the text and any required graphics against their adjacent colors. A passing pair is useful evidence, but it is not a complete accessibility audit.
Table of Contents

Patterned status badges accessibility labels start with visible words
WCAG 2.2 Success Criterion 1.4.1, Use of Color (Level A), says color cannot be the only visual means of conveying information. W3C’s technique G111 describes pairing color with pattern as one way to respond to that. For compact badges I still prefer a visible word. A reader has to learn what stripes mean, while “Pending” explains itself. The WCAG 2.2 Recommendation I am referring to is dated October 5, 2023.
Here is what the motif and colors add to each of the three badges, and what they should never replace.
Pending
The word does the work. A stripe motif in warm companion colors helps a sighted reader spot pending items while scanning a table. Any association between stripes and “in progress” is a local convention, not a universal one, so nothing may depend on it.
Approved
A quieter motif, or none at all, can suit a state that rarely needs attention. If the word “Approved” is visible, the dots or flat fill are a visual extra.
Needs review
This status often asks the reader to act, so a stronger motif can help it stand out in a long list. The phrase tells the reader what to do. Do not let the motif be the only difference between this badge and Pending.

The removal test: decorative motif or information?
Remove the motif in your head, or in the browser by switching the CSS off. If the badge still says exactly what it said before, the motif is decoration. If a reader would lose a meaning, it is informative. W3C separates images into informative, decorative and functional, recommends CSS backgrounds for purely decorative imagery, and treats information conveyed only through a CSS background image as a failure of Success Criterion 1.1.1.
| Case | Removal test | Implementation |
|---|---|---|
| Motif as CSS background | “Pending” is still understood | Keep it in CSS. Give it no accessible name. |
| Icon that repeats the word | Nothing is lost | For an img use alt=””. For a non-focusable inline SVG, hide it from assistive technology. |
| Icon that adds information | Meaning is lost | Give it an equivalent text alternative, and consider showing that information in visible text too. |
| Icon-only control | The control is the icon | Name the action, such as “Mark as approved”, not the icon’s appearance. |
When the icon adds something the text lacks
Suppose a badge reads “Needs review” and a small clock icon means the item is overdue. The word does not say that. Giving the icon a text alternative helps screen reader users, but sighted readers must also decode a symbol. Showing “Overdue” as visible text is usually clearer for everyone.
When the badge is a control
If a badge becomes a button that filters the list, the control needs a name that describes what happens when it is activated. “Show pending items” is useful. “Yellow striped badge” is not.

Build a patterned badge from a color page
The goal is a badge where the word is always readable and the motif is a bonus. Follow these steps.
- Open a color page and choose a motif from its Pattern Lab, then pick two or three companion colors. Check the motif and colors you actually see on that page before you copy anything, because my example only shows structure.
- Write the visible label first: Pending, Approved or Needs review. Keep it in real text, not in an image.
- Place the motif on the edge or ring of the badge, and put the text on a solid inner panel. This way only one color ever sits directly behind the letters.
- Leave the motif without an accessible name. It is a CSS background, so assistive technology never encounters it.
- Test the text color against the panel color, and any needed graphic against its neighbors, as described in the next section.
<span class='badge badge--pending'>
<span class='badge__text'>Pending</span>
</span>
.badge--pending {
display: inline-flex;
padding: 2px;
border-radius: 999px;
background: repeating-linear-gradient(45deg, #C98A00 0 6px, #F2D28B 6px 12px);
}
.badge__text {
padding: 2px 10px;
border-radius: 999px;
background: #FFF8E6;
color: #3A2A00;
font-weight: 600;
}
The hex values above are placeholders to show the structure. They are not a tested pairing and not taken from a specific color page, so replace them with your chosen colors and check them yourself.
Which patterned status badges accessibility labels need contrast checks?
Every badge with visible text does, and any graphic that a reader needs in order to understand the status does too. WCAG 2.2 AA asks for at least 4.5:1 for ordinary text and 3:1 for large text. Large text means roughly 24px regular or 18.66px bold, so do not assume a small badge qualifies. For required graphics and state cues, Success Criterion 1.4.11 Non-text Contrast (Level AA) asks for 3:1 against adjacent colors.
A decorative motif does not gain a 3:1 requirement just because it is visible. That is why the removal test comes first: it tells you which parts of the badge you must measure and which are ornament.
Put the badge’s actual text color in the foreground and each color that can appear directly behind the letters in the background. With the solid inner panel from the previous section, that is one pair. If you let letters cross a pattern, check every segment they touch. To check a whole set of badge and surface colors at once, the Palette Accessibility Matrix grades every pair in a palette, and the Color Palette Accessibility Audit lists safe text colors for each background.
The adjacent-color idea is easy to get wrong by eye. The CSS darkgray Lighter Than gray article walks through a calculated border example where the keyword that sounds darker is actually the one that fails against white.
What a contrast pass cannot tell you
The 66Colorful contrast tools take two colors and report WCAG results. They do not test every part of a patterned badge, and a passing pair is not a conformance certificate. Use this list as the next layer of review.
- Accessible names: confirm decorative icons are hidden or have empty alt text, informative icons have equivalent text, and icon-only controls are named by action.
- Comprehension without the motif: read the badge in grayscale or with the CSS switched off. Does the status survive?
- Rendered overlap: thin strokes, transparency and overlapping segments can change the colors that actually sit beside each other. Inspect the real rendering, not just the two solid values.
- States: hover, focus, selected and disabled versions need their own checks. For interactive badges, the Focus Indicator Checker helps with the focus ring, which is a separate requirement from text contrast.
- Color vision: a Color Blindness Simulator shows an approximation of how colors may shift. It is a design aid, not a diagnosis, and it supports the case for visible text and shape cues rather than replacing them.
Finally, treat color associations such as caution or success as context-dependent. The word on the badge removes the need to guess.
Frequently asked questions
Does a stripe pattern make a status badge accessible?
No. WCAG Success Criterion 1.4.1 allows pattern as one way to avoid relying on color alone, but a visible word such as Pending is clearer for compact badges. The pattern should supplement the label, not replace it.
Do I need an accessible name for a decorative CSS motif?
No. A purely decorative motif drawn as a CSS background should stay out of the accessibility tree. W3C recommends CSS for decorative imagery, which is why the motif should not carry its own label.
How do I treat an icon that repeats the status text?
Treat it as decorative. For an img element use empty alt text. For a non-focusable inline SVG, hide it from assistive technology so the status is not announced twice.
What should an icon-only status button be called?
Name it by the action it performs, such as Mark as approved or Show pending items. Do not describe how the icon looks, because users need to know what activating it does.
Does the motif itself need a 3:1 contrast ratio?
Not if it is purely decorative and the status is clear without it. Required graphics or state cues fall under Success Criterion 1.4.11 at 3:1 against adjacent colors.
Can I rely on one contrast result for a patterned badge?
No. A two-color result does not cover every segment, thin stroke, transparency or overlap in a rendered pattern. Check the actual colors behind the letters and inspect the badge as displayed.
Is a small badge treated as large text?
Do not assume so. Large text is generally about 24px regular or 18.66px bold, so most compact badge labels need the 4.5:1 ordinary text ratio at WCAG 2.2 AA.
Next steps
Patterned status badges accessibility labels work best when the order is fixed: write the visible status, run the removal test, then treat the motif as decoration or give it a real text equivalent. Keep text on a solid area, check the text and any required graphic against their adjacent colors, and review names, rendering and states by hand. Before your next release, take one badge from your own interface and run the removal test on it.
Related tools & resources on 66Colorful:
- Contrast Checker
- Palette Accessibility Matrix
- Palette Accessibility Audit
- Css Darkgray Lighter Than Gray
Sources and further reading
- Understanding Success Criterion 1.4.11: Non-text Contrast | WAI | W3C
- Images Tutorial | Web Accessibility Initiative (WAI) | W3C
- Decorative Images | Web Accessibility Initiative (WAI) | W3C
- Understanding Success Criterion 1.1.1: Non-text Content | WAI | W3C
- Web Content Accessibility Guidelines (WCAG) 2.2