So, where does that leave us?
We have the top-down crowd holding the keys and blueprint and the bottom-up crew holding the tools. And they're usually shouting at each other from different floors. Management is worried about a lawsuit, but they don't fully understand why. And the product team are exhausted from trying to explain why a "pretty" button that can't be announced by a screen reader isn't really a button.
I don't think the sweet spot is a compromise or a middle ground. It must be a head-on collision!
It's rare, but it exists! That moment where the "why" and the "how" finally stop fighting and start coming together. It happens when a CEO realises that accessibility isn't a legal shield, but a sign of a high-performing and empathetic culture. And it happens when a developer realises that those "annoying" corporate policies are actually the cover they need to finally do their best work without having to beg for permission.
Think of it like this.
Top-down gives you the permission to care and bottom-up gives you the soul to execute.