HTML

HTML 4.01 including DHTML and XHTML

HTML and XHTML should be tested against the W3C Validator at http://validator.w3.org/
Avoid proprietary and deprecated HTML tags such as <marquee> and <iframe>

Style Sheets (CSS)

▪ CSS should be tested against the W3C Validator at http://jigsaw.w3.org/css-validator/
▪ CSS should be used for layout in preference over tables
▪ Relative font sizing should be used in style sheets to allow users to resize fonts in the browser (see Appendix for example approach)
▪ A print style sheet should be provided to improve page printing
▪ NCSL recommend the use of style sheets to define a tight set of styles that will be used within the content to improve consistency.

o Preferred Styles:

§ Body text – Arial (standard system fonts)

§ Headings – Arial, Bold, not Italic (standard system fonts)

§ Error Message Text – Arial, Dark-red, Bold

§ Hyperlinks – Blue, underlined

JavaScript

▪ JavaScript should comply with Document Object Model (DOM) 1 conventions and proprietary commands should not be used, unless an alternative is provided for other browsers.

▪ JavaScript should be tested on NCSL approved browsers - see appendix for NCSL Supported Web Browsers List

Flash version 7

▪ Content will usually be provided in HTML format with embedded Flash objects.

▪ NCSL recommend that Flash movies are not directly added to HTML pages using the OBJECT/EMBED HTML tags. This is because in April 2006, Microsoft changed the way Internet Explorer handles Flash plug-in content, requiring users to “click to activate” Flash movies. Read more : http://www.adobe.com/devnet/activecontent/

▪ A widely accepted workaround is to use the SWFObject code, available from http://blog.deconcept.com/swfobject/ which also includes detection code.

▪ Flash-based content should include flash-player detection code, and appropriate error messages, in each instance that requires Flash.

▪ Participants without the Flash 7 plug in should be guided through the download process in concise and intuitive way. The possible need to download the Flash plug-in should be clearly communicated to participants in any related literature, help guides or at face to face sessions.

▪ Original Flash files are to be delivered in FLA format by the Supplier, with their embedded content (eg bitmaps) in their original formats.

Frames

▪ We encourage developers to use alternatives to frames where possible although there are occasions where there are no alternative.

▪ When frames are used they should be labeled properly for accessibility (* see also Accessibility)

Server-side technology

▪ NCSL can support units built with ASP, but normally only client-side technology will be used.

▪ Please speak to the NCSL online team before developing any units built with server-side requirements. * see also the Hosting Section

No Java Applets

▪ No Java Applets should be included in e-learning units for NCSL.

Create your own awesome maps

Even on the go