- From: Charles McCathieNevile <chaals@opera.com>
- Date: Fri, 10 Jun 2011 12:24:07 +0200
- To: www-amaya@w3.org, "Jeff Hunt" <jeffhunt90@gmail.com>
On Fri, 10 Jun 2011 03:08:23 +0200, Jeff Hunt <jeffhunt90@gmail.com> wrote: > A teacher of the blind supplying resources for them has asked me the > following: > > 'My main question at the moment is how come JAWS and SATOGO screen > readers don't read AMAYA. I desperately need to know that.' > > Does anyone know? I would have expected all text to the screen would > be read regardless of software. No, it isn't. There are standard ways of putting text on the screen (and, more importantly but also more complicated in practice, user interface buttons, sliders, text boxes, etc) that are required if you want them to be available to a screen reader. From time to time these change, and they are different for different platforms. Like many cross-platform applications, Amaya is built using a custom approach to rendering that doesn't work well with screen readers. Changing this is likely to be a fairly substantial amount of work, because simple approaches will have a *huge* impact on performance to the extent that the application becomes difficult to use. That said, if anyone has programming skills and plenty of time, it would be a great thing to do... cheers Chaals -- Charles McCathieNevile Opera Software, Standards Group je parle français -- hablo español -- jeg lærer norsk http://my.opera.com/chaals Try Opera: http://www.opera.com
Received on Friday, 10 June 2011 10:24:39 UTC