Forms are quite the cornerstone of the web. I've yet to see a product without a form. And I've yet to see a form without problems.
I can imagine most of the forms go through some rigorous development process. Even so, issues slip through. QA finds most of them. Engineering fixes them. And the tickets are closed.
Next sprint, a different form has the same damn errors. Again.
Still, nobody calls this a recurring problem because the tickets are different. One was on the checkout screen and one was the account settings. And they're both small on their own.
But the team has now paid twice to learn the same thing.
Repeated accessibility issues are expensive in the most boring of ways. Another QA comment, another design clarification, another engineer switching back to work they thought was finished. It's nothing dramatic enough to trigger a process change, so that's why they keep coming back.
Closing a ticket means one thing that was broken is now fixed. It doesn't mean the team learned how to avoid the next version of that issue.
Sometimes the knowledge stays with whoever fixed it. Then a new person builds a similar flow and starts from scratch. And they make the same mistake as others before them.
At some point, this stops being an accessibility bug.
At some point, it became a delivery pattern.
I'm exploring this question along with four more, in a free email course that helps digital health product teams find where accessibility rework starts. Sign up for Kill Accessibility Rework in 5 Days.