Re: Mozilla 1.7 rc1 issues.

["Tom and Esther Ward" <tward1978 earthlink net>]

Hello, Peter.
As a matter of fact I do have some thoughts, comments, and suggestions about
Mozilla's accessibility.

1. When carot browsing is activated it appears the focus is always moved to
the end of the page and not the top. This especially seams true when I
tested Mozilla under Win XP with Window eyes 4.5. As for gnopernicus I don't
have enough feedback in Mozilla and Gnopernicus yet to quite know anything
about Mozilla's behavior although I suspect carot browsing in Mozilla under
Linux would act in a similar way as the Windows port.
What needs to change is have the carot automatically find the top of the new
web page which is a good reference for those of us who are blind and use
assistive technologies.
2. The lynx web browser has a handy feature, number_links,  which I find
very helpful, and would like to see in Mozilla at some future point. The
number_links option in lynx asigns a number to every single link on the web
page, and all links can be accessed simply by entering that number.
For example I find the number_links option extremely helpful on web sites
such as yahoo which has several links on the page, and all I need do is
enter the number asigned to the mail link and lynx takes me imediately to
that link which is very handy and much quicker than tabbing through 30 or 40
links to get to that location on the page.
I think that a similar feature in Mozilla would be a great help to anyone
using a screen reader.
3. Windows screen readers have the ability to take all the links off of a
web page, and put them  in to a listbox. For example when insert+tab is
pressed in Window eyes a dialog appears with a list of links and two buttons
for go to link or activate link. I have found this is a very nice feature,
and one that  I think could be put in to Mozilla at some point.
4. As far as navigating ctrl+home and ctrl+end should always go to top of
page and end of page.  I've noticed in the keyboard list home depends on
where it is, and that can be anoying and confusing having keys act
differently depending on where you are in a web page.
5. This is probably more gnopernicus related than mozilla, but it would be
very nice to have a command that would announce the active link, active
frame, and table location. I don't know how many times I have been on a web
page, in a table, and unable to figure out what column and row I was in on
the table.

Hth.



----- Original Message -----
From: "Peter Korn" <Peter Korn Sun COM>
To: "Luke Yelavich" <themuso themuso com>
Cc: "Tom and Esther Ward" <tward1978 earthlink net>;
<gnome-accessibility-list gnome org>
Sent: Thursday, April 29, 2004 8:24 PM
Subject: Re: Mozilla 1.7 rc1 issues.


> 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
>
>