Live data from Hacker News

For software that is cross platform and accessible, forget about Qt

blind.guru

81–86 of 86 posts

Re: For software that is cross platform and accessible, forget about Qt

#81
post #73
post #63

Earlier quoted context omitted.

> He shouldn't blame a community of volunteers for not fixing his personal problems for free. Please allow me to highlight this statement. I encountered it so frequently when I created and maintained several popular open source projects. I honestly think a lot of people assume that if you're working on a project, you must be getting paid for it. Then again, many of them were totally unfazed when I pointed out that I…

I do get paid for the project I maintain, but ONLY when I am doing something that benefits my employer. I became maintainer because my employer needed a feature that wasn't there so they paid me to write it. That makes me someone who cares enough to be maintainer (the previous maintainer didn't want to be maintainer anymore). If you submit a good patch I will accept it. Submit several good patches and I'll make you c…

> I believe the majority of people working on open source projects are like me: they work on things someone pays them for but do not have the time to do anything for someone else.

To be fair, I've also occasionally had people pay me to add features to my project. However, most of the work I've done has been volunteer, at no charge.

Also, I'm not sure I agree that the majority of people working on open source projects are like you. Perhaps the more popular projects have one or two individuals working like you, but even then, there are a lot of commits coming in from volunteers. At least, that's my impression from the frontend community (JavaScript) and functional programming communities (Scala, Haskell, etc.).

Re: For software that is cross platform and accessible, forget about Qt

#82
post #73
post #63

Earlier quoted context omitted.

> He shouldn't blame a community of volunteers for not fixing his personal problems for free. Please allow me to highlight this statement. I encountered it so frequently when I created and maintained several popular open source projects. I honestly think a lot of people assume that if you're working on a project, you must be getting paid for it. Then again, many of them were totally unfazed when I pointed out that I…

I do get paid for the project I maintain, but ONLY when I am doing something that benefits my employer. I became maintainer because my employer needed a feature that wasn't there so they paid me to write it. That makes me someone who cares enough to be maintainer (the previous maintainer didn't want to be maintainer anymore). If you submit a good patch I will accept it. Submit several good patches and I'll make you c…

[deleted]

Re: For software that is cross platform and accessible, forget about Qt

#83

Earlier quoted context omitted.

If the linked bug[0] is to be believed it sounds like JAWS are ignoring QT, rather than the other way around. [0]: https://bugreports.qt.io/browse/QTBUG-53024

I'm not sure about that - it also mentions that Qt is incompatible with Microsoft Narrator. If it doesn't work with the screen reader that comes bundled with the operating system, it suggests Qt is doing something wrong.

[deleted]

Re: For software that is cross platform and accessible, forget about Qt

#84
> While other screen readers seemed to work (NVDA) it is simply not feasable to ask my future users to switch to a different screen reader just for a single program

If there's a screen reader that works then the problem isn't with QT. This complaint should be aimed at the software that doesn't work or does only selectively; not at the people working for free who ultimately did provide accessibility.

Re: For software that is cross platform and accessible, forget about Qt

#85
Well, not supporting JAWS is like claiming you are big in the transportation bussiness, and when someone comes up to you with a car, you end up explaining "Oh, but we only do horse carriages." Not supporting JAWS is just not an option. The fact that JAWS is proprietary is irrelevant here. It is simply the most wide-spread screen reader, period.

IOW, not supporting JAWS is just not an option. Besides, Qt doesn't work with Narrator either. It is telling if your accessibility support doesn't work together with the screen reader provided natively on a specific platform. So it is really not about JAWS. Qt's Accessibility support on Windows is just not up-to-date and bitrotten to a point where it is no longer useful to endusers.

Re: For software that is cross platform and accessible, forget about Qt

#86

This article isn't anything more than a rant. The author filed a bug in the QT issue tracker [1] that some proprietary screen reader (JAWS, that his customers use) does not work well with QT on Windows. No (technical) details provided whatsoever. I don't believe anyone in the QT team is /against/ stronger support for accessibility. IMO it is understandable that fixing some piece of proprietary software is not a top p…

The bug report is just prosa. No simple test case is attached to reproduce his problem. I think he did not even start a debugger. So what does the guy expect. Maybe it is just some broken string conversion. But without a bit investigation on his side he will never find out. Only well paid support will waste time with that kind of horrible report.
Post reply on HN