Katherine: I’m not a dev, but. There’s documentation for RDP here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa383015(v=vs.85).a... Based on this, my guess, and its only a guess, is that all that the RDP support in JAWS or Window-Eyes does is use one of these extensible channels that the docs talk about. Text that would normally go to the synthesizer is sent through the extent channel just like it’d normally be sent to the synthesizer, the screen reader on the other end gets it and it continues on its way just as normal. I’m sure I’m really over simplifying things as again I’m not a dev, but it doesn’t look like making it work would be a really big deal, the foundations for it are already in the RDP spec. Ryan -----Original Message----- From: Blind-sysadmins on behalf of Katherine Moss Reply-To: Blind sysadmins list Date: Thursday, December 17, 2015 at 10:39 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions
Figures ... I'm not even going to go into my thoughts about that guy ... just suffice it to say, he's not my favorite developer in the world That's putting it nicely. But on the issue of RDP ... I'm just curious for the devs on this side, what API would that even use? I figured it was some proprietary thingo that AISquared and FS had with Microsoft, so that's why it doesn't work with NVDA, but maybe I'm wrong?
-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Kathryn Jedynak Sent: Thursday, December 17, 2015 9:32 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions
I aggree. The developers should have provided the relay server themselves even if it ment paying for it. I tryed contacting Christopher Toff but he never responded.
Sent from my iPhone
On Dec 17, 2015, at 3:56 AM, Andrew Hodgson <andrew@hodgsonfamily.org> wrote:
Hi,
The NVDA plugin is good, but I was very disappointed that they decided not to release the relay server themselves (in my view for reasons which didn't stack up), and since the release, they have closed the beta list and there hasn't been any further discussion on the addin. Further to this I don't believe it scales well to allow admin of several servers, and could potentially be seen as a backdoor by some IT departments. This is why I like the RDP so much: it uses existing interfaces to provide the remote desktop capabilities, which is known and loved by everyone.
Andrew. ________________________________________ From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of Kathryn Jedynak [ms98kasia@gmail.com] Sent: 17 December 2015 00:43 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] remote desktop solutions
It seems like neither nvda, or nvda remote are not very popular in the United States. not too many people know about the nvda remote plugin nor the fact you can have a relay server. I learned about the open source relay server for nvda from Michal Dziwisz Tyfol podcast which is based in Poland. Now I'm trying to convince the place where I work at to implement it. It seems that people here are stuck on Jaws. They aren't aware that there are a few other screen readers out there.For example, you can use window eyes for free as long as you have Office 2010 and up. Of course, you can download nvda for free. Sent from my iPad
On Dec 16, 2015, at 4:45 PM, Sean Murphy <mhysnm1964@gmail.com> wrote:
HI,
Have you tried Team Viewer? I am not sure if this will help. Do you require full access to the linux environment? There must be a way so the client can see what you are doing at the time of your support call if you are supporting Linux platform product.
This is why they like products like WebEx.
Sean
On 17 Dec 2015, at 4:07 am, Jen Bottom <jen.bottom@gmail.com> wrote:
It is my understanding that RAM and RIM only work on Windows.
This is not great for me, as I support a product called Git Fusion (among others) which only runs on Linux.
I have a 'tmate' server set up, but I am finding that a lot of the customer's we support expect WebEx, GoToMeeting or similar.
Trying to get them to jump through any extra hoops so that I can support them is tricky ans usually results in "We will wait for the US to com eonline" or similar.
Given that the customer has to install something for the Serotek solutions to work, I don't personally consider it much of a jump for them to install NVDA and NVDA remote, also they are free.
However, I find that as soon as I say the word "screen reader" to a customer, who is not always very tech savy and usually stressed, they freak out.
It would be nice to have a cross-platform solution.
Tmate only works for terminals (Unix and Linux).
Cheers, Jen.
On 12/15/15, Ryan Shugart <rshugart@ryanshugart.com> wrote: Unfortunately not. While I’ve gotten Window-Eyes to install through SCCM, the way that AISquared bundles their updates is not very conducive to delivering them through an automated process, at least that I’ve been able to figure out. While the main installer has a silent install flag the updates don’t, and you can’t use the main installer to do an update from a previous version, you have to use a specific update installer. With time I could probably rap the installer in a script and perhaps do something with it that way, I just don’t have the time. For what its worth, Citrix is heavily used where I work too, but I just install my own applications on my workstation and RDP whenever I need to get to a server. Longterm the idea is to move more toward a VDI infrastructure, which is where a lot of companies are going, but I don’t think anyone’s thought through the accessibility implications yet. Ryan
On 12/15/15, 10:18 AM, "Blind-sysadmins on behalf of Katherine Moss" <blind-sysadmins-bounces@lists.hodgsonfamily.org on behalf of Katherine.Moss@gordon.edu> wrote:
Can't you bake Window-Eyes updates into the SCCM/WSUS update process? (and that's the current issue at my company' Citrix is used for some applications, and the Mass Commission only supports JAWS, to getting Window-eyes to be recognized it sort of hard.)
-----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart Sent: Tuesday, December 15, 2015 12:40 AM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] remote desktop solutions
I have Window-Eyes installed on about 200 servers where I work, probably more now since we bake it into the base image so whenever a new server gets deployed its just ready to go. My biggest complaint is its a paine to keep all those copies up-to-date. Mostly I don’t worry about it, but that means I’ve got Window-Eyes all the way from 7.1 to 9.2 running on various servers. That can be a paine. I have an SCCM collection to tell me what’s where but I’d love a more automated way to update it across the environment. I know I’m in a unique situation, or relatively unique, but I think about the government agencies that employ tons of blind people, and wonder how they keep all those screen readers up-to-date. Ryan
On 12/14/15, 12:44 PM, "Blind-sysadmins on behalf of Barry Toner" <blind-sysadmins-bounces@lists.hodgsonfamily.org on behalf of barry@tonermail.co.uk> wrote:
> Hi, > > Or even if it's internal and you are expected at any one time to > log into > 1 of thousands of servers as I was and was turned down from a > post for Allstate because of this. > Hence why I'm now studying the Linux LPI Essentials in the hope > I'll be able to get a job using SSH for remote access. > > Barry. > > -----Original Message----- > From: Blind-sysadmins > [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On > Behalf Of Sean Murphy > Sent: 13 December 2015 02:14 > To: Blind sysadmins list > Subject: Re: [Blind-sysadmins] remote desktop solutions > > All, > > The problem with all the remote control solutions is that you > require screen reader to be installed. Thus if you support > customer’s who do not like this or have a platform that your > software doesn’t work on. Then you are out of luck. > > It is fine for internal customer’s as you can educate. Far more > difficult for external customers. > > Sean >> On 12 Dec 2015, at 2:34 pm, Guerra Access Technology Training >> LLC <gaccesstt@gmail.com> wrote: >> >> JAWS Tandem, Remote Incident Manager, >> >> >> Respectfully, >> >> Guerra Access Technology Training LLC An Authorized state of >> Minnesota Vendor for Technology Training >> >> Call Guerra Access Technology Training LLC guerra Access >> Technology Training LLC Visit Guerra Access Technology Training >> on the Web >> >> -----Original Message----- >> From: Blind-sysadmins >> [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On >> Behalf Of Kathryn Jedynak >> Sent: Friday, December 11, 2015 7:15 PM >> To: Blind sysadmins list >> <blind-sysadmins@lists.hodgsonfamily.org> >> Subject: [Blind-sysadmins] remote desktop solutions >> >> Hello all: >> I would like to know what remote desktop solution do you use for >> helpdesk support? Do any of you use the remote assistance >> feature that comes with system center? I find system center >> clunky to use with a screen reader. In my experience, Window >> Eyes works the best with it so far. It looks like nvda remote >> is the most responsive right now. Is anyone using either nvda >> by itself or nvda remote in a corporate environment? I know >> there was a post on here about the nada remote relay server developed by techno-es. >> _______________________________________________ >> Blind-sysadmins mailing list >> Blind-sysadmins@lists.hodgsonfamily.org >> https://lists.hodgsonfamily.org/listinfo/blind-sysadmins >> >> >> _______________________________________________ >> Blind-sysadmins mailing list >> Blind-sysadmins@lists.hodgsonfamily.org >> https://lists.hodgsonfamily.org/listinfo/blind-sysadmins > > > _______________________________________________ > Blind-sysadmins mailing list > Blind-sysadmins@lists.hodgsonfamily.org > https://lists.hodgsonfamily.org/listinfo/blind-sysadmins > _______________________________________________ > Blind-sysadmins mailing list > Blind-sysadmins@lists.hodgsonfamily.org > https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins
_______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins