E-mail List Archives
Re: Accessible Javascript
From: Andrew Kirkpatrick
Date: Sep 20, 2004 3:18PM
- Next message: Jukka K. Korpela: "Re: Re[2]: examples of accessible sites"
- Previous message: Patrick H. Lauke: "Re: Accessible Javascript"
- Next message in Thread: None
- Previous message in Thread: Patrick H. Lauke: "Re: Accessible Javascript"
- View all messages in this Thread
Ben,
Assuming javascript is required, which seems to be the case, it is best to
make sure that the HTML created by the script is standard and accessible,
and that it loads as soon as the page loads. If the HTML loads after the
rest of the page, users might not be made aware of the text. Similarly, if
a user reads beyond the new items and then they change, the user might not
know that the change has occurred. In some cases the user would need to
force a refresh of the page model, in others the user just needs to navigate
to the changed content, but won't know where that changed content is.
Not too easy in either case. Provide information to help users, and
consider a noscript alternative that is non-dynamic.
AWK
>> i'm interested in the fact that (some) Screen readers can use
>> javascript - how could I then test to see wether it was accessible?
>
> first of all: turn javascript off, then test...can you still access the
> core functionality? e.g. if the javascript is used to create some sort
> of navigation system, can the site still be navigated when javascript is
> not available?
>
> next: check any documentation from screen reader manufacturers. do they
> give any information about which javascript functionality is seamlessly
> supported by their product? e.g.
> http://www.freedomscientific.com/fs_support/BulletinView.cfm?QC=565
>
> "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."
>
> although there are other cases not covered by this (e.g. scripts
> attached to onload behaviour that manipulate the DOM at page load time)
>
> other than that, short of testing it in different screenreader/browser
> configurations, the best would be to ask on lists such as this one, i
> think...
>
> Patrick H. Lauke
> _____________________________________________________
> re
- Next message: Jukka K. Korpela: "Re: Re[2]: examples of accessible sites"
- Previous message: Patrick H. Lauke: "Re: Accessible Javascript"
- Next message in Thread: None
- Previous message in Thread: Patrick H. Lauke: "Re: Accessible Javascript"
- View all messages in this Thread