Make sure this works for everyone.
Sounds reasonable. So does everything else that boils down to accessibility matters.
These maxims don't do much good and they leave the decision of what matters up to every person. They also now have to decide when to think about it and how much time they should give it.
I've never seen any team say accessibility doesn't matter. If you asked them, they'd say they care about accessibility. But they still repeat the same mistakes. They struggle to make good decisions purely based on good intentions. That's because good intentions count for nothing when responsibility is unclear. Good intentions won't help different teams make good decisions. Even with good intentions, accessibility can still come up late, when deadlines are close and changes cost more. People want to do the right thing but aren't sure what "good" means.
Teams need better defaults.
Designers should be able to choose a component that already has accessible behaviour. Engineers should know what must work before development is complete. QA should know which interactions need checking without waiting for an expert to provide a checklist.
These better defaults should reduce the number of decisions people have to make under pressure. Their goal should be to make quality more consistent across teams, even when experience varies.
But defaults can fail too.
A large set of guidelines nobody can find or won't understand don't improve the work in any meaningful way. A checklist added to the end of delivery only confirms that a problem already exists. Audits are such a checklist.
The best defaults sit close to the decision. They might live in the design system, the ticket or the team's definition of done.
How do you get to these better defaults?
I have no magic formula for you. So far, I've been starting with issues the team have fixed more than once and simply asked what would be a good default that would make the accessible choice easier next time.
It's slow, but it seems to work.