> Since native UI toolkits are not used, knowledge that the user already has about using their computer and how user interface elements should behave becomes us

> Since native UI toolkits are not used, knowledge that the user already has about using their computer and how user interface elements should behave becomes useless every time they download a new Electron app with a different "design" This is definitely not just a problem with Electron apps. I've seen a lot of OS X apps written using cross-platform toolkits rather than Cocoa, and every time it throws me for a bit of a loop. > Electron app developers are rarely qualified to design good usable UI elements from scratch and are often really bad at it See above. This isn't solely a problem with "Electron app developers"- more often it seems to be any developer trying to use a cross-platform toolkit. > Complete lack of accessibility integration - don't even bother trying to use an Electron app with a screen reader or other assistive tech Do you have any more details about this? I haven't looked much into a11y under Electron- does it prevent screen readers from detecting ARIA directives?