4 ms·

Oddly enough your comment made me think of electron apps vs native apps, because they are usually impenetrable to accessibility APIs so they appear as completel

• Earw0rm 4y ago
  Seems like a solvable problem in the medium term - Electron apps are, in effect, a web page; build an accessible page, the Electron runtime _should_ be able to join the dots same as a full browser does.
  • giantrobot 4y ago
    It seems like a lot of frameworks used with Electron are the "reinvent every HTML tag as a component with divs" variety. So unless a developer hangs a bunch of event handlers off some widget they don't have default handlers for a lot of accessibility. If they used a real tag they'd get a bunch of free accessibility/functionality but instead they use components.
• kitsunesoba 4y ago
  To me that highlights how important it is for UI frameworks of all types to have accessibility affordances not only built in, but as one of the pillars of their designs. That makes it so even apps developed without any regard to accessibility are reasonably accessible by default. This doesn't gel well with the bring-your-own-everything nature of the web, unfortunately. Even if you look just at React there's 50 ways to build the same thing, which I'm sure makes rolling in accessibility that "just works" across all React apps without additional effort from the developer extremely difficult. It's much more practical with UI frameworks that are strongly opinionated with only a single well-supported "happy path" for most things.