Re: [orca-list] Accessibility of Chromium / Google Chrome
- From: Mario Sanchez Prada <msanchez igalia com>
- To: orca-list gnome org
- Subject: Re: [orca-list] Accessibility of Chromium / Google Chrome
- Date: Tue, 16 Aug 2011 12:58:10 +0200
As one of the developers working in a11y support in the WKGTK port, I'm
very happy about this (very good) piece of news :-)
On 08/15/2011 10:10 PM, Dominic Mazzoni wrote:
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.
Just out of curiosity, I'd like to know (as far as it's possible) some
details about why it was not possible.
I imagine using the same source code base of WK (that is, the chromium
port) for all the versions of chrome could be easier than using each WK
port for each version of chrome, but maybe I'm wrong.
Anyway, as I said, just wondering :-)
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.
I cannot agree more :-)
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.
I know how to build WK (at least the gtk port) and also the chromium
browser on my Linux machine (ideally a release build, dynamically linked
-otherwise I usually find problems), as well as ORCA and the ATK/AT-SPI
needs, so I think I could help on this too, whenever time permits :-)
Hope this helps.
] [Thread Prev