Not every bug gets fixed right away.
There's always a list. There are always competing priorities. And you'll never have enough time to get to everything. So you need to make choices about what matters most right now and what can wait.
Accessibility issues are the easiest to push down that list. They don't show up in analytics. They don't always trigger support tickets. That silence can look a lot like there's no problem.
Your job is to ask better questions when deciding what to fix and when.
Here are a few that have always guided my work.
- Does it affect someone's ability to use the product altogether?
- How many people does it affect?
- Has someone complained?
- If someone complained, how long has it been sitting there?
- Is there a workaround, and if so, how bad is it?
- Does this block a core flow? For how many users?
None of these questions are complicated. But they're easy to skip when you're moving fast and your backlog is already long.
Asking them won't fix everything. But it's a start.