Hi Essential,

Hi, it is going to be a list of news events and
will hopefully when I figure it out print the info
to RSS that's why I was thinking of the DL so it's
just a list of some events rather that full news?

I'm sorry, I guess I don't realy understand what you're after. I mean I understand you want a list, but you also asked for the best markup. You see, naturally I guess I shy away from the list idea to begin with.

With the source order and how it's displayed, plus the addendum of a date, naturally forms an order so to speak so I thought the best approach was to make the marking up part as simple as possible. In other words I couldn't think of a reason for a list.

That said, if for some reason it _must_ be listed, I guess this would be about as clean as it can be (the span assumes you want the date to be styled differently)...

<ul>
<li>
 <h#>Heading/Title</h#>
  <p><span>The Date</span> - The excerpt/content.</p>
</li>
<li>
 <h#>Heading/Title</h#>
  <p><span>The Date</span> - The excerpt/content.</p>
</li>
</ul>

...but again, I don't think this brings anything to the table that would be considered beneficial or more accessible. Albeit these may not be particularly detrimental solutions, I just didn't/don't understand why the list is needed to begin with.

I don't really recommend an ordered list because, as said, the date and physical order is enough in this case. And I don't really recommend a DL either because I would assume you'd use the definition title element for the title, but doing so would make those titles more difficult for screen reader users as they wouldn't be able to use the DT as navigation aids as they can and do with headings.

I must disclaim again, though, I don't really understand your final goal or what exactly you're after so if a list is necessary...

Respectfully,
Mike Cherim


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [email protected]
*******************************************************************

Reply via email to