Arguing harder doesn't work. You have to reframe the problem. But what do you actually say to the team to bring them on board?
It sucks that there isn't an universal script for this.
But I found there are patterns. After enough meetings, I started to recognise the same objections coming from the same roles.
When the developer pushes back, it's not them being lazy or indifferent. They're just worried about their output looking worse on paper. Less features completed, less tickets closed. So I can't talk about accessibility because they perceive that as extra work. I frame it as avoiding rework.
Hey, I caught a focus issue on the buttons. If we spend a few minutes on it now, we'll probably avoid it coming back from QA. And then it'll be a whole thing, retesting, back-and-forth, lots of wasted time.
I'm helping them protect their time.
When the designer pushes back, it's because they care deeply about their work. They've put in a lot of effort into those high-fidelity mockups and accessibility feels like it'll just take away that shine.
The design here is solid. If we slightly adjust the base colour on these buttons and bump the text size up a bit, it will actually make the layout feel cleaner and modern. Want me to show you a quick comparison?
We're now working together on improving their design instead of critiquing it.
When the product owner pushes back, it's usually about timeline anxiety. They're not trying to bypass accessibility and ship broken stuff. They genuinely believe they can do it later.
Totally get it. I just wonder what happens when this comes back as a bug after we ship. Where does it land in the roadmap? Because in my experience it bumps something else and that something else is usually a feature we planned for already.
Now I'm just helping them see what will become a blocker later.
A lot of the times, we wait for sprint planning to make these arguments. But by then everyone's already protecting their estimates. A better approach is to catch the developer during a PR review or to drop a note in the designer's Figma file before the design review.
It's my job to make the right choice feel like the easy choice for them before they get to make it.