Python still ships with TKInter. I don't want to add speech to it, because that kind of kills the point of using it with a reader, but I would like to use something to allow Jaws, Wineyes and NVDA to access it with no problems.
On 1/28/2011 11:23 AM, Ken Perry wrote:
Um are there still people using TK? I would go with gtk on any project over tk. If you have to make it accessible though you will need to make the gui accessible and that means replacing anything that has a UI component with something that has either hooks or talks on its own. You might want to look at the gtk++ accessibility frame work for examples of what they had to do to get gtk to work. ken -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Littlefield, Tyler Sent: Friday, January 28, 2011 1:11 PM To: programmingblind@xxxxxxxxxxxxx Subject: Making TK accessible? I don't know if some of you remember Octavian, or if he's still on this list. To make a very very very long flame-filled thread shorter, he's basically screaming and yelling on the python list about discrimenation and TKInter not being accessible. Having not ran anything TK-like in Windows, I'm curious what the deal with this is. How could TK be mmade more accessible? His solution was to rip it out of the STDLib and replace it with WX, which won't end up happening for a few reasons, at least not any time soon. So, I want to try to talk to the TK folks, maybe jump in the trenches if I can and help code/make things more accessible. Can someone knowledgable about this give me some input on what needs to be done?
-- Thanks, Ty __________View the list's information and change your settings at //www.freelists.org/list/programmingblind
