I'm very fanatic about quality. I think most teams I worked with shared this. They also believed, like me, that accessibility is part of quality.
But it doesn't always play out like that.
Tickets constantly reach QA where they quickly discover that not everything works with a keyboard properly and nobody has a useful answer as to why. It's not that they don't care. It usually means accessibility was treated as something the team would notice and fix later.
But later is a bad time to define what done means. Later is when design moved on and the engineers already built the thing around some assumptions they made out of thin air. There is already a set release date.
And now the form doesn't work with screen readers. The error messages aren't properly hooked up to the fields they belong to. Ooops!
Maybe the definition of done was missing something small but important.
Was there a shared expectation for the kind of work you'd shipping?
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.