None of these six habits will get flagged in a normal design review. Each one has survived plenty of them. Someone on the team probably defended each one out loud at some point, with a perfectly reasonable-sounding sentence: "the color makes it obvious," "the carousel looks more alive moving," "the icon is self-explanatory," "everyone knows what click here means."
Each one is also a real, named WCAG failure. Not a stylistic nitpick, not a "nice to have" - a documented success criterion with a letter grade and a number, the kind an auditor circles in red on page one of a report. And together, these six habits are one of the quietest ways a site pushes real users away without a single complaint ever being filed. Nobody emails support to say "your status badges are colorblind-hostile." They just leave, and the analytics dashboard has no field for why.
This is the list we hand clients first, before anything about scores or audits, because it's the fastest way to see how much damage small, defensible-sounding decisions can do at scale.
The Stat: WCAG Success Criterion 1.4.1 Use of Color states plainly that color cannot be the only visual means of conveying information or distinguishing an element. It's a Level A requirement - the floor, not a stretch goal. (Source: W3C Web Content Accessibility Guidelines)
Habit 1: Color-Only Status Badges
A little red dot means "overdue." A little green dot means "on track." It looks clean in a design file, and it tests well with sighted reviewers who happen to have typical color vision.
But WCAG 1.4.1 Use of Color exists precisely because color-blind users, low-vision users, and anyone viewing a screen washed out by sunlight cannot reliably tell a red dot from a green one. The rule isn't "don't use color." It's "don't use color alone." Pair the dot with a word, an icon shape, or a pattern, and the same design still looks clean - it just also works.
Habit 2: Autoplaying Carousels With No Pause
Carousels survive redesign after redesign because someone insists motion "feels premium." The trouble starts when that motion never stops, and there's no visible button to make it stop.
WCAG 2.2.2 Pause, Stop, Hide requires that any moving, blinking, or auto-updating content give the user a way to pause, stop, or hide it. Without that control, screen reader users can get the moving region re-announced mid-task, and users with attention-related or vestibular conditions lose the ability to read at their own pace. A visible pause control is a small addition that resolves the whole failure.
Habit 3: Icon-Only Buttons With No Label
A trash can icon. A gear icon. A hamburger icon. To a sighted user hovering long enough to read a tooltip, the meaning is obvious. To a screen reader user, an unlabeled icon button often announces as nothing more than "button" - no name, no role beyond the tag, no clue what it does.
This falls under the broader requirement that every interface component expose a real accessible name, not just a visual glyph. The fix costs nothing in layout: a visually hidden label or an aria-label attribute gives the same icon a name a screen reader can actually speak.
Habit 4: Vague Link Text ("Click Here")
"Click here." "Read more." "Learn more." These phrases repeat across a page like wallpaper, and in a normal reading flow, surrounding sentences carry the meaning.
But many screen reader users don't read in a normal flow - they pull up a list of every link on the page to navigate faster. When ten links all say "click here," that list is useless. WCAG 2.4.4 Link Purpose (In Context) requires that a link's purpose be determinable from its own text or its immediate context - which rules out repeated, generic phrases standing alone. "Read the full pricing breakdown" tells the same story in the same space "click here" wastes.
Habit 5: Removed Focus Outlines
Somewhere, a developer decided the default blue focus ring clashed with the brand palette and reached for outline: none. It's one line of CSS, and visually the interface looks tidier immediately.
It also erases the only way a keyboard-only user can see where they are on the page. WCAG 2.4.7 Focus Visible requires that a visible keyboard focus indicator remain available at all times - a blanket removal with nothing to replace it is a straightforward failure. The fix isn't "put the ugly ring back." It's designing a focus style that matches the brand and still meets the bar, which takes minutes, not weeks.
Habit 6: Low-Contrast Placeholder Text
Light gray text on a white input field looks minimal, modern, restrained. It's also frequently the hardest text on the entire page to read, and it tends to be exactly the text explaining what the user is supposed to type.
Placeholder text is still text, and it's still subject to the same contrast expectations as everything else on the page. Low-vision users, older users, and anyone on a phone screen in direct sunlight are the ones who quietly give up on the form rather than squint at it.
Why These Six, Together
Individually, each habit is defensible in isolation. A designer can point to a competitor doing the same thing. That's exactly what makes the pattern dangerous - none of the six trips an obvious alarm, so they accumulate across a site until the experience is genuinely hostile to a meaningful share of visitors, with no single moment anyone can point to and say "that's where we went wrong."
| Habit | WCAG Criterion | Level | Who It Blocks |
|---|---|---|---|
| Color-only status badges | SC 1.4.1 Use of Color | A | Colorblind and low-vision users who can't distinguish status by hue alone |
| Autoplaying carousels, no pause | SC 2.2.2 Pause, Stop, Hide | A | Users with attention or vestibular conditions, and screen reader users |
| Icon-only buttons, no label | SC 4.1.2 Name, Role, Value | A | Screen reader users who hear an unnamed button |
| Vague link text ("click here") | SC 2.4.4 Link Purpose (In Context) | A | Screen reader users navigating by a links list |
| Removed focus outlines | SC 2.4.7 Focus Visible | AA | Keyboard-only users who lose their place on the page |
| Low-contrast placeholder text | SC 1.4.3 Contrast (Minimum) | AA | Low-vision users and anyone in bright ambient light |
A quick self-check before you open a full audit:
- Every status indicator pairs color with a label, icon, or pattern
- Every auto-moving element has a visible pause or stop control
- Every icon-only button has a real accessible name
- Every link makes sense read on its own, out of context
- Every focusable element shows a visible focus style
- Every placeholder and body text passes a contrast check against its background
None of these fixes require a redesign. Most are a component-level change once you know which pattern to look for, and we've laid out copy-paste fixes for these exact patterns so you can patch them without reinventing anything.
If you want to know which of these six habits your own site is currently carrying, run it through our free tools and see - it takes less time than the design review that let the habit through in the first place. You can also check your own site against all six with our free tools, or if you'd rather talk it through with a person, email the team directly at experts@wcag.world and we'll help you prioritize the fixes that matter most for your users.