Re: Mozilla 1.7 rc1 issues.

[Luke Yelavich <themuso themuso com>]

Hi all
I second all suggestions proposed so far, but I am also thinking that we 
may need something to indicate blocked quotations, as well as headings of 
various levels.

Will probably think of more tomorrow, but this is a start from me.

Luke

At 10:24 AM 30/04/2004, Peter Korn wrote:
> Hi Luke, Tom,
>
> As you have deduced, Mozilla's present caret navigation leaves much to be 
> desired.  This is being worked on.  Alas, I don't have an estimate of when 
> it will get significantly better (beyond "as soon as possible").
>
> I'd like to open a related topic: what do you (and the other Gnopernicus 
> users on this alias) want in a web browsing interface?  Caret navigation 
> is critical for mouseless operation (a mouseless user must be able to do 
> anything a mouse-ed user can, including selecting text to copy to the 
> clipboard), and good feedback from Gnopernicus to caret navigation should 
> result in a basic level of blind/low-vision accessibility (especially if 
> you include the usual Ctrl-arrow, home/end stuff).
>
> Now, is that sufficient?
>
> Sufficient or not, what would you add if you could add something to 
> this?  Is there an existing set of keybindings and approach to the problem 
> you particular like and think would be a good model (e.g. JAWS browsing, 
> Window Eyes browsing, Home Page Reader, etc.)?
>
>
> Regards,
>
> Peter Korn
> Sun Accessibility team
>
>
> Luke Yelavich wrote:
> > Hi Tom
> > At 06:01 AM 30/04/2004, Tom and Esther Ward wrote:
> >
> > > Hi, List.
> > > Recently, I grabbed the Mozilla 1.7 rc1 source code, and compiled it.
> > > I am having several issues I would like to discuss about it.
> > > I noticed that while tabbing through the page I can get spoken feedback on
> > > the frame titles, but none of the links on the page get announced.
> >
> > I had the same problem as well, even under GNOME 2.6.
> >
> > > I also noticed on forms the buttons will get announced, but the edit 
> > > fields are
> > > ignored and are not spoken.
> >
> > The same here also.
> >
> > > When carot browsing is activated I had assumed it would allow me to uparrow
> > > and down arrow through the page elements or at least the text on the pages.
> > > Again I get no speech feedback.
> >
> > Since I have a bit of sight, I have found that the carrot seems to start 
> > at the bottom for some reason, and pressing CTRL+Home doesn't always 
> > help, and you don't know when you are at the top of the page.
> > Another thing that I think I have mentioned earlier, is that the carrot 
> > browsing mode doesn't take tables into consideration at all. One has to 
> > know where the carrot is, and press CTRL+Right Arrow, or Right arrow 
> > alone to get to the other section of the table.
> >
> > > Is there anyone or any specific list I should address Mozilla accessibility
> > > with? I would like to get involved with testing Mozilla, help find
> > > accessibility issues, and report those problems to the developers for future
> > > fixes/changes.
> >
> > http
> > ://mail.mozilla.org/listinfo/mozilla-accessibility
> > Is the mailing list.
> >
> > > Currently, I linked Mozilla with gnome 2.4, but plan to update to Gnome 2.6
> > > in the next couple of weeks. Does it make a large difference with Mozilla
> > > weather I use Gnome 2.4 or Gnome 2.6?
> >
> > It will perhaps be a bit more responsive, but that is about it I think.
> > Luke
> > _______________________________________________
> > gnome-accessibility-list mailing list
> > gnome-accessibility-list gnome org
> > http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list