[jareds]

Is there any possibility of insuring that Workspaces will be accessible to users of assistive technology? I use a WIndows PC because that's what has the best screen reader support, a quick google search didn't turn anything up about running a screen reader in the workspace and having it's sound piped back to the thin client.

[mgkimsal]

coincidentally, that's what I was doing in march, and... surprisingly, it sort of worked.

client had JAWS, and the JAWS installer read itself to me while it was installing - I was rather impressed. Had to reboot, and it never came up after that - assuming it was related, but never figured it out.

The NVDA screen reader did work, as well as the windows voice assistant thing itself. both would generate audio in the workspace, and I was hearing it over my el capitan local setup.

[jareds]

The Jaws problem may have been video card drivers. Jaws installs it's own video driver that I have found to not work under Virtualbox unless guest additions are installed. I could see there being something in the Amazon virtualization solution that could cause problems with the driver.

[mgkimsal]

I wanted to dig in to a bit further, but the client just reset the whole thing and said "you don't get JAWS now". Project cancelled soon after that - unrelated to JAWS/workspace.

Don't have time now, but hopefully it will be resolved at some point. NVDA was 'good enough' for the testing I was doing, and it was pretty slick to know the audio was streaming and working without any extra configuration. Probably old hat for some folks, but I'd never experienced that before. :)

[commandshift90]

I would imagine that if the screen reader running on the Workspace itself outputs its audio to the standard audio output, you would have no problems.