Android is every bit as bad as iOS. Windows is as bad as MacOS, and Linux is as bad as either of them.
And it’s not just older folks. I routinely run into problems explaining technology to relatively younger folks; even highly educated ones.
I’ll bet that the author would have been just as frustrated, teaching Android to a room full of doctors and lawyers.
My doctor just sold his practice to NYU Langone, a very good organization (and he got lots of money, I’m sure). They installed a really intense (and expensive) IT setup in his office. I’ve been watching him and his staff, struggling with it. It’s actually an excellent system, and I’m sure that many folks here, would be proud of it, but they still struggle. He has a full-time staff member, supplied by Langone, whose only job, is to come in and help staff use the IT services. She’s very busy (and patient).
I feel like Accessibility needs to include discoverability, affordance, and usability, as principal axes.
The terminology we use, the words we pick, in user interface and feedback are vital. The design of affordances, the placement of UI elements, etc.
Glossaries are really important, and I watch people’s eyes glaze over, when I start talking about them. You can have Design Language glossaries; not just text ones.
It’s a huge topic, and not a particularly popular one.
I feel that a good start, is highlighting examples of products that get it right, with discussion on how they do it. I get pretty tired of everyone complaining about the failures. That’s just discouraging, and tends to get people circling their wagons. I think good examples would be very helpful.
I’ll start. My wife likes OXO kitchen gadgets a lot. So do I. She tends to buy stuff that I’d never get, if I were making the decision, but I find really good, once I start using it.