Hi A C,
I'm not seeing the headings. You are correct though with relation to
whether the cursors are tethered. I'd also add that if you have
group items in web pages checked, when you first enter the group on
your page with shift-vokeys-down arrow, the link does nt immediately
fire. you actually have to hit space or tab to get that to happen.
On Jul 30, 2006, at 6:37 PM, Alastair Campbell wrote:
Hi everyone,
I've been experimenting with VO and those JavaScript functions, and I
think I've worked out what happens, but thought it would be good to
check with the VO experts...
It seems to revolve around whether the mouse cursor follows the
keyboard cursor, which might explain why Tim and others had fairly
sporadic results.
On the first test case:
http://sf.id.au/js_tests/onmouseover/mouseover-event-link.html
If you do not have the mouse pointer following the keyboard cursor (a
setting in the navigation tab of VO utility), I could not get the
mouse over event to activate.
I tried Tab, space, VO-space, and VO-shift-space. Without the mouse
pointer actually hovering nothing happened. Which makes sense from a
technical point of view, but seems different to what others have found?
However, if you move the pointer to the keyboard focus (VO-cmd-F5) it
activates, and you get returned to the top of the page. Then you can
read the link with the new text: "onmouseover link text - onmouseover
fired".
If you have the mouse pointer following the cursor, you can get into
quite a loop, activating the link and getting put at the top of the
page. I managed to get a page full of link text!
Does that sound about right? I made a quick variation on the test
page to make it easier to understand:
http://alastairc.ac/testing/voiceover/mouse_over_event_on_link_test.html
It has a heading, paragraph 1, link with onmouseover, and paragraph 2.
Kind regards,
-Alastair
