Yeah, I understand your logic. When trying to market a product
sometimes it comes down to mob rule. That still however doesn't wave
my concerns about it. Now, a question.
When people produce games is it possible to turn this feature off I.E.
just use Sapi instead of Jaws support etc or are we stuck with
whatever the game designer decides? My real concern is if someone who
really loves Jaws decides only to support that screen reader and
decides to screw everyone else who might want to use Window-Eyes,
NVDA, Sapi, whatever just because they have an opinion that by
supporting Jaws only they will be supporting 90% of the market etc. It
would have to be universally understood by adding screen reader
support every game written with BGT must offer alternative speech
output systems. That no game can make this or that screen reader a
default preference. Any thoughts or comments on this?
On 1/20/11, Philip Bennefall <phi...@blastbay.com> wrote:
> Hi Thomas,
> Right, that strengthens my point about having screen reader enumeration in
> BGT if, of course, we want this support at all. I agree with you that it's
> not a critical or even important thing to have in a game engine, but I
> reason like this. Customers want it, customers pay the bills, customers get
> what they want. That's how I have to do my business, e.g. submit to popular
> demand even if I might not strictly agree with it on a personal level. Of
> course there are a lot of cases when I won't do it, but for something as
> simple as this I don't have a problem adding it.
> Kind regards,
> Philip Bennefall
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.