Real talk: We have no bandwidth

1 minute read

Let's be honest: when you claim there's no bandwidth for accessibility, what you really mean is it's not a priority.

You'll squeeze in last-minute silly CEO requests. You have no problem chasing vanity metrics. And you always find the time to refactor code for "scalability."

But ensuring keyboard navigation works?

Nah, that can wait.

Accessibility isn't a standalone task. It's not some "extra." It's part of the work! If your team can't ship a button that's both "pretty" and usable, you're not delivering a product. You're delivering technical debt with a user interface.

Don't hide behind agile like it's some excuse for cutting corners. Scrum doesn't ask half-built features. Kanban doesn't absolve you of legal responsibility.

The budget exists. The developers exist. The designers exist. The tools exist. What doesn't exist is the spine to tell the CEO that their shiny new widget matters less than making sure everyone can actually use the damn thing.

Every inaccessible interface is a choice. Every "we'll fix it later" is a choice.

Stop making that choice.

Accessibility isn't a task on your Jira board.

Make a better choice.

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.