Re: RunRev Accessibility

[viktoras didziulis]

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
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Re: RunRev Accessibility

[Tereza Snyder]

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


--
Tereza Snyder
Califex Software, Inc.


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Re: RunRev Accessibility

[Mark Schonewille]

Hi Tereza,

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. Additionally, it  
might be useful if your app could run from the command line. Perhaps  
you could turn on speech features automatically, after reading the  
system's universal access settings.


Best regards,

Mark Schonewille

--

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Our servers may be off-line between 28 April and 1 May. If you have an  
urgent request, you can contact us at <[EMAIL PROTECTED]>.  
Apologies for any inconveniences.






On 5 mei 2008, at 16:57, Tereza Snyder wrote:


Hiya all,

Does anyone know (spare me the testing!) whether apps made with  
RunRev using ordinary controls are accessible to screen readers out  
of the box? I have over the years implemented various accessibility  
modes in apps using Rev—single-switch access comes to mind—but I've  
yet to tackle screen-reader access in Rev. I know Hypercard wasn't  
accessible because I had to implement a blind-access mode for a  
major application back in the day when I worked at the Trace Center (http://trace.wisc.edu 
), and I suspect Runtime Revolution isn't because—at least in the  
beginning—'system' controls were emulated. But is that still the  
case? on all platforms?


A client has a C application that has bogged down in development. I  
know I can redo it in Rev and carry it forward expeditiously;  
however there's a federal grant involved and furthermore the client  
is committed to universal access.


Anyone have a clue?

tereza



___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Re: RunRev Accessibility

[David Bovill]

Not much help maybe - but here is a link to the API's that could be
implemented:

   - http://en.wikipedia.org/wiki/Screen_reader#Accessibility_APIs

And a free Apple based tool for testing?

   -
   
http://developer.apple.com/documentation/Accessibility/Conceptual/AccessibilityMacOSX/OSXAXTesting/chapter_5_section_2.html#//apple_ref/doc/uid/TP40001078-CH210-DontLinkElementID_48

My guess is that this would all be much harder than making the app -
"self-voicing":

Self-voicing applications
>
> Some programs speak or make other sounds so that they can be used by blind
> people or people who cannot see the screen. These programs are termed
> self-voicing  and can be a form
> of assistive technologyif 
> they are designed to remove the need to use a screen reader.
>


2008/5/5 Tereza Snyder <[EMAIL PROTECTED]>:

> Hiya all,
>
> Does anyone know (spare me the testing!) whether apps made with RunRev
> using ordinary controls are accessible to screen readers out of the box? I
> have over the years implemented various accessibility modes in apps using
> Rev—single-switch access comes to mind—but I've yet to tackle screen-reader
> access in Rev. I know Hypercard wasn't accessible because I had to implement
> a blind-access mode for a major application back in the day when I worked at
> the Trace Center (http://trace.wisc.edu), and I suspect Runtime Revolution
> isn't because—at least in the beginning—'system' controls were emulated. But
> is that still the case? on all platforms?
>
> A client has a C application that has bogged down in development. I know I
> can redo it in Rev and carry it forward expeditiously; however there's a
> federal grant involved and furthermore the client is committed to universal
> access.
>
> Anyone have a clue?
>
> tereza
>
>
> --
> Tereza Snyder
> Califex Software, Inc.
>
>
> ___
> use-revolution mailing list
> use-revolution@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

RunRev Accessibility

[Tereza Snyder]

Hiya all,

Does anyone know (spare me the testing!) whether apps made with RunRev  
using ordinary controls are accessible to screen readers out of the  
box? I have over the years implemented various accessibility modes in  
apps using Rev—single-switch access comes to mind—but I've yet to  
tackle screen-reader access in Rev. I know Hypercard wasn't accessible  
because I had to implement a blind-access mode for a major application  
back in the day when I worked at the Trace Center (http:// 
trace.wisc.edu), and I suspect Runtime Revolution isn't because—at  
least in the beginning—'system' controls were emulated. But is that  
still the case? on all platforms?


A client has a C application that has bogged down in development. I  
know I can redo it in Rev and carry it forward expeditiously; however  
there's a federal grant involved and furthermore the client is  
committed to universal access.


Anyone have a clue?

tereza


--
Tereza Snyder
Califex Software, Inc.


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution