"Finished" is one of those words that sounds simple until people have to agree on what it means.
Let's think through it a bit. When is a ticket finished?
A ticket can be finished when the code is merged. Finished because the screen matches the design. Finished because QA passed it. Finished because the acceptance criteria were checked. Finished because nobody said otherwise yet.
All of those sound perfectly reasonable, but they are not always the same thing.
I think most people would say finished means it's either ready to release or released.
Then everyone is surprised when some issue shows up. People aren't being difficult. It's just the team used one word and meant different things by it.
This is why Definition of Done matters.
And I want to keep this very plain.
Definition of Done says what finished means.
That's it.
It gives everyone a shared meaning before release gets close and someone has to decide whether an issue is small or not.
For accessibility, this matters because many problems start with this misunderstanding. If finished doesn't include accessible, then finished might only mean work was delayed.
I think that's where rework starts.