Re: [orca-list] Fw: XUL
- From: "Rich Caloggero" <rjc MIT EDU>
- To: "Aaron Leventhal" <aaronlev moonset net>
- Cc: orca-list gnome org
- Subject: Re: [orca-list] Fw: XUL
- Date: Tue, 15 Jul 2008 16:48:37 -0400
OK, will add it now. I wanted to get confirmation from a nonscreen reader
user as well to be sure it wasn't the screen reader causing problems. I did
just verify that about an hour ago.
Thanx.
-- R
----- Original Message -----
From: "Aaron Leventhal" <aaronlev moonset net>
To: "Rich Caloggero" <rjc MIT EDU>
Cc: <orca-list gnome org>
Sent: Tuesday, July 15, 2008 4:21 PM
Subject: Re: [orca-list] Fw: XUL
Hi Rich,
Apologies for not getting back to you :)
Sometimes it's just best to file a bug with a testcase. Your case is
certainly not a common one that anyone had an answer for immediately! :)
Everyone's pulled in 10 directions at once. The bug database helps us
focus on one problem at a time without losing track.
- Aaron
Rich Caloggero wrote:
Not sure if this is the best place to post this, but it does relate to my
navigation extension. I got no response on the dev-accessibility list at
mozilla, so thought I'd post here.
I've been finding some weirdness in the way xul is handled. I'm not
sure where the problem lies: with firefox or screen reader.
The nd most rellevant to my navigation extension development is the
fact that things seem to get very sluggish when dealing with xul listboxes
containing many elements. See the test case at:
http://narita.mit.edu/ncam/firefox/xul/list.xul
This simply creates a list of 1400 elements and displays it. This is a
large
list, but some pages (look at wikipedia's index pages) have many links, so
handling lists of this number of elements is necessary. There are two
buttons, one just before the list and one just after to give the screen
reader something to focus on which is not the list. They are dummy
placeholders and do nothing when clicked.
What I notice is:
focusing on the list and pressing down arrow - wait a long time before
the screen reader responds and reads next item
* I see this behavior with jaws, window-eyes, and NVDA under latest
firefox.
Have not been able to test with orca yet.
Can anyone reproduce these results? How does it act without a screen
reader?
Update: I just enlisted a sighted person to take a look, and she says that
the page is extremely slow. Can anyone else verify this?
I did try an HTML page with many elements in Firefox and it works well.
Thanx much.
-- Rich
_______________________________________________
dev-accessibility mailing list
dev-accessibility lists mozilla org
https://lists.mozilla.org/listinfo/dev-accessibility
_______________________________________________
Orca-list mailing list
Orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
Visit http://live.gnome.org/Orca for more information on Orca
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]