2 ms·
I'd also like to add that accessibility is not a binary that's either on or off. Parent comment might be thinking of features for people with high disability ra
by cratermoon 4y ago
I'd also like to add that accessibility is not a binary that's either on or off. Parent comment might be thinking of features for people with high disability ratings, but eventually everyone has some level of disability. Some even start of life with one: color blindness, vision impairment. Most people have progressive near vision loss (presbyopia) as they age.
Also, disability may not be permanent. I recently underwent major surgery and for at least a few days afterwards using my cell phone was nearly impossible. I resorted voice control a few times because I did not have the coordination or cognitive function to type. (Aside: cell phones in general are accessibility dumpster fires, but it took a major life event to demonstrate to me how bad it really is.)
So no, accessibility is not just a toggle switch or installable library. In fact, I hope future UI design incorporates some kind of non-intrusive learning and adaptability, such that when the system detects the user continually making certain kinds of errors, the UI will adapt to help.
- prmoustache 4y agoAnd I'll had you want it available on the installer already. Having said that you canct explain all that bloat with accessibility.
- cratermoon 4y ago> you want it available on the installer already Of course. Navigating around the install process without accessibility already enabled is going to be a non-starter for many. As for why all the bloat? I speculate it's because accessibility features are a second-class citizen at best, and when it comes to optimizing and streamlining, all the effort in development goes into the most-used features, whether or not they are the most essential.