Keeping in mind that everyone has their own opinion on semantically correct
markup, I'll give you my opinion.
If they are reduced to their most basic level, navigation links are simply a
list of links to other parts of the site.
If we assume that some devices will see them without any css or other visual
styling, then it is important that they have some meaning and structure. So,
a list can (arguably) be seen as the most semantically correct option.
The funny thing about css is that all elements are just blocks to be styled
as you need - <div>, <form>, <address>, <a>, <p>... Doesn�t matter. You can
still apply borders padding, margin, colour and background colour...
So, it should not be TOO hard to convert your nav system into a list. All
you have to do is overcome the default behaviour of the list first. This is
achieved by a few rules like:
ul { margin: 0; padding: 0; list-style-type: none;}
li { display: inline}
Be warned, my brain is gone tonight so this code could be a little off :)
Once you take out these browser default behaviours you can rework your own
rules and you are away.
Russ
> Awwwww russ...
> I see your point!
>
> One thing - which I have NEVER understood is...
> Why you people all use Lists?
> I mean I just dont understand why lists are used for menus...
> It sounds like a stupid question - beause a menu is a list...
>
> But just wondering, why you use them, instead of simply lining up the
> content??
>
> I dont know how well i can convert the code to work with a list...
> I will try, otherwise I can just use a to spread it...
> Chris Stratford
> [EMAIL PROTECTED]
> Http://www.neester.com
>
>
> russ weakley wrote:
>> Chris,
>>
>> The tabs looks really nice but Tonico does have a point. If you strip out
>> all css styles, the links will appear in one line with very little between
>> them - making them hard to distinguish on older browsers, browsers that have
>> css switched off or text-based browsers..
>>
>> Could you convert that system into a list and tweak the styles slightly?
>> Then you'd have (arguably) a much more semantically correct base to work
>> from.
>>
>> Russ
>>
>>
>>
>>> It has been said that adjacend links should be separated with more then
>>> whitespace.
>>>
>>> WCAG 10.5
>>> <http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-divide-links>
>>> <http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#tech-divide-links>
>>>
>>> Don't know if this is relevant for your audience.
>>>
>>> Tonico
>>>
>>
>> *****************************************************
>> The discussion list for http://webstandardsgroup.org/
>> See http://webstandardsgroup.org/mail/guidelines.cfm
>> for some hints on posting to the list & getting help
>> *****************************************************
>>
>>
>>
>>
>>
> ***************************************************** The discussion list for
> http://webstandardsgroup.org/ See
> http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to
> the list getting help *****************************************************
Thanks
Russ
-----------------------------------------------
Russ Weakley
Max Design
Phone: (02) 9410 2521
Mobile: 0403 433 980
Email: [EMAIL PROTECTED]
http://www.maxdesign.com.au
-----------------------------------------------
*****************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
*****************************************************
