3 ms·

I'm one of those people... It's simply about pointing devices hurting my hand, wrist, and arm. Keyboard use does not. Is that so hard to understand? This is

I'm one of those people... It's simply about pointing devices hurting my hand, wrist, and arm. Keyboard use does not. Is that so hard to understand? This is what makes it an accessibility issue for me, not a preference.

adambatkin 5y ago
I don't think the argumentative tone was warranted. No one is suggesting that anyone be forced to use a mouse or that accessibility solely using the keyboard be limited in any way. But there is definitely the appearance of an aversion to the mouse in some a older (and things that want to seem old-school) Unix/Linux tools. For _some_ people, the mouse is easier to use, so increases accessibility for _them_. I think the OP was implying that better mouse accessibility could be added on-top of the existing keyboard support.
eddieh 5y ago
Does your keyboard have a num pad? If so, then you're likely extending your arm to to far, bending your wrist at an odd angle, and relying on your shoulder to bear the weight of your arm when you use your mouse.
- forgotmypw17 5y ago
  Thank you for your suggestion. This is certainly a contributing issue when it is the case that I'm using a keyboard with a numpad and a mouse together, but not the only one. I use many different keyboards and pointing devices (not just mice) and the general trend I described holds true.
int_19h 5y ago
This is a very good argument for making keyboard one of the devices that can be used for UI interaction. And, indeed, keyboard-navigable UI is a hard accessibility requirement for products that I work on. But then there's this whole subculture in Unix that basically claims that keyboard should be the only device used for interaction. The software that they make makes it deliberately hard, or outright impossible, to use the mouse. And there's a cult following around this, based solely on the notion that it's somehow better in general. (A stark example of this approach is https://www.nongnu.org/ratpoison/ https://www.nongnu.org/ratpoison/, where it's readily obvious from the name and the logo.)

adambatkin 5y ago

I don't think the argumentative tone was warranted. No one is suggesting that anyone be forced to use a mouse or that accessibility solely using the keyboard be limited in any way. But there is definitely the appearance of an aversion to the mouse in some a older (and things that want to seem old-school) Unix/Linux tools. For _some_ people, the mouse is easier to use, so increases accessibility for _them_. I think the OP was implying that better mouse accessibility could be added on-top of the existing keyboard support.

eddieh 5y ago

Does your keyboard have a num pad? If so, then you're likely extending your arm to to far, bending your wrist at an odd angle, and relying on your shoulder to bear the weight of your arm when you use your mouse.

forgotmypw17 5y ago
Thank you for your suggestion. This is certainly a contributing issue when it is the case that I'm using a keyboard with a numpad and a mouse together, but not the only one. I use many different keyboards and pointing devices (not just mice) and the general trend I described holds true.

int_19h 5y ago

This is a very good argument for making keyboard one of the devices that can be used for UI interaction. And, indeed, keyboard-navigable UI is a hard accessibility requirement for products that I work on. But then there's this whole subculture in Unix that basically claims that keyboard should be the only device used for interaction. The software that they make makes it deliberately hard, or outright impossible, to use the mouse. And there's a cult following around this, based solely on the notion that it's somehow better in general. (A stark example of this approach is https://www.nongnu.org/ratpoison/ https://www.nongnu.org/ratpoison/, where it's readily obvious from the name and the logo.)