E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 4 (In chronological order)

From: smithj7
Date: Wed, Aug 22 2007 6:10PM
Subject: Re: Navigation lists and headers - best practise?
No previous message | Next message →

I've been using header levels for my navigation ever since I went to the
Assistive Technology conference in Orlando, FL. The speech users said
it was a definate improvement from a whole much of link lists on a
website. It broke up the link lists on front pages in a similar way
that a sited person might have. However, I was wondering if anyone uses
the navigation list for xhtml? I only learned about it recently and
don't want to change everything if it is not good standards.

Example code follows:

<nl>
<label>Contents </label>
<li href="#introduction">Introduction</li>
<li>
<nl>
<label>Terms</label>
<li href="#may">May</li>
<li href="#must">Must</li>
<li href="#should">Should</li>
</nl>
</li>
<li href="#conformance">Conformance</li>
<li href="#references">References</li>
...
</nl>


-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Penny Roberts
Sent: Wednesday, August 23, 2006 11:05 AM
To: WebAIM Discussion List
Subject: [WebAIM] Navigation lists and headers - best practise?


This is going off at a tangent from the original post so I've started a
new thread.

In response to the thread "are there any accessibility testing
best
practices" Jon Gunderson posted a link to the Functional Web
Accessibility Evaluation Tool.
I've looked at the UIUC "Best Practices" site before but I must
have
missed this: http://cita.uiuc.edu/html-best-practices/nav/menus.php
Does everyone agree that it is best practice to have an h2
heading
before a ul used for navigation? I've never come across the suggestion
before so I'm interested to know how well supported (or not)+ the idea
is.

Penny

From: Moore, Michael
Date: Thu, Aug 23 2007 7:30AM
Subject: Re: Navigation lists and headers - best practise?
← Previous message | Next message →

= EMAIL ADDRESS REMOVED = wrote:

I've been using header levels for my navigation ever since I went to the
Assistive Technology conference in Orlando, FL. The speech users said
it was a definate improvement from a whole much of link lists on a
website. It broke up the link lists on front pages in a similar way
that a sited person might have. However, I was wondering if anyone uses
the navigation list for xhtml? I only learned about it recently and
don't want to change everything if it is not good standards.

Mike's response:

The navigation list element <nl></nl> is a part of the xhtml 2.0
specification, which I believe is still a draft document. As far as I
know browser and screen reader support for this docType is virtually non
existent. I found X-Smiles but it only offered partial support for <nl>
http://www.x-smiles.org/features_xhtml2.html. I would recommend
continuing to mark up navigation lists using semantic xhtml 1.0/html
4.01 list markup and use heading elements appropriately.

Mike

From: Austin, Darrel
Date: Mon, Aug 27 2007 3:30PM
Subject: Re: Navigation lists and headers - best practise?
← Previous message | Next message →

Whoa...this thread is going on over a year now. Made me go back and
reflect on some of the comments.

I'm being swayed by the H2 arguments, yet I still like the semantics of
using a DL list. Any thoughts on an implementation like this:

<dl>
<dt>
<h2>Section Navigation Title</h2>
</dt>
<dd>
<ul>
<li>link</li>
<li>link</li>
</ul>
</dd>
<dt>
<h2>Section Navigation Title</h2>
</dt>
<dd>
<ul>
<li>link</li>
<li>link</li>
</ul>
</dd>
</dl>

Redundant? Useful?

-Darrel

From: Jukka K. Korpela
Date: Mon, Aug 27 2007 4:00PM
Subject: Re: Navigation lists and headers - best practise?
← Previous message | No next message

On Mon, 27 Aug 2007, Austin, Darrel wrote:

> Whoa...this thread is going on over a year now.

And it's really not leading anywhere, is it?

> I'm being swayed by the H2 arguments, yet I still like the semantics of
> using a DL list.

A definition list doesn't magically become semantically appropriate just
because people like its semantics. If you really love it, leave it for its
_defined_ use as a list of _terms_ and their definitions.

> <dt>
> <h2>Section Navigation Title</h2>
> </dt>

Here we go again. It's not just semantically wrong. It's even
syntactically wrong, since dt elements allows inline content only (not
surprisingly, since terms are words, not blocks).

--
Jukka "Yucca" Korpela, http://www.cs.tut.fi/~jkorpela/