What would be cool is if there would be a way to write another interface for the existing client that uses for instance, .net or something so that it is harder to run into accessibility issues since a programmer really has to work hard to not label buttons and fields. At least in that environment anyway, though I'll check it out, for I forgot to reinstall that in Window-eyes 8. I know that there was a nondefault app I was missing, and it turns out that it's QT. And I do have NVDA on here, though I seemed to believe that QT doesn't work with any screen readers at all since it is built to be an inaccessible framework by default.
-----Original Message----- From: Chip Orange [mailto:[email protected]] Sent: Saturday, May 11, 2013 8:08 PM To: [email protected] Subject: RE: WE 8 and TeamSpeak: what's everyone's experience? 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. 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.
