It's not so much what will happen as it is how do wee know something
is supposed to be happen. Vo will give us an indication that
something has happened but it won't tell us that something should
happen or where it should happen from. Jaws and window eyes report
the element attribs.
On Jul 24, 2006, at 6:39 PM, Alastair Campbell wrote:
Hi everyone,
I have a request for help, which hopefully will be an interesting web
development experiment.
Gez Lemon recently did a very good article on screen reader support for
JavaScript, specifically the on-mouseover event:
http://juicystudio.com/article/screen-reader-onmouseover.php
However, there is one glaring omission: Voiceover.
Would anyone here be able to go through the test cases and report back
(to me or Gez) the results?
It would involve going to each of the test cases (I've added the links
below my name), and recording what is announced for each, and whether it
is possible to activate them.
These tests are very useful for web developers, and I wouldn't want to
miss report something because of my inexperience with VO.
Kind regards,
-Alastair
8 Test cases:
1: http://sf.id.au/js_tests/onmouseover/mouseover-event-link.html
2: http://sf.id.au/js_tests/onmouseover/mouseover-event-link-delay.html
3: http://sf.id.au/js_tests/onmouseover/mouseover-event-non-link.html
4: http://sf.id.au/js_tests/onmouseover/mouseover-event-non-link-
delay.html
5: http://sf.id.au/js_tests/onmouseover/mouseover-event-link-add-
text.html
6:
http://sf.id.au/js_tests/onmouseover/mouseover-event-link-add-text-
delay.html
7:
http://sf.id.au/js_tests/onmouseover/mouseover-event-non%20link-add-
text.html
8:
http://sf.id.au/js_tests/onmouseover/mouseover-event-non%20link-add-
text-delay.html
