Hi. I think you are on the right track using Windows here, I don't think there is anything in Linux which supports this stuff. Have you tried contacting FS support? I have used a couple of virtual desktop solutions in this scenario, and usually there was something we needed to modify to get this working and I wouldn't have got to the bottom of this without help from FS. In one case it was video ram, and in another case it was some settings in the protocol. This was using VmWare and Citrix solutions so haven't used Amazon Workspaces. I take it you also have the remote license on your Jaws authorisation? Thanks. Andrew. Lukasz Golonka wrote:
Dear all,
My employer recently decided to move most of our software development activities to a remote systems accessed via Amazon WorkSpaces. By >default it just connects to an Amazon Linux 2 running Mate as an GUI, which obviously will not work with a screen reader. My initial idea was to >access this remote system via SSH, which is a supported scenario for accessing WorkSpaces, and while it will be possible to write and compile code >that way, there are some activities that require a GUI, accessing our GitLab instances via a web browser being a prime example. Note that these web >applications are not and will not be accessible from our main machines i.e. they are reachable only from the systems running inside the WorkSpace. >According to JAWS's documentation its remote access solution has support for accessing remote Windows inside WorkSpaces, so I gave this a try. >Sadly this either does not work, or I'm missing something very obvious. AWS supports two protocols when creating a remote machine: WSP and >PCoIP. When running JAWs on a remote machine using the former it does not detect that it is running in a remote access scenario and relies on >transferring audio to the client. For the latter while JAWS claims to be running in the remote mode the authorization is not taken from the client >JAWS's speech is also transferred as an audio and not using a remote channel. Has anyone tried and successfully used JAWS's remote support in >Amazon WorkSpaces? JAWS's documentation for remote access is sadly very basic in this area. Note that I am aware it should be possible to achieve >the similar goal by using NVDA Remote, however that will require a remote server which is visible both from my work machine and from the system >running inside the WorkSpace, which is going to be pretty difficult, as main reason for deploying WorkSpaces in the first place was separation of >these two environments. Obviously any alternative proposals for accessing remote Windows in WorkSpaces are very welcome. Thanks for your help!
-- Regards Lukasz Golonka