Re: [orca-list] Update on Jokosher accessibility

[Steve Holmes <steve holmes88 gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Hi Mike,

I think it is exciting to see a software developer such as you to come
onto the list and get involved with the finer points of how to make
the program more accessible; thanks much for doing this.

You had asked about your documentaion/help and whether or not an
accessibility section should be added or not.  That might be a good
idea, particularly if the methods of interaqcting with the program
might differ from how other sighted people might use it.  An example
might be the keyboard alternatives to mouse clicking and the like.
But certainly if the keyboard methods are commonly used by other users
as well, then just listing these keystrokes in the normal keyboard
shortcuts section should suffice.

I've never used nor heard of jokisher til now so this thread is
interesting to me.  In the past if I had audio editing to do, I used
Goldwave in Windows, another fine sound editor but to be able to do
that sort of thing over here in Linux, that's more exciting indeed.

On Sun, Apr 18, 2010 at 02:15:30AM +0100, Michael Sheldon wrote:
> Hi Joanie
>
> On 18/04/10 01:47, Joanmarie Diggs wrote:
> > However, as I use shift+left/right, I'm not seeing any way to identify
> > the new location of the point. Are you exposing that value to ATs? If
> > not, perhaps an object:property-change:accessible-value emitted by the
> > focused event....
> >
> > Once I press space to cut, I'm not seeing any
> > object:children-changed:add events to (which would be a nice way to
> > confirm the successful split to the user.
>
>  Excellent, these sound like much better ways of exposing that
> information, thanks for pointing them out. I'll see if I can make a
> little time tomorrow to play with implementing this.
>
> > In light of the fact that Jokosher is even more accessible than I
> > realized (D'oh! and thanks!!), what probably makes the most sense is for
> > me to start on the Orca script for Jokosher, which I'll begin tomorrow.
> > As things come up for which there seems to be no way to provide feedback
> > non-visually, I'll ask and/or file a bug in launchpad. And we can go
> > from there.
>
>  Great, when you do find aspects that need extra support from our
> end would it be possible for you to make your orca script available
> to me somehow (either via e-mail or attached to the relevant bug
> report) so I can test the fixes myself?
>
>  Thanks,
>   Mike.
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
> Log bugs and feature requests at http://bugzilla.gnome.org
> Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAkvLG8QACgkQWSjv55S0LfHdpwCeLo9ndBbLi/Zd16MYGaMXmrEK
9GwAoNYkfqnYqmwtnWxzGIGWxpn9xfBb
=MpsD
-----END PGP SIGNATURE-----