Accessibility rework rarely starts when QA finds a bug. It starts earlier, when you skip a decision or leave it hanging.
But when? And how do you figure that out?
Here are three questions you can ask your team to find out.
- When do we first discuss how a feature works with a keyboard, screen reader or zoom?
If the answer is "during QA" or "after release," the team is learning too late. By then, design and code may both need changing.
- What accessibility details must be clear before the design is ready to be built?
A vague answer exposes a handoff gap. Missing focus order, labels, error behaviour and acceptance criteria force engineers to guess.
- Who checks the implementation against those decisions and when?
If nobody can name a person and a moment, QA will end up finding decisions the team should have made earlier.
Ask these about your next feature. The first fuzzy answer points to where rework begins.