Time. We never have enough of it and we always squander it.
Time is the thing nobody budgets for accessibility. Not really, if we're honest.
I've always had to battle for it because there was always another feature that was committed work with a set deadline. They thought accessibility should be a different feature. And at most it got the leftover hours. If there were any. Which there usually weren't.
I've said it before. What if you treated accessibility the same way you treat security? Nobody ships and then adds user accounts with passwords. Why then build a feature and then go back to the drawing board and add screen reader support?
Your primary job is time allocation.
And time allocation is a values problem. But it's thought of as a scheduling problem.
Here's a concrete example.
When a user can't reset their password, they can't log in. That's a critical bug and deserves a hot fix. When someone using a keyboard instead of a mouse can't log in, it's a backlog item. Same broken experience, but wildly different urgency.
That's not a calendar issue. That's what your team values and believes about whose experience matters.
Accessibility doesn't need its own column on your kanban board.
Budget the time before the work exists.
Radical, I know.