I think each case is different. However, GW seems to feel the latest QT is the best for accessibility, so why not forward their message to the developers of TeamSpeak, along with your request that if they disagree about the latest QT being the fix for the problems you are having, would they please contact the author of your screen reader, who feels the latest QT is the best solution for this issue. They may not be correct in their assessment that there is a bug in the latest QT (or it may be an excuse so that they don't have to do a little work).
-----Original Message----- From: Katherine Moss [mailto:[email protected]] Sent: Monday, May 13, 2013 1:54 PM To: Stephen Clower; Chip Orange Cc: [email protected] Subject: RE: WE 8 and TeamSpeak: what's everyone's experience? Thank you all for your support; You are helping very much in my mission to insist that developers handle accessibility in their programming process as an integral part. And you guys read my mind; I'm going to eventually send this information right on to the folks who develop TeamSpeak, but they say that they are using a lower/older version of QT due to a "bug in the latest version" that prohibits screen reader accessibility. They claim that they can't fix it till the folks who develop QT fix the problem on their end. Why does accessibility have to be so complicated? Why do so many people have to get involved in something that should be so simple? I'm sorry for the rant, but this does drive me nuts; for instance, on another application, Windows Server 2012 server manager, I tried to put the blame on Microsoft for there being less accessibility in it with Window-Eyes and the other screen readers since that's what somebody told me; whenever there is an accessibility problem, the developer and not the screen reader manufacturer is to blame, and then you guys over at GW Micro took the blame for that one saying "sometimes we could do better". So, where do I go to report accessibility problems since sometimes it is obviously the developer's fault, and sometimes it is the screen reader manufacturer's problem? It makes my head spin. -----Original Message----- From: Stephen Clower [mailto:[email protected]] Sent: Monday, May 13, 2013 1:28 PM To: Chip Orange Cc: [email protected] Subject: Re: WE 8 and TeamSpeak: what's everyone's experience? Chip, Indeed. I just wanted to make sure she's armed with the right information if she decides to contact the developers. Steve On 5/13/2013 1:24 PM, Chip Orange wrote: > Thanks Steve. I meant it only as a "last ditch" effort on her part. > If it worked, then she could contact the vendor to let them know it > appears they're using QT version 4, and they need to upgrade to > version 5 if they want to support accessibility. > > Chip > > > -----Original Message----- > From: Stephen Clower [mailto:[email protected]] > Sent: Monday, May 13, 2013 1:14 PM > To: Chip Orange > Cc: [email protected] > Subject: Re: WE 8 and TeamSpeak: what's everyone's experience? > > Chip, > > Just to clarify, you will get limited access with QT 4.6 or 4.7 with > Window-Eyes and the QT Support app, and similar access is available in > other adaptive products. The problem with 4.x access is that all > events are pushed to the screen reader; we have no way to interrogate > a QT program for contextual info, and a lot of what we get back is > incomplete data. QT 5, on the other hand, is based off of IA2 and thus > provides a much richer interface for data conveyance and program > introspection, but in the case of Window-Eyes version 8 or newer is required. > > HTH, > Steve > > > On 5/13/2013 1:00 PM, Chip Orange wrote: >> Why not forward them Steve's note and tell them that you wanted them >> to > know >> that the screen reader which works with QT (Window-Eyes) requires QT >> 5 or later? You might get some useful action or info from them if >> you provide them this information. >> >> Chip >> >> >> >> -----Original Message----- >> From: Katherine Moss [mailto:[email protected]] >> Sent: Monday, May 13, 2013 11:25 AM >> To: Stephen Clower; Chip Orange >> Cc: [email protected] >> Subject: RE: WE 8 and TeamSpeak: what's everyone's experience? >> >> They say that they have taken accessibility seriously, yet only > Window-Eyes >> works at all with any sort of QT applications, so they need to make >> that clearer on their site that an additional Window-Eyes application >> (I don't like the word App outside of a mobile context), is needed, >> don't you > think? >> Why don't people get it? And I'm pretty sure the "special" version >> of the client uses QT 4.7.2, but I can't bank on the use of standard >> widgets > since >> I'm not the developer, and any questions regarding it fall on deaf ears. >> >> -----Original Message----- >> From: Stephen Clower [mailto:[email protected]] >> Sent: Monday, May 13, 2013 8:56 AM >> To: Chip Orange >> Cc: [email protected] >> Subject: Re: WE 8 and TeamSpeak: what's everyone's experience? >> >> Note, too, that the QT Support app will assist only if the program in >> question is using the standard widget set provided in QT 4.6 or 4.7, >> and > the >> program must be built in such a way as to allow the accessible >> widgets to > be >> installed into its own directory. If your application is built >> against QT > 5, >> then you will need Window-Eyes 8.2. The QT Support app will not >> function > for >> QT 5-based programs. >> >> Regards, >> Steve >> >> >> >> On 5/11/2013 8:07 PM, Chip Orange wrote: >>> If QT is the problem, I have found that installing the original QT >>> app (written by Steve Clower) did help me in a situation with a >>> program using QT, where WE wasn't reading it's output. You could >>> try installing this app (it's still available on app central, and is >>> named something beginning with QT). If it solves the problem, I'd >>> suggest writing to GW support and telling them about it. >>> >>> Or, you could get a copy of NVDA and run it (you don't have to >>> install it, you can just run it as in its "mobile" mode where it >>> doesn't >>> install) and see how it does. If it too fails with TeamSpeak, you >>> could write to them and tell them you've tested with two screen >>> readers and it's not working; ask them to consider downloading the >>> demo version of Window-Eyes and trying it themselves. >>> >>> Chip >>> >>> >>> -----Original Message----- >>> From: Katherine Moss [mailto:[email protected]] >>> Sent: Saturday, May 11, 2013 6:38 PM >>> To: Chip Orange; [email protected] >>> Subject: RE: WE 8 and TeamSpeak: what's everyone's experience? >>> >>> This has to do with me and my desire to run my own TeamSpeak server >>> on my own hardware. I gave you the reasons why I don't like >>> TeamTalk though aside from the SDK thing. TeamSpeak allows >>> development to be open source, TeamTalk doesn't. But more >>> importantly, TeamSpeak allows the administrator to not have to keep >>> information that they shouldn't have around such as when setting up >>> a TeamTalk server, there is no option for users to register >>> themselves, and if I'm going to have a server of any kind, I don't >>> want to know the passwords and credentials of my users; that is a >>> very bad security practice, and until TeamTalk is developed in a way >>> in which users can register themselves, I will not use it. I have >>> no interest in custom development right now, but when I get there, >>> I'd like to be able to distribute add-ons and stuff freely which >>> TeamSpeak allows you to do. I just want a security-aware >>> environment for people and TeamTalk does not provide that. But what >>> I don't get is if the TeamSpeak team wrote a special client that >>> uses an older version of the QT framework and was tested to be >>> accessible, then why does it look no different than the normal >>> client? I was told that it would and that it worked with all screen >>> readers. I just want to know that I have not been outright lied to, >>> and then to help users work these things out on the development side >>> of things. I mean, Window-Eyes has QT support, yet I've not found a >>> single QT application >> that works with it. >>> -----Original Message----- >>> From: Chip Orange [mailto:[email protected]] >>> Sent: Saturday, May 11, 2013 6:22 PM >>> To: [email protected] >>> Subject: RE: WE 8 and TeamSpeak: what's everyone's experience? >>> >>> Hi Katherine, >>> >>> Do you want to develop for one of these or just use it? I want you >>> to know I've had great experience using TeamTalk; so good that I've >>> never felt the need to work on anything else, and its developer also >>> provides a special version of the client which is written for >>> accessibility. There are also public servers available so that you >>> don't >> need to run your own. >>> I conducted all of the scripting classes using TeamTalk, recording >>> the output, and it worked fine for us. >>> >>> If you have special needs for developing that relate to >>> accessibility, why don't you ask the author of TeamTalk if he'll >>> provide you with a free sdk for your development (since you seem to >>> be having difficulties with TeamSpeak)? >>> >>> Hth, >>> >>> Chip >>> >>> >>> >>> -----Original Message----- >>> From: Katherine Moss [mailto:[email protected]] >>> Sent: Saturday, May 11, 2013 12:10 AM >>> To: [email protected] >>> Subject: WE 8 and TeamSpeak: what's everyone's expereience? >>> >>> Hey all. >>> I'm wondering if there are a lot of you who use TeamSpeak? Maybe >>> somebody runs and/or connects to a server run by someone else? I'm >>> asking this question because according to the developers of >>> TeamSpeak, they take accessibility very seriously, and so have >>> provided a client written with an older version of the QT framework >>> since the newest version has a bug that prohibits screen readers >>> from working with it at all apparently. Well even with this >>> "special" client, I don't see any difference at all, and so I'm >>> wondering if this is just a lazy developer's way of covering up the fact that they actually don't care. >>> Have you guys had better results? And I could use TeamTalk for my >>> voice server, yes, but I refuse to, due to both security reasons >>> (administrators have to know the password of every user and I do not >>> like that, being a security conscious technologist), and politics; >>> the developer charges outrageous prices for his SDK to develop >>> against the TeamTalk API and TeamSpeak's SDK is free for certain >>> types of projects, so I prefer TeamSpeak over TeamTalk for those >>> reasons. Have > you >> guys gotten TeamSpeak to work with Window-Eyes 8? Thanks for any > feedback. >>> If you reply to this message it will be delivered to the original >>> sender only. If your reply would benefit others on the list and your >>> message is related to GW Micro, then please consider sending your >>> message to [email protected] so the entire list will receive it. >>> >>> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You >>> can manage your list subscription at http://www.gwmicro.com/listserv. >>> If you reply to this message it will be delivered to the original >>> sender only. If your reply would benefit others on the list and your >>> message is related to GW Micro, then please consider sending your >>> message to [email protected] so the entire list will receive it. >>> >>> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You >>> can manage your list subscription at http://www.gwmicro.com/listserv. >>> >>> >>> If you reply to this message it will be delivered to the original >>> sender >> only. If your reply would benefit others on the list and your message >> is related to GW Micro, then please consider sending your message to >> [email protected] so the entire list will receive it. >>> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You >>> can >> manage your list subscription at http://www.gwmicro.com/listserv. >> >> -- >> Stephen Clower >> Product support specialist & App Development GW Micro, Inc. * 725 >> Airport North Office Park, Fort Wayne, IN 46825 >> 260-489-3671 * gwmicro.com >> If you reply to this message it will be delivered to the original >> sender only. If your reply would benefit others on the list and your >> message is related to GW Micro, then please consider sending your >> message to [email protected] so the entire list will receive it. >> >> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You >> can manage your list subscription at http://www.gwmicro.com/listserv. >> >> >> If you reply to this message it will be delivered to the original >> sender > only. If your reply would benefit others on the list and your message > is related to GW Micro, then please consider sending your message to > [email protected] so the entire list will receive it. >> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You >> can > manage your list subscription at http://www.gwmicro.com/listserv. > -- Stephen Clower Product support specialist & App Development GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 260-489-3671 * gwmicro.com If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv. If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to [email protected] so the entire list will receive it. GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
