Re: [orca-list] Accessibility of Chromium / Google Chrome

[Storm Dragon <stormdragon2976 gmail com>]

Hi,
I am willing to help test patches. I am currently using Vinux 3.0 which is based on Ubuntu 10.04 Lucid. another idea may be to subscribe to the Vinux support list and see if someone won't add the patched versions to the testing repositories so that you can get a lot of testers who can install it through ordinary, sudo apt-get install ... methods.
thanks
Storm

--

Vinux Publicity Coordinator: http://www.vinuxproject.org/
Registered Linux user number 508465: http://counter.li.org/
My blog, Thoughts of a Dragon: http://www.stormdragon.us/
How many Internet mail list subscribers does it take to change a lightbulb? http://goo.gl/eO4PJ
My last.fm profile: http://www.last.fm/user/stormdragon2976
"Have you ever been alone at night, thought you heard footsteps behind, and turned around and no one's there? And as you quicken up your pace you'll find it hard to look again because you're sure that someone's there."
Iron Maiden

On Mon, 2011-08-15 at 16:18 -0500, Kyle wrote:
> Count me. In! I'm not a developer, but if compiling from source isn't too tricky, I've been dying to bang around on this thing, so I'll definitely be interested in applying and testing any accessibility patches.
> ~Kyle
> Sent from my Wishdroid! :)
>
> ________________ Reply Header ________________
> Subject:	[orca-list] Accessibility of Chromium / Google Chrome
> Author:	"Dominic Mazzoni" <dmazzoni google com>
> Date:		August 15th 2011 15:10
>
> Hello,
>
> I'm one of the developers of Chrome accessibility support at Google. I
> know that there's been some interest in making Chrome accessible with
> Orca on Linux, so I decided to join this list to talk about it some
> more.
>
> To answer some questions from previous posts, yes, Chrome does use
> GTK+, so making the user interface accessible will be relatively easy.
> Unfortunately, Chrome does not use the GTK+ port of Webkit, and there
> are technical reasons why it's not possible for us to use that code
> directly, so we'd have to rewrite most of that code.
>
> My question is, are there any Orca / GTK+ developers on this list who
> would be interested in working on this with us? Based on my experience
> making Chrome accessible on Windows and Mac, making a web browser
> accessible is very tricky and complicated, and almost impossible
> without some help from someone who's really familiar with the screen
> reader's source code. Ideally I'd like to find someone who'd be
> willing to compile Chromium from source and then help test patches
> that make it accessible and help debug things when Orca doesn't behave
> as expected.
>
> - Dominic
> _______________________________________________
> 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
>
> _______________________________________________
> 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