4 ms·
Not to mention that Chromium takes a performance hit when accessibility is on – that's why it's off by default. But both Safari and native Mac apps are always a
by ivm 9y ago
Not to mention that Chromium takes a performance hit when accessibility is on – that's why it's off by default. But both Safari and native Mac apps are always accessible.
- bramd 9y agoWell, in this case I was quite glad that they have targeted the web platform. At least that allows me to code my own stopgap solution using userscripts and stuff. That's harder for native.
- saagarjha 9y agoWith native apps, you don't need to. Good accessibility solutions are the default.
- deleted 9y ago[deleted]