5 ms·
So, to recap, GTK doesn't work at all for accessibility, wxWidgets has issues with text entry, and Qt works, but only with NVDA, and not with text entry fields
by kuschku 9y ago
So, to recap, GTK doesn't work at all for accessibility, wxWidgets has issues with text entry, and Qt works, but only with NVDA, and not with text entry fields and JAWS.
Now, Qt is an open project, so the question is: are there just no users interested in this who could implement it themselves? Most other functionality in toolkits was implemented like this.
- Asooka 9y agoMaybe 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).
- SwellJoe 9y agoAre they accessible? I know a lot of web toolkits and component libraries are not.
- slifin 9y agoI 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
- dom0 9y ago> 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.
- oblio 9y agoThese are the things that are super low priority for commercial projects, and those don't usually want to leave money on the table. They're super low priority for OSS. If I recall correctly Sun paid a long time ago for usability and accessibility studies for GTK 2 and Gnome 2. And I'd guess most of their work was thrown way during the transition to GTK 3/Gnome 3 (somebody can correct me on this, I'm not really certain). Basically: https://www.jwz.org/doc/cadt.html https://www.jwz.org/doc/cadt.html
- deleted 9y ago[deleted]
- ktta 9y agoThe link is interesting. Looks like it checks for the HN's user logged in cookie and redirects to imgur.
- distances 9y agoNo, it's checking the referrer. Cookies can't of course be read by other sites, that would break everything.
- ktta 9y agoI wasn't thinking about the cookies part. I just learnt about Referer. How doesn't this compromise privacy? Looks like I'm woefully uninformed about web security/privacy. Also, found this[1] for anyone who just learnt about this like me. For firefox, go to about:config and set Network.http.sendRefererHeader to 0 [1]:https://chrome.google.com/webstore/detail/referer-control/hnkcfpcejkafcihlgbojoidoihckciin https://chrome.google.com/webstore/detail/referer-control/hn...
- yoz-y 9y agoNot sending a referer can sometimes break sites though. For example some image hosting sites will not display content if you are not coming from their domain (to avoid hotlinking) and some web-apps will kill deep linking like this. Granted it is not very secure but some people will go to great lengths to break the open web. This is also how Google Analytics knows where people come to your site from, for example.
- alexlarsson 9y agoGtk+ is accessible on Linux, just not the win32 build.
- alexlarsson 9y agoGtk+ is accessible on Linux, just not the win32 build.
- imtringued 9y agoThe only users that are interested and can implement it themselves already use linux where accessibility works better than on windows or with JAWS.
- BeetleB 9y ago>The only users that are interested and can implement it themselves already use linux where accessibility works better than on windows or with JAWS. Eh? I worked with a blind programmer. He loves Linux, but had to stick to Windows because the accessibility for blind people on Linux was horrible compared to JAWS.