The bugs nobody files

1 minute read

Here's the thing nobody talks about.

When accessibility "causes bugs," everyone notices immediately. Even when it's nonsense anyway. You just suddenly find yourself in three Slack channels explaining yourself.

But when you skip accessibility? Silence.

Nobody screams "keyboard users can't complete checkout." Nobody panics when screen reader users can't navigate the new dashboard. Nobody schedules an emergency standup because your colour contrast fails WCAG.

Those aren't bugs. Those are just... the way things are.

Funny how that works, right?

Fixing something that was broken for some people lands you in hot water. But shipping something that will never work for 15% of users in the first place? That's just Tuesday.

So yeah, you'll get blamed when accessibility seemingly breaks things.

But you'll never get any credit for all the breaking you prevent.

Sent on

Did you enjoy this bite-sized message?

I send out short emails like this every day to help you gain a fresh perspective on accessibility and understand it without the jargon, so you can build more robust products that everyone can use, including people with disabilities.

You can unsubscribe in one click and I will never share your email address.