Yes, but there are technical considerations here. You know as well as
I do that Jaws is infamously problematic with games using DirectX.
Accessible game developers have been telling their customers for years
to unload their screen reader or put it to sleep when running game x.
That's because they know Jaws especially causes games to lock up and
doesn't work well with DirectInput. Now, why would a developer turn
around and try to use the Jaws API for speech output knowing full well
that combo is technically going to be a desaster. I don't know how
many VI users out there use Jaws, who don't know a thing about
programming, want support for Jaws built in it still doesn't make it
the right thing to do from a stability and best practices point of
view. For that reason I'm firmly against adding direct support for
Jaws in my games. The only way I might even consider such a thing is
if every single Jaws user called up Freedom Science Fiction and
screamed at them to fix their piece of junk screen reader.
On 1/4/11, Liam Erven <liamer...@gmail.com> wrote:
> That is the wrong attitude to take. Whether or not you care for a particular
> screen reader, if your potenetial customers are using it, then you have an
> obligation to support it. I personally do not use NVDA or care very much
> for it, but when bgt eventually gets screen reader support I will support it
> if my games end up using screen readers for any sort of speech output.
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.