Because it's stupid. Why would accessibility features enabled by default on Windows and Linux be disabled by default in MacOS? There is literally zero advantage to disabling it, and it makes life harder on users.

Same thing with tap to click. Once everyone else enabled tap to click Apple disabled it. They just HAVE to be different, even if it's bad for users, and that stubbornness is frustrating.

▲

dpark a day ago | parent | next [-]

If you expect your users to mostly work with both mouse and keyboard, it can make sense. Dropping stuff from the tabbing order means that the stuff left is is quicker to tab through. I find it mostly annoying.

Tap to click, though, that’s infuriating. I don’t know how people can stand it. I know people who insist they like it and then I see them accidentally “click” regularly and get annoyed by it.

	▲	burnte 10 hours ago \| parent [-]
		No, keeping it disabled makes zero sense. There's no reason now to force people to enable it. Most people don't even know you can do it in windows so it's not like there's a huge problem for them. No reason not to leave it on here.

▲

danaris 20 hours ago | parent | prev [-]

To a large extent, I believe it's a holdover from the earliest days of the Mac, when the mouse was brand-new, and many developers had to essentially be forced to even support it, let alone treat it as a first-class interface device.

I agree that it would be nice if Apple would have more keyboard navigation available by default now than they did then, but given that it is readily available for those who want it, I don't really see it as a huge issue.