News for hackers. Stuff that matters.
Re:For software that is cross platform and accessible, forge... by Asooka on Monday August 07, 2017 @07:43AM (#14946758)
Maybe because it's easier to solve the immediate problem by writing the UI in the target platform's native fully-accessible toolkit and dropping support for platforms that don't have one.

That said, I suspect the easiest solution nowadays would be writing your UI in electron, or the Gecko-based project that was announced a week or so ago (sorry, I can't remember the name).

Re:For software that is cross platform and accessible, forge... by slifin on Monday August 07, 2017 @07:59AM (#14946840)
I use a lot of accessibility apis indirectly for keyboard navigation, on macos Shortcat cannot find any elements to click inside Google Chrome or VSCode which makes me wonder if either Shortcat has a bug or Google Chrome is not exposing those elements through the accessibility api.

Makes me hesitate to assume Electron apps are accessible by default

Re:For software that is cross platform and accessible, forge... by dom0 on Monday August 07, 2017 @08:35AM (#14947027)
> I use a lot of accessibility apis indirectly for keyboard navigation

Many cycles ago I wrote a tool which brought Unity-like menu search to Windows, and also used the accessibility API to do this (IAccessible, I think). Even back then there were many apps which didn't expose anything there, even from MSFT.

Re:For software that is cross platform and accessible, forge... by SwellJoe on Monday August 07, 2017 @07:51AM (#14946792)
Are they accessible? I know a lot of web toolkits and component libraries are not.