Improving Gnome Desktop Accessibility

[Jacob Schmude]

And how easy is it to learn when they follow an instruction, such as to
launch the software sources application, and this causes Orca and
accessibility to hang and they don't know how to get out of it? Sure
they can drop to the command-line and do it but that's a lot more
technical than a name. I'd say, in balance, that requiring the
command-line causes more issues than hearing panel information. Again
though, these are my opinions and observations and I don't mean any
disrespect. I just think priorities should be on actual performance and
crash-related problems first. They're the ones that hit hardest and make
the most impression when they do.

On Tue, 2010-03-02 at 14:48 +0530, Arky wrote:
> Hi Jacob, 
> 
> 
> > The only true accessibility issue I see in your list is the clock. 
> The
> > rest are cosmetic or a matter of preference, and with actual bugs
> > coupled with GNOME 3 on the horizon, I think focus should 
> be on that.
> > What good is it if GNOME just says "desktop" when I 
> still can't access
> > Webkit-based apps properly, or can't launch 
> apps as root as I should be
> > able to do from the GUI?
> 
> I have found a certain low impact improvements like providing less technical information or providing a better accessible name will make it easier for non-technical blind users to learn gnu/Linux desktop.
> 
> Cheers
> 
> --arky 
> 
> 
>  Rakesh 'arky' Ambati| IT Consultant| http://www.braillewithoutborders.org | Blog: http://playingwithsid.blogspot.com
> 
> 
>       Your Mail works best with the New Yahoo Optimized IE8. Get it NOW! http://downloads.yahoo.com/in/internetexplorer/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-accessibility/attachments/20100302/b2113f7d/attachment.pgp