Accessibility Myths in Digital Design: Let’s Set the Record Straight

Accessibility in design goes beyond compliance checklists. Let’s debunk common myths, from who accessibility is for to what WCAG really means, and uncover how true accessibility empowers users across all experiences.

On top and right there's a bold heading that states: "Accessibility Myths in Digital Design: Let's Set the Record Straight".

Accessibility. It’s one of those words that gets thrown around in the design world like confetti. Everyone talks about it, but when it comes to actually doing it? Let’s just say things can get… messy (?).

Some folks think it’s just about making things easier for a small group of people, like 1% of the population—we already shared in previous posts that this group is indeed made by 15% of the world population. Others assume checking a few boxes or turning some parameters on or off means “Mission Accomplished.” And don’t even get me started on the debates over font sizes and color contrasts.

But here’s the deal: Accessibility isn’t about being perfect. It’s about being thoughtful and inclusive—and that’s good for everyone. Let’s bust a few myths together, shall we?


Myth #1

“Accessibility Is Only for People with Disabilities”

You’ve probably heard this one. People act like accessibility is a niche thing for people with permanent disabilities. But here’s the truth: accessibility is for everyone.

Think about it:

• Ever tried using your phone with one hand while holding a coffee (or a screaming baby)? Situational disability.

• Gotten eye surgery and couldn’t see properly for a day? Temporary disability.

• Stuck using a crummy touchscreen at an ATM (who even uses these still...)? Yeah, that’s accessibility too.

It’s not just about wheelchairs and screen readers—it’s about making life easier for anyone who interacts with your design.

Image illustrating a wheelchair sign and a computer that will have a screen reader tool opened. On the right a bold heading that states: "It's not just about wheelchairs and screen readers".

Myth #2

“I Took a Course, So I’m an Accessibility Guru Now!”

Oh, you took a course? That’s cute. Look, I’m 100% not knocking learning—it’s an amazing and super valuable first step. However, accessibility isn’t something you just “finish” like a Netflix series.

The real challenge? Putting that knowledge into action. A lot of people go, “I used this tool, so my design is accessible!” But then the actual users—you know, the people you’re designing for—find it confusing or unusable.

Accessibility is like cooking: You can have all the ingredients, but if you don’t follow the recipe (or taste-test it along the way), you’re not serving anything edible.

Myth #3

“WCAG Guidelines Are the Law”

Ah, WCAG—the holy book of accessibility. Don’t get me wrong, it’s super useful—as is reading the entirety of the guidelines, not just the summary. Oh and here’s the thing: WCAG guidelines are what they say—guidelines.

For example, ever heard the rule “all text must be at least 16px”? Not true. Smaller text is fine if you give people the option to zoom or adjust it. It’s about flexibility, not rigid rules. Of course there are limits: if you're going to write something with 4px, probably it's because it's not that important so, why bother having it?

Accessibility isn’t a game of Simon Says. It’s about understanding the why behind the guidelines and applying them thoughtfully.

Myth #4

“If the Color Contrast Passes, It’s Accessible”

This one is amazing. People run their designs through a contrast checker, get the green light, and call it a day. But did you know those tools aren’t perfect?

Yeah, even WCAG’s contrast rules have been questioned. They’re a good starting point, but they don’t cover everything. For example, take the classic case of black text on an orange background. The algorithm will confidently tell you black has better contrast, but most people find white text much easier to read in this scenario. Why? Because human vision is complex, and the current WCAG 2 contrast algorithm doesn’t account for things like font weight, size, or specific font choices—all of which dramatically impact readability.

The good news? WCAG 3.0 (still in working draft) is bringing a new sheriff to town: the Accessible Perceptual Contrast Algorithm (APCA), developed by Andrew Somers—really recommend reading a lot about all of this. It's mindblowing. Unlike its predecessor, APCA is based on actual human vision research. In fact, it often recommends the exact opposite of what WCAG 2 might tell you—like white text on orange instead of black.

This shift highlights something crucial: contrast is not one-size-fits-all. What works for one user can be a nightmare for another. It’s not just about passing or failing some rigid ratio; it’s about making thoughtful, situational design choices that meet real user needs.

And let’s not forget dark mode—it’s everywhere now, and it only makes contrast decisions trickier. As designers, we can’t rely on outdated tools or “universal” guidelines. We’ve got to test, adjust, and think beyond the algorithm.

Bottom line: Don’t rely on tools alone. Test your designs with real people to see if they actually work.

An image comparing the standards applied to colour contrasts using WCAG 2 and APCA. On the left we can see an orange button with a white label failing in contrasts using WCAG standards but passing on APCA and real perception standards. On the right, an orange button with a black label passing on WCAG standards and failing at APCA and real percetion standards.
The difference in applying the WCAG standards vs APCA standards

Accessibility Isn’t Just About “Following the Rules”

Here’s the kicker: Accessibility isn’t just about big fonts, bold colors, or checking boxes. It’s about giving people options to use your design in a way that works for them.

For instance:

  • If someone's blind, they don't care about your color palette. They need your website to be prepared for a screen reader that should work flawlessly.
  • If someone's colourblind, it's not just about contrast—it's about making sure critical info isn't colour-dependent (like a red "error" message).
  • If someone can't use a mouse, they need keyboard navigation that doesn't make them want to throw their laptop out the window.

At its core, accessibility is about empathy. It’s about saying, “Hey, I see you. Let me make this easier for you.”

So, How Do We Get It Right?

Here are a few tips to level up your accessibility game:

  1. Test with real people. Accessibility checkers are great, but they're no substitute for actual humans. Accept feedback and learn from it.
  2. Think beyond the guidelines. WCAG is a starting point, not the finish line.
  3. Give people control. Let them adjust text sizes, colour settings, or navigation options to suit their needs.

Let’s Make Accessibility a Priority

Here’s the truth: Accessible design isn’t just a nice-to-have. It’s what makes your product better for everyone—and it shows your audience you actually care.

At Mistaek, we’re all about creating designs that work for real people, in real situations. We're focused on that. So, if that sounds like the kind of vibe you’re into, let’s chat.

Subscribe to Mistaek Blog

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.
jamie@example.com
Subscribe