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
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/hn...
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.
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.
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).
Makes me hesitate to assume Electron apps are accessible by default
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.
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.