Priority is always about right now.
That's cool, but I know you already have a backlog full of accessibility issues. How do you figure out what "right now" means?
If you're like most teams, you're likely doing something like this. You look at an issue and you rate it a 4 out of 5. Then you move to the next one and rate that a 3. Rinse and repeat.
Before you know it, you've got a prioritised list. Amazing! That felt productive, right?
The problem is you made those numbers up. They have no basis in reality. You didn't prioritise anything. You just assigned some numbers to things so that you can order them in your backlog. You might as well just ordered them alphabetically.
This doesn't work for obvious reasons. Your brain isn't built to judge issues in a vacuum. When you rate an issue a 4 out of 5, you're not measuring anything. You might be merely reacting to how the ticket was written. Or how loud someone was in the meeting when the issue came up. Or, most probably, how recently it came up.
We suck at looking at issues in isolation. But we're surprisingly good at looking at two issues side by side and saying which one feels worse.
So a better process is to look at two accessibility issues and decide which one is causing more harm right now.
Put that one on top and grab the next issue. Walk through the list and figure out which issue already on your priority list feels less worse than that. That's where it goes.
Work through your backlog this way and you'll end up with a list that pretty much reflects reality. Compare that to the previous list that reflected only how you felt when you wrote the ticket.
What you do next matters the most.
Look at the top issue and fix it.
Just that one issue. Don't worry about the next three issues because they all feel "high priority." Work on the worst problem until it's done, then move to the next.
That's it.
Compare, order, fix one thing at a time, move down the list.