Re: Mozilla 1.7 rc1 issues.

[Ken Perry <whistler blinksoft com>]

When I see a developer say they don't have an estimate on when things 
will get better that tells me one of two things there is either not a 
plan or not enough people working on the plan.  After seeing the other 
replies to your question and the question in itself I see there is not 
much plan.  What I want to know is is there enough developers working on 
this project or is there a need for more developers.  

I guess in short I am a software developer I make games for a living but 
I don't mind working on other projects but after going over a lot of the 
Gnome pages its hard to figure out where to dive in and get started.  Is 
there documents on what is beign done on the web interfaces or is that 
something someone needs to do is jump in and get some of these web 
interface functionalities documented and ready for codigng?

I have developed software on my own so long now I don't know where to 
get started joining a development group but I am an accomplished linux 
coder and if pointed in the right direction will climb in and hang on 
for the ride so can someone who needs help on a Gnome speech access 
project let me know where I can help?  If that means the web interface 
is the place then I want to get going.

KenOn Thu, 29 Apr 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
> 
> 
> _______________________________________________
> gnome-accessibility-list mailing list
> gnome-accessibility-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
>