You may have heard this before and there's a bit wrong with this question. It's a fairly common one in teams that care about making their products accessible, which is a good thing, but it's also exposing some deeper problems.
What are you really asking?
The task "done accessibility" can be a roundabout way of saying, WCAG criteria. So by asking have you done accessibility the question often means "Have you reviewed this against the WCAG 2.x success criteria?".
Why is this a problem?
The goal is that accessibility features for people with disabilities become a default part of designing and building products, not seen as an addition. As an example, keyboard navigation isn't an add-on to alternative ways to navigate your UI, but it is part of building all other interactions, equivalent to ensuring you can click things with a mouse.
Another issue here is that by approaching accessibility as a tick box exercise, by nature, once the box is ticked it stays ticked. Yes tick off the criteria but they need to be constantly reviewed and reevaluated. Ticking them off does not make your product accessible, the team needs to be engaging people with disability to gather further feedback and insight.
With those criteria built in, the question, "have you made this feature accessible?" is asked less and it's simply, have you completed the feature. The accessibility is built-in.
There's a lot to it and ensuring your products are accessible may seem from the outset a large set of work. And that's true, because great products require a great deal of work.
25th January 2026