If meaningful change is what you're after, you have to pick your battles. You need to show what are the specific changes you're after and how they'll benefit everyone involved.
Once you've shown that, something will eventually shift.
People will start to see accessibility isn't this massive, overwhelming thing that'll grind their workflow to a halt. It's just, well, it's part of the work. Just like any other consideration.
But you still can't force it down their throats! You can't impose your way to accessible products.
The job is to create the conditions for the ones we work with to make a choice that aligns with the change we want to make.
That means making the choice between accessible and not accessible easy. That means removing friction. Depending on your workflow, it might mean having a component library or the examples already there. At the very least, it means having the documentation written and easily accessible to everyone.
Slowly, you become the person who helps, not the person who blocks.
That's when it sticks. When people choose accessibility themselves because they see it as helping them do better work rather than something imposed on them.
That's the job. Create the conditions where the right choice is the easy choice.