Stopping isn't on the roadmap.
Slowing down isn't on the roadmap.
Neither is asking if you really need this feature and much less talking to some of your customers to see who'll use it.
Are they in the backlog then?
Hardly. These things are nowhere to be seen.
And neither is the accessibility debt you've accumulated over time.
Because shipping the new thing always won the fight for attention. Every sprint, planning meeting, the new thing got a shiny ticket and a deadline. It got a budget and a person responsible for delivering it.
Accessibility always got a shrug and a "we'll fix these later."
It may not be a cool new feature, but it's not an optional polish you can add once the real work got done. Accessibility is whether real people can use what you built.
So maybe the ask isn't to add accessibility on the roadmap or in the backlog. Maybe it's simpler than that.
Stop treating it like a nice-to-have!
What's the first step?
Put one accessibility fix in your very next sprint and do it.