Problems with VoiceOver interaction
Problems with VoiceOver interaction
- Subject: Problems with VoiceOver interaction
- From: Håkan Waara <email@hidden>
- Date: Fri, 6 Oct 2006 11:48:22 +0200
Hi all,
Right now I'm testing VoiceOver with our initial accessibility
support in Firefox.
1. Since we're providing info about webpages, there are a huge amount
of elements. What are the general ways of speeding up such
interaction with VoiceOver?
I've found that VoiceOver seems to recurse all hierarchies, trying
know everything about everything. It also repeatedly queries the same
elements for the same attributes (like AXRole) over and over. So more
often than not, VoiceOver just says "busy!". When it's done, it will,
if I'm lucky, speak the currently focused element.
2. Another problem is that VO cursor sometimes doesn't move. Right
now I'm firing off a AXFocusChanged notification for every focus
change, but sometimes VO doesn't seem to care. Sometimes it speaks
the focused element's name/text, but doesn't bother to move the
cursor. Maybe it's too busy parsing my other stuff?
So, I would appreciate general ways to make interaction more
performant. Right now it's almost unusable. I've tried reducing big
parts of the hierarchy (ignoring many roles), but webpages will
always be webpages, so this is not a problem we as an accessible
implementation can step around.
As a final observation: I noticed that WebKit currently uses some
kind of internal AppKit method to assign unique IDs to elements, such
that they are weakly referenced (and faster?).
Ideas, comments?
Thanks,
Håkan Waara _______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden