you may already know this, but if not, you can find some general rules
on diverse accessibility issues related to web applications here:
http://www.w3.org/WAI/
It is mostly about websites, but it helped me to figure out in one
project how should an 'accessible' application behave...
also there is a relatively old but still useful document at:
http://trace.wisc.edu/docs/software_guidelines/software.htm
bets regards
Viktoras
Tereza Snyder wrote:
On May 5, 2008, at 10:12 AM, David Bovill wrote:
My guess is that this would all be much harder than making the app -
"self-voicing":
and Mark Schonewille wrote:
I have tried a few screen readers and none can work with Revolution.
The screen readers I tried usually use the mouse cursor to determine
which control or text should be described by means of audio. You can
easily do this with Revolution's speech features
It looks like self-voicing is the way to go. Not too different from
single-switch access, code-wise.
Thank you. You've spared me endless tests and incidentally let me
sound like I know what I'm talking about in front of a client.
tereza
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
