One accessibility issue might be a mistake. But the same issue appearing across several features tells me something more useful.
Perhaps accessibility is first mentioned during QA, when reworking everything is expensive. Or maybe people know there's a problem but don't feel able to challenge the release date because of it, so it gets pushed to later. Or the team keeps making the same default decision that leads to problems later, without even knowing it.
In any case, repeated issues show product leaders what keeps their teams making the wrong decisions easier than the right ones.
A single bug rarely tells me enough to suggest a wider change. People miss things, new issues show up and no process can catch everything. I start paying attention when the same type of rework keeps showing up.
The first step is to show the pattern clearly.
A few weeks ago, I remember fixing a keyboard issue in three different places that all used the same component. When I noticed that, it gave me something concrete to improve. We should fix the component, change the guidance and make keyboard behaviour part of the acceptance criteria.
You don't need to solve every accessibility problem yourself. You can help people notice what keeps producing those same type of problems all the time.
In time, they'll start fixing it themselves.