If the same accessibility issue keeps coming back, I don't think it's the same issue anymore.
The first time, maybe it's a bug that you fix. The second time, maybe it was just bad luck. The third time, I start to suspect you're constantly fixing the symptom, not the cause.
And it's insane how easily this happens.
The ticket comes in, you fix the issue and the work moves on. Everyone feels a small amount of relief that you fixed something. The fix might even make it onto your release changelog.
Then the same issue shows up somewhere else.
So what do you do? You open another ticket, fix it there and have another little celebration.
But did the team learn anything?
Did the component change? Did the design pattern change? Did the acceptance criteria change? Did the Definition of Done change? Did anyone write down the decision somewhere the next person will actually look?
These repeated issues are feedback that didn't make it back into how your team works.
You may have solved one issue, affecting this next release. And yes, you've stopped one bug from reaching production. But no, you didn't kill rework.
Because the lesson only lives inside that one ticket you fixed, the next ticket starts from zero. That's how teams end up paying for the same accessibility issue over and over again. Rework.
Because the knowledge stays local. One ticket. One person. One review comment. One Slack thread that you'll lose forever.
I notice this pattern more and more. And when I do, I change my thinking from trying to figure out where else the same bug might be to figuring out what the lesson is and where it needs to live so that more people can learn from it.