I've heard it a million times. We'll get to accessibility after this sprint. After this sprint becomes after launch. And after launch becomes after things settle down.
But things never settle down. That's the nature of product work. You never catch a break so you never have time.
But we're not really blocked by time. We're blocked by priorities that we never really set.
If accessibility sits in your backlog, it's not because it's hard to schedule, but because no one with decision-making power has said this matters enough to prioritise.
And that means that accessibility is a leadership problem, not a capacity problem.
And that's good news! If you can call it that. Leadership problems are solvable. You don't need a bigger team or a longer runway. You need to make a decision. One that has consequences, not one you put on a slide deck.
Decide that accessibility is part of done.
Decide that it gets resourced like features do.
Decide that the people your product is leaving out are worth it.
A day always has 24 hours and there's always going to be 7 days in a week. Time has been there all along.
It was just going somewhere else.