Re: Yelp and a11y
- From: Marco Pesenti Gritti <marco gnome org>
- To: Shaun McCance <shaunm gnome org>
- Cc: bill haneman sun com, korn sun com, desktop-devel-list gnome org
- Subject: Re: Yelp and a11y
- Date: Fri, 14 Jan 2005 11:36:12 +0100
On Mon, 2005-01-10 at 22:01 -0600, Shaun McCance wrote:
> In the 2.9 series, Yelp is using Gecko as its rendering engine. It
> seems that the accessibility isn't quite up to par. On my machine, at-
> poke is able to see the text of the page, but it doesn't seem to show
> the links as anything special.
>
> http://bugzilla.gnome.org/show_bug.cgi?id=157941
>
> This is a major problem. If it can't be fixed soon, then I'll have to
> punt another release cycle with Yelp. It's too late in the game to put
> gtkhtml2 back onto HEAD and hook all the code paths up.
Hi,
so we now have probably a clearer picture, still it's going to be a
difficult call...
The problems we know about are:
1 Hyperlinks not showed in at-spy
That actually seem to be a non issue. Quoting Louie Zhao (mozilla sun
accessibility guy):
"In Gnome, Hyperlinks are normally included in HyperText and has
no standalone accessible object presented in accessible tree of at-poke.
I am not sure whether this is the answer for your question. Feel free to
contact me if you have any question."
2 Hyperlinks not showed in gok UI Grab
The patch is now in mozilla 1.8, but the final release is scheduled for
March which is too late for GNOME 2.10
3 There are apparently more patches in Sun branch that will not be
upstream in time for GNOME 2.10. I dont know what concrete problems they
cause though. See:
http://bugzilla.gnome.org/show_bug.cgi?id=157941#c10
So, basically, if we want no accessibility regression with unpatched
mozilla in 2.10 we will very likely have to use gtkhtml. (Note that I
dont have a strong opinion here... just trying to provide infos).
Marco
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]