Tkinter: The good, the bad, and the ugly!

Adam Skutt askutt at gmail.com
Thu Jan 20 15:49:46 EST 2011


On Jan 20, 3:02 pm, "Octavian Rasnita" <orasn... at gmail.com> wrote:
> From: "Adam Skutt" <ask... at gmail.com>> Yet, for some unfathomable reason, you keep promoting
> I would be glad if you could tell me about a portable solution which is accessible with JAWS and Window Eyes, the most used screen readers under Windows (real glad).

I did, Qt.  I'm not yournanny and I'm not going to go test it for
you.  There are bugs in the Qt database relating to JAWS
functionality, so it others have plainly gotten it working to some
degree.  But honestly, why should I waste my time replying to you when
you're too damn lazy to even use Google?  I certainly won't be doing
so in the future.  "Lead a ignorant, thirsty horse to water, watch it
die of thirst" and all that.

> Exactly. When you will read that thing on a GUI creator site it means that that GUI is not accessible because the screen readers don't support it yet.
> The GUI libs manufacturers will say that the screen readers are bad because they don't offer support for their GUI, although that GUI offers accessibility features.

No, that's not what that page says or means.  But I'm not going to be
able to explain it to you any more clearly, so if you'd prefer to keep
living in your own delusional, illydic world, that's your decision.
Qt has been pretty clear in painting the blame on who it belongs on,
which is not the screen reader vendors.

Adam



More information about the Python-list mailing list