Basic accessibility tool support is not a feature, it just becomes a part of the frontend workflow when you get into it.
My flow is basically:
- Develop some frontend stuff
- Check that I can use it with only keyboard
- Check that it looks OK at 200% zoom
- Run Devtools + axe audit
- Fix any issues found
Of course there are odd cases such as complex custom components that are really hard to get right, but mostly it's quite easy and goes fast.
Just an interesting Side-note: features customers REQUEST and features customers CARE ABOUT are not the same.
People are great at telling what they like or don't like when you show it to them, but they're not always great at telling you how to improve it.
I can't find the source now, but I've come across a story of a game in which players were complaining that the shotgun was too weak. The game devs solved this problem by... increasing the reload time on the sniper rifle, and the complaints went away. The players could correctly tell that there was a problem, but incorrectly diagnosed the best solution (assuming the devs were right in their decision).
Here are some random articles going over this argument in more detail:
https://www.appcues.com/blog/dont-give-users-what-they-want
https://www.nngroup.com/articles/first-rule-of-usability-don...
https://uxplanet.org/stop-asking-users-what-they-want-21e9ba...