4 ms·
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 wa
by mgkimsal 10y ago
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 10y agoThe 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 10y agoI 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. :)