Re: help with data on webkit accessibility

Hey Xan.

The caret navigation ones are key:

* 25526 - Additional support is needed for caret browsing. Almost done,
but home, end etc. are waiting for something in DRT.

* 25533 - Elements on the same line should be treated as such by caret
navigation. Hasn't been touched.

We also need to unbork the table hierarchy (30895) because if memory
serves me, tables are used to display tables of contents. And presumably
could be used to display a table of commands, etc. Related to this is
30896 - getting the column header.

Making sure that we have the correct states on text objects (27048) also
needs doing. That hasn't been touched, but we needed to collapse the
text objects first anyway. This one shouldn't be hard.

I need to get back to 25677 (extents for characters and ranges). I had
that pretty much working, but that was before the collapsed hierarchy.

I'm afraid I had to stop working on these things largely due to Firefox
regressions and changes. :-( Hopefully starting this weekend, I'll be
able to focus on WebKitGtk again.

The other issues need addressing as well, but in terms of basic Yelp,
the above are the priorities.


On Tue, 2010-02-23 at 19:47 +0200, Xan Lopez wrote:
> On Tue, Feb 23, 2010 at 7:37 PM, Kenny Hitt <kenny hittsjunk net> wrote:
> > Hi.
> > After the recent discussion on this list, I filed a bug in Debian to try to
> > ask them to not use webkit for yelp.
> > The Debian maintainer replyed and told me he thought the accessibility issues
> > were resolved.  A quick sirch for webkit on didn't
> > find any bugs.  I'm sure I didn't
> > use the right search terms.
> > Would someone who knows please provide me with links to bug reports or post
> > comments to:
> >
> >
> >
> > The Debian maintainer said the gecko backend wasn't currently in a buildable
> > state and gave me the impression webkit is likely to stay the default unless
> > I can convince him differently.
> It would be interesting to know which bugs exactly are preventing you
> from actually using yelp/webkit. There's always going to be bugs in
> our a11y code because there's always bugs in any non-trivial body of
> code, so that's not a good metric of whether you should be using
> something or not. Are all the Orca blocker bugs in webkit issues that
> absolutely must be fixed in order for yelp to be useful? Some? Which
> ones? Etc.
> Cheers,
> Xan
> >
> > Thanks.
> >          Kenny
> >
> > BTW, Ubuntu users might want to consider filing a similar bug so Ubuntu
> > knows about the problems with webkit.
> >
> > _______________________________________________
> > gnome-accessibility-list mailing list
> > gnome-accessibility-list gnome org
> >
> >
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]