Daniel et al,
(I don't really know enough about DHTML to comment on that, but as for Javascript:)
As Ruth says, this kind of depends what you are doing with them. The Web Accessibility Initiative guidelines say that it's ok to use scripts as long as an alternative means of accessing the content is provided. As long as you make judicious use of the <NOSCRIPT> tag and code the pages in such a way ( ie. cleanly & logically) that they transform gracefully without the use either of Javascript or style sheets, then you shouldn't have too much of a problem in my experience.
To quote WAI - 'Ensure that pages featuring new technologies transform gracefully' (http://www.w3.org/TR/WCAG10/):
6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. [Priority 1] When content is organized logically, it will be rendered in a meaningful order when style sheets are turned off or not supported.
Techniques for checkpoint 6.1 <http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/> 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1]
Techniques for checkpoint 6.2 <http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/> 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [Priority 1] For example, ensure that links that trigger scripts work when scripts are turned off or not supported (e.g., do not use "javascript:" as the link target). If it is not possible to make the page usable without scripts, provide a text equivalent with the NOSCRIPT element, or use a server-side script instead of a client-side script, or provide an alternative accessible page as per checkpoint 11.4. Refer also to guideline 1.
As an aside to this, I have recently been quoted 0.03% of users surfing with Javascript disabled in their browser preferences by one webmaster, while another told me that their logs registered up to 6% of users. There's no real indication of the number of people for whom Javascript will present a real problem.
I suppose the only other point I would highlight is that it also depends on where your Javascript is coming from. If it is being coded for you by someone who knows what they are doing, and who will also be responsible for integrating it into your pages, then there's lots you can do to make sure it works for as many people as possible. If, on the other hand, you are using cut and paste scripts and simply putting them into the HTML of your pages, this can cause some real problems - scripts often either conflict, or throw up some peculiarities when put in the wrong place. Furthermore, there is a danger in pasting 3rd party scripts and then trying to edit the pages using a WYSIWYG HTML editor - some of these will try and identify the scripts and, in extremis, may re-write parts of them for you.
This raises another question by the way - anyone who is using browser/system recognition to define the output of their content to the screen is likely to be using Javascript to do it. Is this acceptable given the question mark hanging over Javascript in general? Is this even something people are doing?
Regards,
Nick
Nick Poole
ICT Adviser
Resource: The Council for Museums, Archives and Libraries
16 Queen Anne's Gate
London
SW1H 9AA
Tel 020 7273 1410
New! Visit the Cornucopia database of UK museum collections at http://www.cornucopia.org.uk
Visit the Resource website at http://www.resource.gov.uk
Visit the Peoples Network website at http://www.peoplesnetwork.gov.uk
Join the Resourcenews email list at http://www.jiscmail.ac.uk
> -----Original Message-----
> From: Daniel Merriman [SMTP:[log in to unmask]]
> Sent: Tuesday, April 09, 2002 4:17 PM
> To: [log in to unmask]
> Subject: Re: DHTML & Javascript
>
> Hmm, thought about this one recently myself.
> DHTML would definitely allow for some more interesting presentation and interaction than pure HTML. Well troops, any thoughts...?
>
> PS For anyone who's interested: http://www.dhtmlcentral.com
>
>
>
> Daniel Merriman - Project Manager
>
> From Weaver to Web Project
> Calderdale MBC
> Reference Library
> Northgate House
> Halifax
> HX1 1UN
>
> 01422 392632
>
> >>> Tony Brindle <[log in to unmask]> 04/09/02 03:58pm >>>
> Can any tell me if DHTML and JavaScript are acceptable within a NOF
> project. I can't seem to find any mention of them with the guidelines.
>
> Thank you
>
> Tony Brindle
>
> *** SCANNED FOR VIRUSES ***
|
