My mom has been legally blind for almost two decades now, IIRC. It's only within the past year or two that her computer and phone usage has begun to switch to primarily screen reader-based rather than primarily magnification-based. From then and continuing on to this day, she chooses between the terms 'low vision' and 'blind' (and various others) mainly according to what she thinks the person she's talking to will most easily understand. (Although over the course of time she has gradually shifted toward favoring the word 'blind', both as she becomes more connected to the local blind community and as her vision continues to degrade).
One thing to keep in mind is that going from normal/visual phone usage to a screen reader is like learning to walk all over again (and discovering that some paths are not for you anymore). It's starting over from zero, and it sucks. Going from typical visual usage to jacking up your font sizes is basically free, and using some kind of magnification a fairly natural next step. For people with progressive vision loss, there may be decades where one is 'blind', but it's still not efficient or opportune to drop everything and switch to relying exclusively on a screen reader.
Screen readers are convenient if you want to do anything while reading (I listen to at least view articles per week that way. I'll even admit to reading HN comments with screen reader. Surprisingly accessible).
It's almost always a mixed usage: one minute users use a feature, and the next minute they are fine without it. But those features are very nice to have
Definitely. I think one good way to think about it is as a matter of engineering excellence. Yes, there are moral and legal cases for accessibility features, but it's also a dimension of making software that is great to use and demonstrates attention to important details. It's part of the fit and finish and general UX.
Accessibility features are absolutely vital for some users, but for other users they are still nice to have. And to everyone, they are signals of quality, care, and maturity.
I find your comment interesting because it speaks to users who can see, just not well. When I think of web accessibility, I (mostly) think of users who are entirely blind. While it turns out:
~80% of screen reader users are blind. The other ~20% may be partially vision impaired, or sometimes not visually impaired at all (but use it due to things like dyslexia). [1]
~2.4% of Americans are visually impaired and use (or could benefit from) a screen reader. [2]
A "low vision" / "low touch accuracy" version of an app would likely be serving less than 0.5% (20% of 2.4%, see above) of your userbase. (As opposed to simply supporting screen readers in the "regular" version of the app.) Doesn't seem like a priority to optimize for 0.5% of your userbase when you're just trying to vet an unproven idea.
[1] https://www.tempertemper.net/blog/not-all-screen-reader-user...
[2] https://nfb.org/resources/blindness-statistics