This is an accessibility conversation that needs to happen but I don’t know if I could articulate it w/o it coming out ableist. Like disability is not a bad word… but I don’t have the language here to describe it like I might for a user who needs a louder volume or won’t hear any sound.
I think there's something about how people who make software need to keep in mind that no one is going to care about what they build as much as they do, and that means people are going to misuse it/use it wrong/etc, so we have to design with that in mind.
Yes! Willfully abuse or need different things or don’t understand! For my work, I know that this is not going to be a top priority for my users, so how can I get them to do what we need them to while spending minimal cognitive load on the process itself? (Sometimes I do want to scream RTFM)