E-mail List Archives
Re: Web accessibility and usability
From: Patrick H. Lauke
Date: Oct 11, 2004 11:30AM
- Next message: Sesock, Kevin A: "iCITA Petition (Accessible Web Publishing Wizard for Microsoft Office)"
- Previous message: Chris Heilmann: "Re: Web accessibility and usability"
- Next message in Thread: michael.brockington: "Re: Web accessibility and usability"
- Previous message in Thread: Chris Heilmann: "Re: Web accessibility and usability"
- View all messages in this Thread
lists38 wrote:
> AFAIR all screen readers (except for the linux ones of course) need IE as
> their engine, but they don't apply scripts that add additional HTML via
> DOM. If someone has other information, that'll be great to know.
And from what I remember (speaking of first hand experience with JAWS,
so can't vouch for any other screenreaders), whether or not the
screenreader is present does not stop the DOM-changing javascript to be
executed in IE (it runs as it normally would), but the screenreader
itself only becomes aware of it if the changes were a result of user
interaction (activating a link, putting the focus on an element, etc)
Found this document a while ago, not sure if it still applies to the
very latest version (never mind the behaviour of other screenreaders):
"Q: How can I expect JAWS to handle JavaScript on my Web page?
A: JAWS will work correctly with JavaScript if:
* The scripts are activated by clicking a link or clickable item and the
script dynamically updates the HTML source.
* The scripts do not update the page without user intervention."
Patrick H. Lauke
_____________________________________________________
re
- Next message: Sesock, Kevin A: "iCITA Petition (Accessible Web Publishing Wizard for Microsoft Office)"
- Previous message: Chris Heilmann: "Re: Web accessibility and usability"
- Next message in Thread: michael.brockington: "Re: Web accessibility and usability"
- Previous message in Thread: Chris Heilmann: "Re: Web accessibility and usability"
- View all messages in this Thread