The question was why accessibility to the blind was
such an abhorrent concept to mainstream game designers. I refuse to say
we've been trying to explain it to them for years and most refuse to
Well, as I have said so many times already most of it comes down to
numbers of potential end users and money. If a feature like
accessibility isn't going to sell millions of extra copies, and it costs
them x to produce that accessibility it isn't going to happen. It is
simple supply and demand unfortunately.
Another issue to consider is simply that accessibility is not taught in
college courses either. Anyone can pick up some programming credits at a
local community college, tech school, etc but that will generally
consist of programming theory and basic training in language x. None of
that training is hands on instruction on ways to make your applications
accessible to a blind user. In fact, this lack of understanding among
programmers about accessibility needs is why the Gnome foundation has
build accessibility directly into the core Gnome 2.x desktop. Apple has
also set about building accessibility features into the core Cocoa API
for Mac OS. The concept on Linux and Mac now is rather than putting
accessibility into the hands of the third-party developers that
operating system core APIs do what is necessary by default leving the
third-party developers to concern themselves with writing the
application and let the various access features built into the API
handle the access needs for the application by default.
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.