Anabelle,

          If you have a "direct line" to the folks at Audionamix the first 
thing I'd do is give a first person singular testimonial about what it means to 
you to have programs be accessible, period, and to offer examples to them of 
those that are and, just as importantly, are not.  Most companies are becoming 
much more concerned with making products that have the maximum accessibility 
that they possibly can, and very often it's pure ignorance of what that means, 
both from a coding standpoint and the end-user standpoint.  If ADX Trax Pro 
turns out to not be accessible with JAWS consider using it as the "are not" 
category - it drives the point home.  If you happen to have a sighted assistant 
(as this next suggestion pretty much requires it) you might try to create a 
live screen capture video of JAWS interacting with their product (or not 
interacting, as the case may be) with an online screen recording tool such as 
the one at either showmore.com or apowersoft.com.  There really are times where 
a picture, or in this case a video, is worth a thousand words.

          Then, if they show an interest in pursuing this, I would encourage 
them to actually get in touch with Freedom Scientific for JAWS, AI Squared for 
Window-Eyes, and nvaccess for NVDA (which is open source and actually promotes 
accessibility testing as part of its website).  All of these entities know what 
is required for their software to successfully interact with other programs and 
I would imagine they'd be more than willing to share the essential design 
features required to make a program "play well" with accessibility software.  
There's nothing like going to the source (and it's in the business interests of 
the accessibility software makers to try to have as many other third party 
programs as is humanly possible "play well" with their products).

          Direct advocacy like you're proposing is more valuable in 
demonstrating your point than you can ever know.  Even though accessibility is 
becoming more and more important, this helps to drive home the point as to 
precisely why.

Brian

Reply via email to