Your cart is currently empty!
I hate to write posts like this.
Really, I do.
Because most people in tech aren’t malicious. Most companies aren’t trying to exclude people. But intent doesn’t matter when the outcomes say otherwise.
There are patterns—things I keep seeing over and over—that quietly shout:
“We don’t actually care about accessibility.”
And that’s a problem.
Not just for users who are constantly blocked, ignored, or patronized—but also for people inside your organization who are trying to do better and need backup. They need proof points. They need to be able to say, “Look, this is what it looks like when we’re not even trying.”
So here it is. Five red flags. If these show up in your product, site, or process… it’s time for a reality check.
1. No Accessibility Statement
If you don’t have an accessibility statement on your site, you’re telling people two things:
- You haven’t thought about accessibility at all, or
- You have thought about it… and didn’t care enough to say so
An accessibility statement isn’t just a legal safety net. It’s a signal of your intent.
It tells people, “We know this matters. We’re working on it. Here’s where we stand.”
If you can’t even offer that, why should anyone believe accessibility is a priority?
2. You Rely on an Accessibility Overlay or Widget
If your solution to accessibility is a third-party widget that injects a toolbar to “make the site accessible,” you’re not solving anything. In fact, you’re probably making it worse.
Overlays don’t fix inaccessible markup.
They interfere with screen readers.
They create confusion, add clutter, and give a false sense of compliance.
They’re a band-aid on a broken leg. And worse, they send this message:
“We’re not willing to fix the real issues, so we bought this thing instead.”
That’s not innovation. That’s negligence.
3. No One Is Responsible for Accessibility
Is there someone on your team who owns accessibility? Can you name them?
If not, that’s a red flag.
Accessibility doesn’t happen by accident. It requires ownership, process, and accountability. If it’s “everyone’s job,” then it’s no one’s job.
And if you’re outsourcing it to one overworked dev at the end of a sprint cycle… you’re not doing accessibility. You’re just hoping no one notices.
4. You Don’t Include Assistive Technology Users in Testing
You can’t build an accessible product if you don’t talk to the people you’re designing for.
If your research pool never includes screen reader users, keyboard-only users, or people with cognitive or motor impairments—you’re not looking at real user experiences. You’re guessing. You’re building for a world you don’t understand.
And it shows.
Inclusive research isn’t optional. It’s foundational.
5. You Only Talk About Accessibility During Lawsuits or Launches
If accessibility only comes up when a lawsuit hits the news or you’re launching a public-facing product, that’s not a strategy. That’s PR damage control.
True accessibility work is quiet, consistent, and part of the day-to-day. It shows up in:
- Design critiques
- Code reviews
- Onboarding documents
- Performance goals
If it’s only on the radar when there’s heat, you’re not prioritizing inclusion—you’re managing risk.
Here’s the Thing
Accessibility doesn’t require perfection.
It requires effort. Honesty. Accountability.
People aren’t asking you to have it all figured out. They’re asking you to show that you’re trying.
And if you’re not even doing that?
Well… we notice. And we act accordingly.
Leave a Reply