Re: [orca-list] accessiblity in chrome

[Piñeiro <apinheiro igalia com>]

From: jonathan Nadeau <j nadeau charter net>

> A while ago I filed a bug against chrome and this is the latest. Maybe
> someone could help with this.

I would give a hint here, not sure if useful.

> Comment #5 on issue 24585 by dmazz    chromium org: orca screen reader  
> doesn't work with chromium
> http://code.google.com/p/chromium/issues/detail?id=24585
<skiping>

> However, if anyone in the community would like to work on implementing
> ATK  
> and Orca support in Chrome, we'd be more than happy to help them get  
> started and review the patches.

JFYI, Chrome uses WebKit as web engine.

Good new: At this moment some people are implementing the
accessibility support on WebKit in ATK terms for that, as GNOME has
decided to start to use it. In brief, the ATK support works as as
wrapper/proxy of the in-WebKit a11y support.

Bad new: At this moment, ATK support is only available if you are
using the GTK+ port. So saying that WebKit supports ATK is not 100%
true, it is WebKitGtk+ the one which supports it.

Not as so good new: although there are ATK support in WebKitGtk+,
right now it is not complete. Orca maintainer, Joanmarie Diggs, has
created a metabug with all the issues related with that [1]. She is
doing a awesome work reporting bugs and creating patchs. Xan Lopez
(from Igalia) is working as well, mainly reviewing patches. Some weeks
ago Mario Sanchez (also from Igalia) started to work in this field
also.

Anyway, I will add a comment on the bug. It would be a pity that the
work done in this port can't be used in other ports.

[1] https://bugs.webkit.org/show_bug.cgi?id=25531

BR

===
API (apinheiro igalia com)