If you want it to be easily accessible I would say yes. ken -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James Sent: Monday, January 31, 2011 7:12 AM To: programmingblind@xxxxxxxxxxxxx Subject: Cross Platform Accessible GUI's Was RE: Making TK accessible? Hi, Since I'm at the beginning of my Java learning, I'm asking this. My book teaches Java Swing. Should I substitute SWT? Thanks. Jim Jim Homme, Usability Services, Phone: 412-544-1810. Skype: jim.homme Internal recipients, Read my accessibility blog. Discuss accessibility here. Accessibility Wiki: Breaking news and accessibility advice -----Original Message----- From: programmingblind-bounce@xxxxxxxxxxxxx [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Alex Midence Sent: Saturday, January 29, 2011 11:57 AM To: programmingblind@xxxxxxxxxxxxx Subject: Re: Making TK accessible? Hello, Jamal Wx-Widgets is not very accessible in Linux. It actually uses gtk not gtk+ in Linux. Gtk+2.0 is what works best with at-spi. As a result, accessibility in wx-widget applications is sometimes a bit sketchy depending on which widget is used. Pannel, for instance, can be a bit problematic. Dialogs and menus are sometimes a problem. I recently became painfully aware of this when I tried using Code::blocks 10.05 and Amaya 11.3 in Linux. Code::blocks is a c+ Ide which is quite accessible in windows and has a ton of nice features. In Linux, however, things are ... messy. Amaya 11.3 is a wysiwyg html editor created by none other than the w3c whhich is not accessible in neither platform. The closest I have found to comparable accessibility across both windows and Linux is java swt. Eclipse, as it happens, is about as accessible with Orca as it is with Jaws. Gecko is also quite nice although there's a lot of work being done in Orca right now to speed it up since it's not as responsive with Gecko as Jaws or NVDA is. Having said that, my research appears to indicate that the way to make an app accessible across all platforms with wx-widgets would be to port the linux side from gtk to gtk+ and then to gtk+ 2. I don't know how much work that would involve. I'm just now getting into this stuff and learning more and more every day. There are a lot of very exciting things coming in Gnome 3 and they have some very lofty and commendable goals. I wish I knew enough C and Python to truly be of use in helping with it all. What is coming is accessibility for QT in Gnome using Orca. They're trying to bridge it's built-in accessibility api to At-spi so Orca can get at the controls. It wouldn't surprise me if, one day, wx-widgets moved form gtk to gtk+ 2 for the native widgets it uses in Linux. My two cents, Alex M On 1/29/11, Lex <lex@xxxxxxxxxx> wrote: > 28.01.2011 20:49, Littlefield, Tyler пишет: >> 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. > > You will need to learn some accessibility interface (they are > platform-specific) like MSAA, IAccessible2 to do that. > > > Lex > __________ > View the list's information and change your settings at > //www.freelists.org/list/programmingblind > > __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind This e-mail and any attachments to it are confidential and are intended solely for use of the individual or entity to whom they are addressed. If you have received this e-mail in error, please notify the sender immediately and then delete it. If you are not the intended recipient, you must not keep, use, disclose, copy or distribute this e-mail without the author's prior permission. The views expressed in this e-mail message do not necessarily represent the views of Highmark Inc., its subsidiaries, or affiliates. V������jʱ�j�í������n __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind