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).
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).