Earlier quoted context omitted.
1. Accommodating disabled people is in no way an insult. 2. Being disabled is a normal fact of life, also not an insult. 3. Accessibility affordances are not only for disabled people. Lots of people who wouldn’t identify as disabled routinely and gladly use a wide variety of accessibility features. 4. Having difficulty identifying actionable elements like buttons isn’t about reading anyone’s mind, and it isn’t a univ…
1. Accommodating disabled people is in no way an insult. No, but treating non-disabled people as disabled could be. Just like offering help to some disabled people triggers them. I was going to respond to these numbered points in turn, but that'd be silly. My point is that having basic (previously standard) UI cues like buttons is important and stuffing that option anywhere is a poor choice. To put it under the acces…
Putting this option in accessibility settings does no such thing. That assumption is what I take issue with, and what prompted all of my points above.
> My point is that having basic (previously standard) UI cues like buttons is important and stuffing that option anywhere is a poor choice.
I disagree. I often find designs with fewer borders and shapes easier to use—that is, more accessible to me—_because_ there’s less information for me to visually process to find what I’m looking for.
That said, I’d be perfectly fine if they inverted the default… or even just asked on first install/startup, with a note on where you can change it later if you change your mind.