We just don't have the time right now.
Just one more bug fix.
Just one more feature.
Just one more sprint.
Just one more release.
Then we'll get to accessibility.
Yup, it's another common objection. People like to wait for another day, another sprint, another release. That's when they'll kick their accessibility efforts into high gear.
The thing is, it'll never happen. You'll likely not have more time tomorrow than you do today. And work won't get any easier than it is now.
This is the opposite of what actually happens.
And it makes sense.
Think about it. If you were trying to clean up your fridge, when would the best time to do it be? Before or after you do your weekend shopping and need to stuff the fridge with fresh groceries?
It's out with the old, in with the new. Not in with the new, out with the old.
First throw out the old stuff, then put in the new things.
First improve what you have, then build what you want.
Just one more feature won't be what's going to help your users with disabilities who cannot use what you already have.
Again, not everyone will get it. And I understand that. It's in our nature to focus on the new and shiny things and it's easier to attribute our lack of whatever (market share, customers, revenue, positive word of mouth) to a missing product feature.
Much easier to say "we need this" than "we need to fix this."
It's also much harder to admit we messed up and not everyone can use what we built.