These days most operating systems already come with a voice control feature, designed for people with a motor impairment to use their device entirely by voice.
When you add alt text to an image button, you're not just enabling a blind user to hear a description, you're also enabling someone with carpal tunnel to speak the name of that button to activate it.
Most other accessibility APIs and preferences have multiple use cases like that, too.
That's why accessibility is designed the way it is: you're not modifying your app to work with specific disabilities, you're adding missing semantics and respecting user accessibility preferences, and assistive technology adapts things to work with different users.
The ADA has a private right of action which means that there's distributed effort to find out what's a reasonable accommodation and also to drag businesses into compliance. There's plusses and minuses with this approach, of course.
Your first half of that sentence is debatable in absolute terms but in practice almost always right due to the second half. It can be reasonable to have an alternative version of something — for example, an audio or braille version of a printed document, or a ramp alternative to stairs – but the really hard part is actually keeping them in parity. If something is seen as a compliance obligation, I’d be shocked if that actually happened versus resources being allocated mostly to the extent that they’re cheaper than legal fees.
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...
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 wouldn't advise it, though.
What will end up happening is you have your normal app which isn't accessible, and a second app with a fraction of your features that is likely often broken because it's hard to prioritize.
So just like we have desktop and mobile views, I'm just proposing one more view where you also get to reuse some of your components, and where you get to pushback on stuff like animations, rich interactions, or novelties.
Only occasionally does the "accessible way" need to be in addition to what was planned all along, such as up, down, left, right arrow buttons beside a draggable map, you don't need a whole separate map for that.
You could be right though, especially with more and more sites blocking robots. Legitimate companies might just have to shrug and say, "this site prohibits me from reading it. You'll have to go there instead) though that seems like a legal problem to me rather than a technical one.
https://news.ycombinator.com/item?id=39227843
Fitts' Law intuitively and mathematically explains why pie menus are faster and have lower error rates than linear menus. Fitts's Law says in effect: the bigger and closer a target is, the faster and more reliably you can hit it.
https://en.wikipedia.org/wiki/Fitts%27s_law
>Fitts's law (often cited as Fitts' law) is a predictive model of human movement primarily used in human–computer interaction and ergonomics. The law predicts that the time required to rapidly move to a target area is a function of the ratio between the distance to the target and the width of the target. Fitts's law is used to model the act of pointing, either by physically touching an object with a hand or finger, or virtually, by pointing to an object on a computer monitor using a pointing device. It was initially developed by Paul Fitts.
Pie menus both minimize the target distance, while also maximizing the target size. And the physical directional gesture required to select an item does not demand your continuous visual attention and cognitively taxing hand-eye feedback loop. You don't need to look at the screen to select items from a pie menu, so you can reliably "mouse ahead" or gesture, which is impossible with linear menus.
Another advantage is that they support "rehearsal", by seamlessly training novice users to become experts.
Unlike keyboard shortcuts, the physical action of the novice and expert is the same, only experts can do it faster without looking at the screen.
Unlike traditional "invisible" gesture recognition systems like Palm Graffiti or StrokePlus.net, pie menus are "self revealing" in that the can pop up a menu that shows all the available options and their direction. It's quite difficult to learn which invisible gestures are available and what they all mean, but easy to discover them with pie menus.
Pie menus also support "browsing" and "reselection", which gesture recognition doesn't, allowing users to correct errors or even browse around highlighting every item to preview its effects.
Since pie menus can provide live continuous preview of the effects of the selected item in the application itself (which is especially nice when you use the distance as a parameter, for example a pie menu that lets you create eight objects, with a pull-out size parameter: the more you pull out, the bigger the object previewed at your cursor, which switches to different objects as you browse around the menu, then turns into a real object when you release the button), so you can see the effect and release the button when it's perfect, or go back to the center to cancel. Often the only feedback you need is the live preview of the pie menu selection, and popping up a menu would be a distraction.
Once you learn the directions, you can quickly select items by stroking in the desired direction without even looking at the menu, so pie menus can perform the selection without popping up the menu. There's no need to pop up the "self revealing" menu until you stop dragging the mouse, or you can pop it up instantly by "clicking up" the menu. So a novice can get directions instantly, while an expert can fly ahead without waiting for directions, then pause for directions or confirmation that you have the right selection at any time.
There's a smooth escalator moving you up the learning curve every time you use a pie menu, training your muscle memory through rehearsal.
That is how pie menus "Lead, follow, or get out of the way".
We performed an empirical study in 1988 that measured eight-item pie menus to be 15% faster than linear menus, with less frequent errors.
An Empirical Comparison of Pie vs. Linear Menus (Jack Callahan, Don Hopkins, Mark Weiser, and Ben Shneiderman, Proc. ACM CHI’88):
https://donhopkins.medium.com/an-empirical-comparison-of-pie...
>Pie menus gain over traditional linear menus by reducing target seek time, lowering error rates by fixing the distance factor and increasing the target size in Fitts’s Law, minimizing the drift distance after target selection, and are, in general, subjectively equivalent to the linear style.
[...]
>Pilot study results: A pilot study of 16 subjects showed that users were approximately 15% faster with the pie menus and that errors were less frequent with pie menus. Statistically significant differences were found for item seek time but not task type. Subjects were split on their subjective preference of pie and linear menus. Some commented that they were able to visually isolate an item easier with linear menus and that it was hard to control the selection in pie menus because of the sensitivity of the pie menu selection mechanism. These subjects tended to be the most mouse naive of all whereas those who had heard of or seen a mouse/cursor controlled system but had not used one extensively tended to prefer pie menus. The most mouse naive users, while finding linear menus easier, tended to be better at pie menus and commented that with practice, they would probably be superior and in fact prefer the pie menus because of their speed and minimization of hand movement with the mouse. Not surprisingly, therefore, most of those preferring linear menus did not have a strong preference on the scaled subjective questionnaire.
More about Fitts's Law and pie menu in this thread from Sept 27, 2022 on: Cairo: Alternative Windows Desktop:
https://news.ycombinator.com/item?id=32992673
More info:
Then you could provide the accessibility-minded users with something customized to their needs, instead of trying to shoehorn accessibility onto a layout that might have no commonality between what "normal" users want and what accessibility-required users want.