Hi,
I am blind, so use a screen reader called jaws for windows to access my pc. However, in many situations, such as virtual instruments, it cannot, or has trouble interpreting the data on the screen (whether because it's all pictures, or anything else), so I was wondering if anyone (whether from vsl or from the community) could give me an answer on this question:
Is the vsl player accessible for the blind using screen readers, whether fully accessible (or if not, at least the browser). I've had many instruments that were very inaccessible, but the browser is not, so using a script for jaws called hotspot clicker, I can make a keystroke that moves the mouse to the browser button and clicks it. Then the browser window opens, which is accessible. I have also had some (rather frustrating) experiences with software that the browser is not accessible at all, so even if I wanted to I could not use hotspot clicker to browse for instruments to load, as if I were to program every single instrument into a new click (which would take days/weeks/months), then the slightest change, such as adding a new instrument which doesn't go after the others, or deleting an instrument would screw it up entirely. You can understand, then, why I ask if vsl is, if not totally accessible (which is unfortunately very common in software instruments these days), at least is the browser?
Thanks,
-Michael.
-
accessibility of vsl player for the blind
-
Hello Michael,
Thanks for posting your question.
I´m afraid our software is not accessible for blind users, you need additional guided mouse-action to switch between the various tabs of the Vienna Instruments Sample Player....
Sorry to have no better news.
Best,
Paul
Paul Kopf Product Manager VSL -
lilmike, I would like to welcome you to the forum.
My situation is a bit different from yours in that I am legally blind, not total (from your description I am guessing you are totally blind).
For what its worth, my overall music software experience has been that newer versions of various company's software have often been increasingly difficult to use for those with visual impairments. One program that used to be fully functional with JAWS was Cakewalk's Sonar, but that was several years ago, and I do not know if that is still the case. Depending on what you are seeking to do musically, that might be worth exploring.
Another option, if you happen to use MIR Pro/VE Pro, though tedious, might be to get someone to set up three or four templates for different setups, say chamber orchestra, full orchesta, soloists, etc., within your working environment. The articulations could be mapped out for each instrument, and consistent keyswitches setup. A map of each setup/template could then be created in MS Word or someother document that you could access, that would tell you what is where within the VSL environment for each instrument. The limitation would be that you could not change that setup, but would have to live with the design.
On a somewhat simpler level, someone could create a similar type of individual instrument profiles that you could then access from within your sequencer - again with master maps in MS Word that you could access to know the details. This option could allow a bit more mixing flexibility as all adjustments would be made from within your sequencer.
Note that I have created these sorts of documents in MS Word for myself, for each instrument profile, though I am still using the older MIR SE. When one has created consistent instrument templates, with articulations mapped in a similar way for each instrument family - strings, woodwinds, and so forth - one can semi-memorize what is where.
Admittedly, none of these options are ideal, but in my own situation, I have found that getting something that will work at all is often more important than the time it takes to get there.
Note to VSL: While in my own situation things are not "ideal", the visual screen designs are at least workable, and your use of sans serif fonts (as opposed to what is in the "noble competition's" Play software, which I visually cannot use at all) at least makes it possible to read most of them. The use of text in addition to just a graphics display is most helpful, particularly where the graphic representations are not something I can decipher.
-
I often wonder about this kind of problem. Would a system of keyboard shortcuts be a solution here, to help navigation? A blind woman I once knew, who was a particularly gifted computer scientist, was once working on a haptic feedback system to allow her to feel her way around windows using some kind of mouse that let her feel the difference between various colours. The more I studied her work, the more I was convinced that many possible solutions for blind users also had huge potential for sighted users as well. Having to look at different parts of the screen and then move the mouse is, I think, a slower way of working. Keyboard shortcuts are one mode of interaction with a program for which being blind is not a disadvantage, and also provide a very quick way of working for sighted users as well.
Anyway, sorry to move off topic, but I just wondered if the workflow enhancements that I like in programs would also benefit blind users. I'd love a really quick way to interact with VI Pro, without so much clicking. It's probably the most efficient and user friendly sample player for sighted users, but with so many articulations available, there is always a huge amount of mouse clicking.
-
Hi all; I'm totally blind and the studio I work for, very recently bought VSL Special Edition volume 1 bundle. I'm afraid that didn't happen with much consultation about whether it is accessible or not. With it here and installed, I am wondering if at least there's a work around that would enable me to load the various instruments into my Sonar projects, so that if need be, I could at least use them, and if nothing better, tweak it once I have it exported to audio? We're using Sonar 8.5 (for that's the last version that is still accessible and works with CakeTalking.
