UDM 4 is valid XHTML, and in our judgement, meets the criteria for WAI Triple-A conformance.
There are two scripts that make up the
ASP configuration - the
generated stylesheet, udm-style.asp, and the generated
menu script, udm-dom.asp. These are controlled from a
configuration file called udm-custom.asp
For the head section you need a single
<link /> element to include the
generated stylesheet, udm-style.asp:
<!-- ULTIMATE DROP DOWN MENU Version 4.6 by Brothercake -->
<!-- http://www.udm4.com/ -->
<!-- ASP generated stylesheet -->
<link rel="stylesheet" type="text/css" media="screen,projection"
href="/udm-resources/udm-style.asp" />
Other things being equal it can go anywhere in the head section. However since global styles can potentially affect the menus, but the menu styles are extremely unlikely to affect other rules, it's best to put it after any other style sheets.
The media attribute serves a twin purpose here - because Opera in fullscreen mode uses projection-media CSS, not screen, and because the comma-delimited syntax is not understood by primitive CSS browsers like Netscape 4, and so it won't process that stylesheet at all.
In the body section you need a single
script include for the generated menu script, udm-dom.asp.
It must go in the <body> -
if you put it in the <head> then it
won't work in Mac/IE5.
As with the script in the head section,
it doesn't need a language attribute:
<!-- ASP generated menu script [any modules or extensions must come AFTER this] -->
<script type="text/javascript"
src="/udm-resources/udm-dom.asp"></script>
Within the body section it can go anywhere, however if you have
an existing window.onload function on your page then the script
should come after it, to avoid an
onload conflict in Mac/IE5.
The DOM
script provides core functionality, but does not include full keyboard access.
For best accessibility I strongly recommend including the
keyboard navigation module
as well (which you already have in your udm-resources folder).
This should come after the udm-dom.asp script include:
<script type="text/javascript"
src="/udm-resources/udm-mod-keyboard.js"></script>
If you're using any other
modules or
extensions, these must also
go in the body section and come somewhere after the
udm-dom.asp script include.
The udm-custom.asp configuration file is used by both scripts,
and included using an ASP
#include statement, assuming
that the configuration file is in the same directory:
<!-- #include file="udm-custom.asp" -->
If you want to change the path you should edit these statements; you can find them at the top of each script.
The scripting is written in JScript, but since it's all in external files you can equally use it on pages written in VBScript. Neither the configuration file itself, nor the page that the menu is on, need to be parsed separately by ASP - it's only the two included scripts that do - so you have the freedom to use this configuration language on pages built in a different one.
UDM 4 is valid XHTML, and in our judgement, meets the criteria for WAI Triple-A conformance.
