Hacker News new | past | comments | ask | show | jobs | submit login

Thank you for caring about accessibility. However, I don't think the pros and cons between Qt and Electron are as straightforward as you may think.

First, Qt accessibility on Windows is improving:

https://blind.guru/qtwin.html

This blogger specifically mentions the JAWS screen reader, but this should also help users of the Narrator screen reader built into Windows.

Speaking of which, Electron is not very accessible with Narrator. The reason is that Chromium implements IAccessible2, a non-Microsoft extension of the old Microsoft Accessibility API. Since IA2 is not a Microsoft API, Narrator doesn't support it.

Also, one of my blind friends told me a few months ago that Electron apps are inaccessible on Linux. I haven't yet verified this myself. Qt is accessible on Linux, though I don't know how it compares with GTK.

I don't know what the situation is on Mac.




I've seen folks with readers on Chrome on Linux. I don't mean to imply that Electron magically providers full accessibility; just that the underlying engine has much more robust support not only for readers and navigators (to which there is a ceiling folks aspire to), but also for auditing.

It's not really possible for developers to understand the full extend of accessibility needs unless they experience it themselves. As such, Electron and Chrome's accessibility auditing tools that capture these needs are an incredible step forwards.

As for Narrator, I think historically folks have been somewhat inclined to use third party or direct integration tools because it was widely considered to be inferior to the capabilities provided by direct integrations like ChromeVox or Apple's (superior) Voice Over (which from all reports I get and can find casually searching, works as well as Safari if not better).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: