Jacob said:
Do you know of a menu that is indexable and standards compliant?
Maybe. What are "indexable" and "standards compliant" supposed to mean
in this regard?
Approach (formatted unordered list with :hover pseudo-classes) is OK to
me, however realisation includes some Voodoo I'd certainly refrain from
(viable solution is indicated by `-->'):
- Serving XHTML 1.1 as text/html (forbidden)
--> Serve either HTML 4.01 Strict as text/html
or XHTML 1.x as application/xhtml+xml.
Can be combined for IE compatibility using Content Negotiation.
Can be maintained easier with server-side scripting.
- Serving XHTML without character processing instruction (unwise)
--> Include the instruction
or use Valid HTML 4.01 Strict served with charset in Content-Type
header and
<meta
http-equiv="Content-Type"
content="text/html; charset=...">
element as first child of the `head' element.
- Using the `style' element in XHTML without reference in
a stylesheet processing instruction (not supposed to work)
--> Include the instruction or serve HTML 4.01.
- Indenting elements -999em
--> Reasonable formatting of elements
- Using
<script type="text/javascript"><!--//--><![CDATA[//><!--
...
//--><!]]></script>
--> Use
<script type="text/javascript">
<![CDATA[
...
]]>
</script>
in Valid XHTML served as application/xhtml+xml
or include external script file
or use
<script type="text/javascript">
...
</script>
in Valid HTML 4.01.
- Not declaring variables
--> Use the `var' keyword.
- Using the `function' expression where a `function' statement suffices
--> Use the `function' statement instead.
- Testing for and usage of window.attachEvent()
--> Use the `onload' event handler attribute value to call function.
HTH
PointedEars
